Relational Database Characteristics Sample Clauses

Relational Database Characteristics. The RDBMS should utilize the concept of user views whereby pseudo-schema are defined and stored for utilization by users without the users becoming involved in the actual schema and sub-schema structures of the database. The system should provide a security system to control utilization of user views by user ID, account, and activity.
AutoNDA by SimpleDocs

Related to Relational Database Characteristics

  • Characteristics The Initial Contracts have the following characteristics: (i) all the Contracts are secured by Motorcycles; (ii) no Initial Contract has a remaining maturity of more than 84 months; and (iii) the final scheduled payment on the Initial Contract with the latest maturity is due not later than June 2014. Approximately 77.89% of the Principal Balance of the Initial Contracts as of the Initial Cutoff Date is attributable to loans for purchases of new Motorcycles and approximately 22.11% is attributable to loans for purchases of used Motorcycles. No Initial Contract was originated after the Initial Cutoff Date. No Initial Contract has a Contract Rate less than 3.989%. The last scheduled payment date of the Contracts (including any Subsequent Contracts) is due not later than September 2014. Approximately 98.98% of the Principal Balance of the Initial Contracts as of the Initial Cutoff Date is attributable to loans to purchase Motorcycles manufactured by Harley-Davidson or Buell and approximately 1.02% of the Principal Balance of the Initial Contracts as of the Initial Cutoff Date is attributable to loans to purchase Motorcycles not manufactured by Harley-Davidson or Buell.

  • Additional Service Characteristics 3.12 The technical specification of the Bitstream 2a Service is set out in Appendix B.

  • ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to Image Access via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one (1) dataset per workday per OCN. If BellSouth determines the Secure FTP Mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.

  • Physical File Characteristics 6.2.1 The Optional Daily Usage File will be distributed to <<customer_name>> via an agreed medium with CONNECT:Direct being the preferred transport method. The Daily Usage Feed will be a variable block format (2476) with an LRECL of 2472. The data on the Daily Usage Feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN.

  • Demographic, Classification and Wage Information XXXXXX agrees to coordinate the accumulation and distribution of demographic, classification and wage data, as specified in the Letter of Understanding dated December 14, 2011, to CUPE on behalf of Boards of Education. The data currently housed in the Employment Data and Analysis Systems (EDAS) will be the source of the requested information.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)

  • Contract Database Metadata Elements Title: Whitesville Central School District and Whitesville Central School Educational Support Staff Association (2003) Employer Name: Whitesville Central School District Union: Whitesville Central School Educational Support Staff Association Local: Effective Date: 07/01/2003 Expiration Date: 06/30/2006 PERB ID Number: 10699 Unit Size: Number of Pages: 23 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT BETWEEN WHITESVILLE CENTRAL SCHOOL EDUCATIONAL SUPPORT STAFF ASSOCIATION AND THE WHITESVILLE CENTRAL SCHOOL DISTRICT JULY 1, 2003 THROUGH JUNE 30, 2006 TABLE OF CONTENTS ARTICLE TITLE PAGE Preamble 1 I Recognition 1 II Collective Bargaining U n i t 1 III Dues/Agency Fee Ckoffand Payroll Deduction 1 IV Rights of Employees 2 V Rights of Employer ------------- 2 VI Personnel F i l e 2 VII Employee Definitions 3 VIII Permanent Status/Seniority 4 IX Wages 5 X Overtime 7 XI Vacation 7 XII Holidays 8 XIII Sick Leave and Leavesof A b s e n c e 8 XIV Conference, Workshops,Required Courses 10 XV Meal Allowance and M i l e a g e 11 XVI Retirement 11 XVII Insurance 12 XVIII Cafeteria P l a n 14 .XIX Uniform Allowance------------------ 14 XX Hours of W o r k 14 XXI Transfers/Promotions 15 XXII Job Descriptions 15 XXIII Grievance Procedure 15 XIV Copies of the Contract 18 XV Zipper C x x x x x 18 XXVI Legislative Clause 18 XXVII Duration 19 SIGNATURES 19 APPENDIX A Grievance F o r m 20 APPENDIX B Dues Authorization F o r m 21

  • Segmentation The purchase of any Products and related Service Offerings or other Service Offerings are all separate offers and separate from any other order for any Products and related Service Offerings or other Service Offerings You may receive or have received from Oracle. You understand that You may purchase any Products and related Service Offerings or other Service Offerings independently of any other Products or Service Offerings. Your obligation to pay for (a) any Products and related Service Offerings is not contingent on performance of any other Service Offerings or delivery of any other Products or (b) other Service Offerings is not contingent on delivery of any Products or performance of any additional/other Service Offerings. You acknowledge that You have entered into the purchase without reliance on any financing or leasing arrangement with Oracle or its affiliate.

  • Technical Characteristics The Participating Generator has provided to the CAISO in Schedule 1 the required information regarding the capacity and operating characteristics of each of the Generating Units listed in that schedule. Pursuant to Sections 8.9 and 8.10 of the CAISO Tariff, the CAISO may verify, inspect and test the capacity and operating characteristics provided in Schedule 1.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

Time is Money Join Law Insider Premium to draft better contracts faster.