weird problem
-
OK 4 as DBA, 2 as Freelance Consultant
* Noel -
That doesn't make you old... unless you started at 40
. -
Before that I was an Automation and Control Engineer for 10
* Noel -
How old are you BTW
* Noel -
24. I finished my 1 year course 14 months ago. Been a programmer/dba/network/helpdesk/analyst at the same job ever since.
-
I am 37, I loved Hardware until I moved to NY, none of that over here and I had to learn everything from scratch at 32
* Noel -
Still pretty young. Wouldn't wanna try that at 60
. -
Noel, you certainly found it!!!!!! That did the trick. Thanks a million.
-
Peter,
I did experienced that once but wasn't sure where to find it (good memory always helps)
Glad, that did the trick!
* Noel -
What causes that problem to come up in the first place?
-
Did you read the link?
* Noel -
Yup but it doesn't say what cause this problem to pop up in the first place (I know about the object_id... but what caused that problem).
-
Those IDs (object ID or Column ID ) are NOT identities, are internally managed by SQL Engine. if something goes wrong at the update event (this could be a canceled statement, thread lock, reboot at the wrong time, etc...) , wherever that happens internally, you will have to use something sort of reseed. Because that is not exposed on any API, you will have to use the brute force method
I know is not common but I guess I got lucky as our poster friend here
* Noel -
I wouldn't call that luck
. -
IT is call sarcasm
* Noel
Viewing 15 posts - 31 through 45 (of 47 total)
You must be logged in to reply to this topic. Login to reply