Can anyone tell me what kind of SQL language this is?

Post #258,948 by folkert 6/14/06 4:52:28 PM Reply	Can anyone tell me what kind of SQL language this is? This is just a small sample of the 28K Line file called "reload.sql". AdminGroup has these rights: GRANT CONNECT TO "AdminGroup" IDENTIFIED BY ENCRYPTED '...snip'\ngo\nGRANT GROUP TO "AdminGroup"\ngo\nGRANT DBA TO "AdminGroup"\ngo So this hopefully makes more sense. CREATE TABLE "AdminGroup"."abmc_account_internal"\n(\n "account_id" integer NOT NULL,\n "db_created_tms" timestamp NOT NULL,\n "db_modified_tms" timestamp NOT NULL,\n "modtimestamp_tms" integer NULL,\n "ending_balance_amt" numeric(20,5) NULL,\n "check_to_send_bool" bit NOT NULL,\n "special_type" smallint NULL,\n "cc_payment_account_id" integer NULL,\n "cc_payee_id" integer NULL,\n "service_charge_class_id" integer NULL,\n "interest_account_id" integer NULL,\n "interest_class_id" integer NULL,\n "service_charge_account_id" integer NULL,\n "last_statement_date" date NULL,\n "last_matched_trans_date" date NULL,\n "reconcile_statement_date" date NULL,\n "interest_date" date NULL,\n "service_charge_date" date NULL,\n "interest_amt" numeric(20,5) NULL,\n "service_charge_amt" numeric(20,5) NULL,\n "reconcile_statement_amt" numeric(20,5) NULL,\n "last_hand_doc" varchar(21) NULL,\n "cc_memo" varchar(100) NULL,\n "company_id" integer NULL,\n PRIMARY KEY ("account_id")\n)\ngo\nGRANT SELECT, INSERT, DELETE, UPDATE ON\n "AdminGroup"."abmc_account_internal" TO \n "UserGroup" FROM "AdminGroup"\ngo\nGRANT SELECT, INSERT, DELETE, UPDATE, ALTER, REFERENCES ON\n "AdminGroup"."abmc_account_internal" TO\n "AdminGroup" FROM "AdminGroup"\ngo Hopefully there is enough here. If not ask for more. I want to see if I can make this work for another db. I just need to know how to wrap it. -- [link\|mailto:greg@gregfolkert.net\|greg], [link\|http://www.iwethey.org/ed_curry\|REMEMBER ED CURRY!] @ *i_wethey* Freedom is not FREE. Yeah, but 10s of Trillions of US Dollars? SELECT * FROM scog WHERE ethics > 0; 0 rows returned.
Post #258,951 by admin 6/14/06 5:01:58 PM Reply	Looks like Sybase SQL Anywhere Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."
Post #258,955 by ChrisR 6/14/06 5:06:52 PM Reply	Pretty close to MS SQLServer But there are a couple of errors in trying to run it under SS2005. The Grant and the Create look like SS, though MS-SS doesn't like having two columns of type TIMESTAMP.
Post #259,175 by lincoln 6/16/06 4:56:03 PM Reply	Why not? MS-SS doesn't like having two columns of type TIMESTAMP. I've created (and needed) tables with multiple timestamp columns for years and have yet to run into any headaches using them. Granted, they were not huge tables - averaging 10K rows - but I'm not aware of anything in BOL advising to not have more than one TIMESTAMP column per table. lincoln "Chicago to my mind was the only place to be. ... I above all liked the city because it was filled with people all a-bustle, and the clatter of hooves and carriages, and with delivery wagons and drays and peddlers and the boom and clank of freight trains. And when those black clouds came sailing in from the west, pouring thunderstorms upon us so that you couldn't hear the cries or curses of humankind, I liked that best of all. Chicago could stand up to the worst God had to offer. I understood why it was built--a place for trade, of course, with railroads and ships and so on, but mostly to give all of us a magnitude of defiance that is not provided by one house on the plains. And the plains is where those storms come from." -- E.L. Doctorow Never apply a Star Trek solution to a Babylon 5 problem. I am not merely a "consumer" or a "taxpayer". I am a *Citizen* of the United States. [link\|mailto:bconnors@ev1.net\|contact me]
Post #259,185 by altmann 6/16/06 6:23:25 PM Reply	Re: Why not? "A table can have only one timestamp column." -- [link\|http://msdn2.microsoft.com/en-us/ms182776(SQL.90).aspx\|http://msdn2.microso...2776(SQL.90).aspx] -- Chris Altmann
Post #259,251 by lincoln 6/17/06 5:46:14 PM Reply	They must mean system time via the database Like I said, I've created many tables in the past with more than one timestamp column, all set programatically, and never had any problems. lincoln "Chicago to my mind was the only place to be. ... I above all liked the city because it was filled with people all a-bustle, and the clatter of hooves and carriages, and with delivery wagons and drays and peddlers and the boom and clank of freight trains. And when those black clouds came sailing in from the west, pouring thunderstorms upon us so that you couldn't hear the cries or curses of humankind, I liked that best of all. Chicago could stand up to the worst God had to offer. I understood why it was built--a place for trade, of course, with railroads and ships and so on, but mostly to give all of us a magnitude of defiance that is not provided by one house on the plains. And the plains is where those storms come from." -- E.L. Doctorow Never apply a Star Trek solution to a Babylon 5 problem. I am not merely a "consumer" or a "taxpayer". I am a *Citizen* of the United States. [link\|mailto:bconnors@ev1.net\|contact me]
Post #259,266 by ChrisR 6/17/06 7:08:20 PM Reply	TimeStamp is a non-standard type In MS SQLServer, it is a system generated value. From the BOL: Is a data type that exposes automatically generated, unique binary numbers within a database. timestamp is generally used as a mechanism for version-stamping table rows. In other databases, it's more like a DATETIME value would be. Anyhow, you can't have two timestamp columns in MS SQLServer because they would be identical with each other. This automatically tells me that the SQL script above is not related to MS.

Welcome to IWETHEY!