You can use LEFT after casting to a character data type if that makes you feel better. Dividing by 100 does the exact same thing.

Maybe I'm overly sensitive, but I don't like this kind of comment.

Care to rephrase?

6473839 / 100 = 64738

Another vote for no difference.

I can't think of a scenario where access paths would be different.

An internals expert such as Paul White would probably expand the answer with implementation details.

I'm sure that there's a lot of good resources to learn CDC on the Internet. Have you tried googling that?

If you have specific questions you can come back any time...

Your requirement is bait confusing.

Can you post table script, sample data and expected output?

If in doubt, you can check out the article linked in my signature line.

For character columns you can use LEFT function, and for numeric columns you can use / 100.

Is this what you mean?

If you really need an identity column and you simply want it to start from a value other than 1, you can set it up as

IDENTITY [ ( seed ,...

Duplicate post.

Replies here please:

http://www.sqlservercentral.com/Forums/FindPost1132630.aspx

Duplicate post.

Replies here please:

http://www.sqlservercentral.com/Forums/FindPost1132630.aspx

My vote goes to the first method. It saves you from re-creating every depending object on the table (indexes, keys, defaults, constraints etc...)

This is a good SQLAgent replacement for Express edition:

http://sqlclockwork.smartbase.pl/

Hope this helps.

Gianluca

No performance gain. On the contrary, I think it could end up being a bit slower that way.

Whan I don't have a particular reason, I go for the single trigger.

Uhmm... I'm finding more and more references that describe query plans as re-entrant.

Also Grant in "SQL Server 2008 Query Performance Tuning Distilled" says so.

I'm a bit confused.

Steve, thanks for the good question. As usual, I got it wrong. 😛

Let me ask one question: this page on MSDN states that:

Server execution plans have the following main...