I've worked with terabytes of data for years, so I have to disagree with joe.

you can often expose your artificial key to the end user if needed, things like "lineitem"

it...

The obvious solution was a GUID, however I hate GUIDs for a number of reasons. One is the huge size--16 bytes does not a useful physical pointer make! My...

I'm with steve on this - the question wasn't "what do you do to fix this" - it was "what error will occur" - and even though I never use...

I see this mistake a lot unfortunately. Using a hashed value based on a multiple column natural key as a primary key.

Algorithms used for hashing values are never guaranteed...

and we could say the same in the UK for our national...

can you post the contents of an sp_who2  - we don't have much to go on

also is it sql that is using the CPU or another process - how are...

I've always found the following points be in favour of artificial keys

if my key is "firstname, surname, dateofbirth" then for every linked table I have to use 2 varchars and...

I made that same mistake - steve didn't...

hardware ?

SQL instance configuration ?

T-SQL code ?

Table design and 3NF?

you have to give us a little more about your problem so that someone can help you - I could go...

dammit - I pretty much only use persisted computed columns (we write once and read many)… so my version worked - I took out the persisted and it errored

Ian

unless i misread the original post (I've done that a lot) , they want a trailing zero not a leading zero

good shout sterling. It's got to be either network transfer or disk.

for network transfer, log onto the desktop and make sure your connection is using the shared memmory protocol (not...

one trick i use... Does it hang before the first row comes back, or start sending results and stall?

if you get nothing for 10 seconds I'd put money on compiles.

if...

the best I can suggest is reverse the string, do a charindex for the first colon :   then you know if there are only 2 digits for milliseconds

if it's...

check in the database settings if you have "legacy cardinality estimation" turned on - also if you can change the database compatability mode you may get some better results

i'd forget...