Maintaining a Database Sample Clauses

Maintaining a Database. 1. In regard to CPC Prospectus filings, CDNX will create and maintain an Excel spreadsheet or other database which contains the following information: (a) the name of each CPC and its trading symbol; (b) the date of filing of the preliminary prospectus; (c) the date the preliminary Receipt was issued; (d) the date the final Receipt was issued; (e) the date of listing; (f) whether a possible Qualifying Transaction was identified in the prospectus; (g) the dollar amount of seed capital; (h) the number of shares being offered under the IPO; (i) the price per IPO share; (j) the IPO Regulator; (k) the CDNX office that reviewed the prospectus; (l) the jurisdictions in which the initial public offering was made; and (m) the date of announcement by the CPC of each proposed Qualifying Transaction. 2. CDNX will also maintain a record of the number of CPC Prospectuses filed, the number that were rejected by the Executive Listing Committee and the number that were withdrawn or abandoned. In regard to any that were rejected by the Executive Listing Committee, the reasons for that rejection will be recorded. If known, the reasons for withdrawal or abandonment will also be recorded. 3. In regard to Qualifying Transaction filings, CDNX will maintain an Excel spreadsheet or other database which contains the following information: (a) the name of each CPC, each Resulting Issuer and each of their respective trading symbols; (b) the date of announcement of the proposed Qualifying Transaction; (c) the date of initial filing of the QT Circular; (d) the dollar amount of any concurrent financing and whether it was conducted by the CPC or a Target Company; (e) the proposed industry sector of the Resulting Issuer; (f) the location of the Resulting Issuer’s head office and, if different, the location of its principal business operations; (g) the CDNX office that reviewed the QT Circular; (h) whether the Qualifying Transaction is a Related Party Transaction as defined in CDNX Policy 5.9; (i) escrow requirements or other resale restrictions imposed by CDNX on any person, other than as contemplated by CDNX’s Policy 5.4 – Escrow, Vendor Consideration and Resale Restrictions; (j) whether CDNX concluded that any person or company was an Excluded Person under sections I B 1 (c) (ii) (B) or II A 4 (b) (ii) of Appendix A and, if so, the name of the person or company, and the reasons for the decision; (k) the date of CDNX’s Bulletin confirming acceptance for filing of the QT Circular; (l) if ...
Sample 1Sample 2
AutoNDA by SimpleDocs
Maintaining a Database. Server Manager can also be used for maintaining a database and preparing it for shutdown. If a database incurs minor problems, such as an operating system write error, these tools enable you to sweep a database without taking the data- base offline. Some of the tasks that are part of database maintenance are: • Sweeping a database • Shutting down the database to provide exclusive access to it • Validating table fragments • Preparing a corrupt database for backup • Resolving transactions “in limbo” from a two-phase commit • Validating and repairing the database structure Server Manager enables the DBA to monitor the status of a database by viewing statistics from the database header page, and an analysis of tables and indexes. CHAPTER 2‌ Building InterBase Databases To create a database and its components, InterBase uses an implementation of SQL which conforms to the ANSI SQL-89 entry-level standard and follows SQL-92 and SQL3 beta specifications for advanced features. Building a database involves defining the data. For this purpose InterBase pro- vides a set of statements called the Data Definition Language (DDL). A database consists of a variety of database objects, such as tables, views, domains, stored procedures, triggers, and so on. Database objects contain all the information about the structure of the database and the data. Because they encapsulate information about the data, database objects are sometimes referred to as metadata. An InterBase database is a single file comprising all the metadata and data in the database. To create a new database for the Local InterBase Server, use Windows ISQL. For more detailed information, see Chapter 4: “Using Windows ISQL.” The following sections provide an overview of the InterBase database objects. For more information on databases and database objects, see the Data Definition Guide. For the complete syntax of data definition statements, see the Language Reference. Figure 2-1: Database Objects‌‌ Tables Domains Indexes Stored Procedures Views Triggers Exceptions Generators Columns Relational databases store all their data in tables. A table is a data structure con- sisting of an unordered set of horizontal rows, each containing the same number of vertical columns. The intersection of an individual row and column is a field that contains a specific piece of information. Much of the power of relational databases comes from defining the relations among the tables. InterBase stores information about metadata in sp...
Sample 1

