InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 20 Jun 2013 04:18:54 GMT20http://www.sqlservercentral.com/Forums/Topic754586-1599-1.aspxIt was straight forward Q, and had a straight forward ans. :-)Mon, 23 Nov 2009 23:01:40 GMTBhavesh_Patelhttp://www.sqlservercentral.com/Forums/Topic754586-1599-1.aspxI too missed the extra comma but saw the intent of the question. Despite that, it is nice to have learned something about the extra comma in table creates.Tue, 25 Aug 2009 12:03:27 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic754586-1599-1.aspxyupFri, 17 Jul 2009 21:15:23 GMTPapo Riverahttp://www.sqlservercentral.com/Forums/Topic754586-1599-1.aspxsorry - posted about the comma without seeing all the other posts - dunno whats wrong with this browser of mine...Fri, 17 Jul 2009 16:42:57 GMTmister.magoohttp://www.sqlservercentral.com/Forums/Topic754586-1599-1.aspxActually the answer is "NONE OF THE ABOVE". The answer (deemed correct) refers to IDENTITY INSERT set to ON. This query will run if IDENTITY INSERT is set to on. However, it is off. The actual error message refers to IDENTITY INSERT SET TO OFF. Minor verbiage change, but can make a big difference (several previous questions had details like this that made the difference between right and wrong so consistency should be maintained).CORRECTION: I just now saw the "not". The error message actually says "hen IDENTITY_INSERT is set to OFF" The "not" through me off. Cheers,BrianFri, 17 Jul 2009 11:48:22 GMTbeezellhttp://www.sqlservercentral.com/Forums/Topic754586-1599-1.aspxdidn't notice the comma, but I realized the intent of the question.Fri, 17 Jul 2009 10:22:19 GMTSteve Jones - SSC Editorhttp://www.sqlservercentral.com/Forums/Topic754586-1599-1.aspxI'm with you guys, I assumed that the comma would cause it to error before the table even got created. So, despite the ambiguous choices, learned something new!:-DFri, 17 Jul 2009 06:45:27 GMTjcrawf02http://www.sqlservercentral.com/Forums/Topic754586-1599-1.aspxI stand corrected. I just tried this query, as written, on both SQLServer 2000 and 2005 and the table DOES get created, even in spite of the extra comma.JimFri, 17 Jul 2009 06:07:15 GMTjimkernhttp://www.sqlservercentral.com/Forums/Topic754586-1599-1.aspxWhich version is giving you an error message?It executes fine in 2008. I tried because my recollection was that the comma does not cause a problem and hasn't for several versions.create table employe (id_num int identity(1,1),fname varchar(20),lname varchar(20),)Command(s) completed successfully.Fri, 17 Jul 2009 06:07:10 GMTbrdudleyhttp://www.sqlservercentral.com/Forums/Topic754586-1599-1.aspxAlthough I got the question right (I did not notice the extra comma), I agree this is a bad question. When you get the error message, no records get inserted into the table. Both the first and last option was correct.I knew either of them could have been the correct answer but the last one was more specific to the problem on why no records would have been inserted. Still, I believe anyone who selects the first answer should also get it right.Fri, 17 Jul 2009 05:45:52 GMTcengland0http://www.sqlservercentral.com/Forums/Topic754586-1599-1.aspxI'm sorry but you're wrong. This query as written will fail for syntax reasons. The comma after lname varchar(20), requires that another field be listed next, but one is not listed, therefore it will fail (which is answer A).Fri, 17 Jul 2009 05:36:55 GMTgrulkehttp://www.sqlservercentral.com/Forums/Topic754586-1599-1.aspxThe syntax is forgiving about the extra comma. I tried it and was able to create the table per the script. Seems this has come up in the course of my typing Create statements -- add the comma by default then decide no more columns are needed and the table still creates. Another example is when generating Create Table statements.Fri, 17 Jul 2009 04:55:41 GMTbrdudleyhttp://www.sqlservercentral.com/Forums/Topic754586-1599-1.aspxTrue, but that won't cause no rows to be inserted, it''l stop the table creation in the first place...Fri, 17 Jul 2009 04:00:44 GMTAndeavourhttp://www.sqlservercentral.com/Forums/Topic754586-1599-1.aspxActually, won't the comma after the lname column cause a syntax error? So, of those answers, "no rows will be inserted" is technically the most correct answer.JimFri, 17 Jul 2009 03:36:50 GMTjimkernhttp://www.sqlservercentral.com/Forums/Topic754586-1599-1.aspxComments posted to this topic are about the item [B]<A HREF="/questions/T-SQL/66598/">Identity_column</A>[/B]Thu, 16 Jul 2009 21:28:06 GMTanu1krishna