Viewing 15 posts - 55,426 through 55,440 (of 59,072 total)
Yes... don't allow developers to have access to write to production machines. Works for us. Create a new server with snapshots of the production box and use that as the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2007 at 2:09 pm
Heh... forget PayPal... UPS will ship a keg ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2007 at 2:03 pm
I don't have access to 2k5, yet, Michael... did they keep the information schema views named the same way?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2007 at 2:02 pm
Heh... yeah... Just look for anything that uses MAX(somecolumnname)+1 or @@IDENTITY in the code. If the aren't "in sync", it'll cause Primary Key violations which is the error you're getting.
Also,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2007 at 1:58 pm
I'd also like to throw my hat in the ring with the others that expressed some disappointment in certs... or rather I should say in some of the people that...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 10:33 pm
I like that answer, Rudy! My similar favorite is "I don't know, but here's what I'm doing to find out!".
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 10:21 pm
DateTime columns have no format... the dates are actually stored as a special form of FLOAT (BOL says 2 INTs but that's not quite right). Changing the column to a...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 10:08 pm
I don't use Power Builder so this will likely not be much help... but, if it were me, I'd select 1 column at a time to troubleshoot which column is...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 10:00 pm
You cannot use a column name as a parameter for a table valued function. From Books Online...
Multi-statement Table-valued Functions
CREATE FUNCTION [ owner_name. ] function_name
( [ { @parameter_name [AS]...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 9:50 pm
Show us the INT value for '5/10/2007' and we'll be able to tell you (but I think you're wrong about the date) ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 9:46 pm
Um... just making sure... you're saying that the current size of TempDB is over 166 GIGA BYTES ![]()
???
I'm...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 8:10 pm
Oh... almost forgot... if the code uses MAX(someid)+1 to determine the next "Key" or uses @@IDENTITY (SCOPE_IDENTITY is OK), that may be the source of the "Key" being out of...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 8:03 pm
Here's a powerful hint... the "key" this error message speaks to is either a "Primary Key" or a column with a UNIQUE index (usually a "Primary Key" for this error).
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 8:01 pm
Ah, sorry... that's too much info...
This will do it without a loop... again, if you get negative numbers for rows for some tables, you will need to do a DBCC...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 7:54 pm
Could be a couple of things, but let's go for the simple side, first.
Try adding the WITH RECOMPILE option to the stored proc... you may be fighting something bad that...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 8, 2007 at 7:25 pm
Viewing 15 posts - 55,426 through 55,440 (of 59,072 total)