Related to Maintaining a Database

  • Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.

  • Maintaining Records The Borrower will record, summarize and report all financial information in accordance with GAAP.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Database File The Servicer will provide the Successor Servicer with a magnetic tape (in a format reasonably acceptable to the Indenture Trustee and the Servicer) containing the database file for each Contract (i) as of the Initial Cutoff Date, (ii) the Subsequent Cutoff Date, (iii) thereafter, as of the last day of the preceding Due Period on each Determination Date prior to a Service Transfer and (iv) on and as of the Business Day before the actual commencement of servicing functions by the Successor Servicer following the occurrence of a Service Transfer.

  • Web Site Information on registration for and use of the E-Verify program can be obtained via the Internet at the Department of Homeland Security Web site: xxxx://xxx.xxx.xxx/E-Verify.

  • TLD Nameservers ICANN will use commercially reasonable efforts to ensure that any changes to the TLD nameserver designations submitted to ICANN by Registry Operator (in a format and with required technical elements specified by ICANN at xxxx://xxx.xxxx.xxx/domains/root/ will be implemented by ICANN within seven (7) calendar days or as promptly as feasible following technical verifications.

  • Contract Database Metadata Elements Title: Great Neck Union Free School District and Great Neck Paraprofessionals Association (2011) Employer Name: Great Neck Union Free School District Union: Great Neck Paraprofessionals Association Local: Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 5132 Unit Size: Number of Pages: 28 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/ ARTICLE# TITLE PAGE# Preamble 2 Article 1 Association Rights 2 Article 2 Board-Administration-Association Relationship and Procedures 4 Article 3 Exchange of Proposals 6 Article 4 Professionals Duties and Responsibilities of Paraprofessionals 7 Article 5 Work Assignments 8 Article 6 Annual Appointment 10 Article 7 Selection and Promotion 10 Article 8 Evaluations and Standards 11 Article 9 Procedures for Termination of Employment 11 Article 10 Conferences 12 Article 11 Human Resource File 12 Article 12 Professional Growth 13 Article 13 Sick Leave 14 Article 14 Personal Leave 16 Article 15 Other Leaves 17 Article 16 Grievance Procedures 18 Article 17 Legal Assistance 19 Article 18 Conformity to Law 19 Article 19 Health Insurance 20 Article 20 Retirement Plan 20 Article 21 Salary Schedule 21 Article 22 Seniority Policy 23 Article 23 Compensation for Financial Loss 24 Article 24 Duration of Agreement 25 Appendix A Determination of Negotiating Unit 25 Appendix B Payroll Deduction Authorization 26 Appendix C Bus Aides 26 Appendix D Salary Schedules 27

  • Sites 11.1 To enable Digital Origin to fulfill its obligations under any Contract: 11.1.1 the Client shall permit or procure permission for Digital Origin and any other person(s) authorised by Digital Origin to have reasonable access to the Client’s Sites, Equipment and/or Leased Equipment and any other relevant telephone system and other equipment and shall provide such reasonable assistance as Digital Origin requests. 11.1.2 Digital Origin will normally carry out work by appointment and during Normal Working Hours but may request the Client to (and the Client shall) provide access at other times. In the event that the Client cancels, reschedules or misses any pre-arranged appointment, it shall be liable to Digital Origin for any costs and expenses which Digital Origin incurs as a result of such cancellation, rescheduling and/or missed appointment. 11.2 At the Client’s request, Digital Origin may agree (at its sole discretion) to work outside Normal Working Hours and the Client shall pay Digital Origin’s reasonable charges for complying with such a request. 11.3 The Client warrants, represents and undertakes that it has adequate health and safety provisions in place at its Sites. 11.4 The Client shall procure all consents, licences and permissions necessary from landlords or other third parties for the carrying out of preparation work, installation of Equipment and/or Leased Equipment and for the provision, use and operation of the Equipment and/or Leased Equipment and/or Services at the Sites (save to the extent Digital Origin has agreed in writing to do it). 11.5 In the event that the Client is not able to procure the necessary consent to provide the Services within ninety days of the Connection Date Digital Origin will be able to terminate the Contract forthwith by giving the Client written notice without any liability. If the Client has not managed to procure the necessary consents and Digital Origin has commenced work the Client shall, on request by Digital Origin, refund to Digital Origin the cost of all such work (including, without limitation, staff costs and equipment costs) of an amount no less than £500 as Early Termination Charges. 11.6 The Client shall provide Digital Origin with the site and building plans (to include full details of all internal cabling runs) of the Sites and provide Digital Origin with full details of all other services in the vicinity of the proposed works. 11.7 The Client is responsible for making the Site good after any work undertaken by Digital Origin at a Site, including without limitation replacing and re-siting items and for re-decorating. 11.8 If the Client is moving a Site, Digital Origin must be informed as soon as is reasonably practicable so that suitable arrangements can be made to transfer the Client’s Services and Equipment and/or Leased Equipment. Unless otherwise requested, Digital Origin, in addition to moving the Service and Equipment and/or Leased Equipment, will also endeavour (but cannot guarantee that it will be able, for example where the Client moves to a different exchange) to retain the Client’s relevant existing telephone number(s). If Digital Origin can transfer the Client’s existing number(s) to the new Site the existing Contract will continue under the same terms and conditions. If Digital Origin cannot transfer the Client’s existing number(s) to the new Site, installation of a new line will be required at the new Site, or if the Client requires any additional new lines, this will attract new line connection charges and a new Contract. 11.9 If the new installation or moving Site involves the visit of an engineer to facilitate the new installation the Client will be responsible for the costs incurred by Digital Origin for the appointment together with an administration fee in respect of any additional works required to be undertaken by Digital Origin to complete the transfer of the Services and Equipment and/or Leased Equipment. 11.10 If the Client moves Sites and leaves the Equipment and/or Leased Equipment for the new owner/tenant the Client is required to inform them that the Service will be discontinued if Digital Origin is not contacted by the new owner/tenant within 72 hours for the purpose of entering into a new contract with Digital Origin for such services and subject in any event to the agreement of such a contract. 11.11 If at the new Site the Client receives services from an alternative supplier the Client is responsible for any contractual agreement the Client has with them and any liabilities the Client may incur for terminating such agreement.

  • Domain Name Data 1.5.1 Query format: whois EXAMPLE.TLD 1.5.2 Response format:

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!