i see errors like this when the source file is not formatted perfectly...for example, if you think the file is comma delimited, but a COMPANY column has a a comma...

I consider it a bad practice to insert summary data into another table...it is very, very possible the data could be out of sync.

you should simly use a VIEW instead.

CREATE...

i would not let a non-dba force me to use an unfamiliar product just because someone wants a lot of columns in a table...I would stick with a product i...

lots of different scripts to do this in the scripts contribution area; search for "compare" and youll get results like these:

CREATE PROCEDURE PR_YOURPROCNAME(=@MS_ID INT,=@PROJECT_ID  INT) AS

UPDATE COST_PROJECT_PHASE

SET COST_PROJECT_PHASE.CONSTRUCTION_CONST = COST_PROJECT_PHASE_UNIFORMAT

FROM COST_PROJECT_PHASE_UNIFORMAT

WHERE COST_PROJECT_PHASE.MS_ID     = COST_PROJECT_PHASE_UNIFORMAT.MS_ID

AND COST_PROJECT_PHASE.PROJECT_ID = COST_PROJECT_PHASE_UNIFORMAT.PROJECT_ID

AND COST_PROJECT_PHASE.MS_ID=@MS_ID

ANDCOST_PROJECT_PHASE.PROJECT_ID =@PROJECT_ID

you are right...you can read or write a registry key, but there is no log or anything to tell you when a registry key was created/edited.

if there is a key...

i should have mentioned, and you probably found it...the second sql can produce a ton of results, so i limited it to top 100...you'd pull that out to get all...

if you have access to the original db on 2005, you can use the scripts below ; here you go:

first script generates both drop and add foreign key statments;

second script...

it's been a couple of months since i last installed an SP4 on a SQL server, but it went less than 15 minutes as i remember; if your server is...

because you are doning dynamic SQL, you'll want to put the SQL command in a string with a placeholder, and then replace the placeholder prior to the real exec statement....

time changes are at the operating system level..there is a registry patch for the operating system to change the daylight savings time on the new date available from microsoft...

sql server...

do not cross post...the Active topics function allows everyone to see new posts, regardless of forum. there is no need to ask the same question in multiple places.

answered here:

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=349780

the correct answer is to not remove the identity at all...NEVER update sys tables directly...

the identity column sis there for conveneince, and you can still insert by setting an additional...

that error is usually when you try and stick 10 characters into a field that is smaller than 10 for example...check the TEST server's DDL for the table...i would bet...

you might want to consider writing a program to do the work(open file, manipulate, save file) instead of in TSQL; most languages are more robust in their ability to edit files...