Predict the outcome

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss content posted by SQL Buzz » Predict the outcome

24 posts, Page 1 of 3

1 2 3 »»»

Predict the outcome

Rate Topic

Display Mode

Topic Options

Author

Message

bazzkar

Posted Wednesday, July 14, 2010 9:32 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, September 03, 2010 4:19 AM
Points: 158, Visits: 72

Comments posted to this topic are about the item Predict the outcome

Post #952829

ziangij

Posted Thursday, July 15, 2010 1:06 AM

SSCommitted

Group: General Forum Members
Last Login: Friday, May 17, 2013 2:53 AM
Points: 1,528, Visits: 359

thanks, nice simple one... Smile

Post #952887

Posted Thursday, July 15, 2010 1:07 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, April 11, 2013 12:58 AM
Points: 174, Visits: 555

1% of 186 or 2 people answered in relation to user permission. I bet these same people were wary of syntax errors and gotchas.

Post #952888

cengland0

Posted Thursday, July 15, 2010 3:37 AM

Ten Centuries

Group: General Forum Members
Last Login: Thursday, January 24, 2013 9:59 PM
Points: 1,354, Visits: 1,299

The URL in the explanation didn't say you cannot use a zero -- at least not that I found.

So why can't you use it? If you have IDENTITY INSERTS on, can't you duplicate values on an Identity column? I never tried that but I think you can unless you also create a constraint to make it unique. So I thought if you have an increment of 0, you'd get the same number in the identity column for every new row.

Post #952941

Rune Bivrin

Posted Thursday, July 15, 2010 4:19 AM

SSCrazy

Group: General Forum Members
Last Login: Today @ 12:46 AM
Points: 2,657, Visits: 719

I couldn't find any mention of the restriction on increment either. My gut reaction was to answer "error" given that an zero increment makes no sense, but as I couldn't see that in the documentation I figured it may actually be valid.

I should have followed my first thought...

Just because you're right doesn't mean everybody else is wrong.

Post #952967

Duncan Pryde

Posted Thursday, July 15, 2010 4:54 AM

Hall of Fame

Group: General Forum Members
Last Login: Today @ 6:35 AM
Points: 3,046, Visits: 1,303

Rune Bivrin (7/15/2010)

I couldn't find any mention of the restriction on increment either.
.

I agree, there doesn't seem to be any mention in the documentation about it. And it's not just zero increments - you can't have a seed or increment which has a higher value than the maximum for the data type, or lower than the minimum (hence you can't have negative increments with tinyint identity columns). You can't have fractional values for either seed or increment, etc., etc.

All semi-obvious, but as yet I can't find any official documentation.

Duncan

Post #952992

ronmoses

Posted Thursday, July 15, 2010 5:46 AM

SSChasing Mays

Group: General Forum Members
Last Login: Today @ 5:12 AM
Points: 649, Visits: 686

Good question. In retrospect it seems obvious, and I think that's why I didn't go with the obvious answer. Like others I researched the question as far as possible without actually running the script, and I couldn't find any solid documentation on it either. I went with "can't predict" figuring there might be an option set that could affect the outcome.

-----
a haiku...

NULL is not zero
NULL is not an empty string
NULL is the unknown

Post #953026

Bob Razumich

Posted Thursday, July 15, 2010 6:23 AM

Old Hand

Group: General Forum Members
Last Login: Today @ 7:33 PM
Points: 376, Visits: 884

For all who look at the data in the URL, I agree that there is no explicit statement that one cannot have a 0 increment. I suppose the following line,

"If an identity column exists for a table with frequent deletions, gaps can occur between identity values. If this is a concern, do not use the IDENTITY property. "

infers that issue, if you add to the sentence "because the identity property may try to make a duplicate after you fill in a gap without proper coding to look for duplicates" etc.

If one does try to run the command, the actual error message that I got was "Identity column 'mainkey' contains invalid INCREMENT." So it's an "undocumented feature."

And no, I honestly didn't execute the command before I answered the question.

Post #953063

OCTom

Posted Thursday, July 15, 2010 6:45 AM

SSCrazy

Group: General Forum Members
Last Login: Today @ 11:48 AM
Points: 2,015, Visits: 2,843

It makes sense to me that an identity increment can't be zero. An identity column is supposed to be a unique index on a row. If you had zero for the increment, all rows would have the same value; the starting value. That would make no sense at all.

Do we really need to have Microsoft tell us the perfectly obvious? w00t

Post #953077

Terri Walls

Posted Thursday, July 15, 2010 6:55 AM

Forum Newbie

Group: General Forum Members
Last Login: Friday, November 30, 2012 9:37 AM
Points: 1, Visits: 85

BTW, the answer ,"Explanation: We cannot use 0 as the incremental seed of the primary key. " Is not accurate. The create statement does not mention primary key. It is an invalid increment of an identity column, nothing to do with the primary key or lack thereof.

Post #953092

« Prev Topic | Next Topic »

24 posts, Page 1 of 3

1 2 3 »»»

Permissions