August 31, 2009 at 2:26 am
Hello
I need to attach 2005 DB'd in 2008 server without the upgrade. Is this possible.
If not I need to find out how to get rid of the following message. If I run the attach manualy it works without errors. In the job it gives the following error.
Executed as user: LAB\Administrator. Converting database 'new_config' from version 628 to the current version 655. [SQLSTATE 01000] (Message 944) Database 'new_config' running the upgrade step from version 628 to version 629. [SQLSTATE 01000] (Message 951) String or binary data would be truncated. [SQLSTATE 22001] (Error 8152) The statement has been terminated. [SQLSTATE 01000] (Error 3621). The step failed.
I use the following script to attach.
EXEC sp_attach_db @dbname = N'new_config',
@filename1 = N'g:\Mssql\dataew_config_Data.MDF',
@filename2 = N'm:\Mssql\Log\New_Config_Log.LDF',
@filename3 = N'i:\Mssql\dataew_config_1.NDF',
@filename4 = N'i:\Mssql\dataew_config_2.NDF',
@filename5 = N'i:\Mssql\dataew_config_3.NDF',
@filename6 = N'j:\Mssql\dataew_config_4.NDF',
@filename7 = N'j:\Mssql\dataew_config_5.NDF',
@filename8 = N'j:\Mssql\dataew_config_6.NDF'
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
August 31, 2009 at 2:30 am
Hello
I see that the output of the upgrade is too long for the job execution. Is there a way to get around this. Swith off output maybe
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
August 31, 2009 at 3:36 am
tvantonder (8/31/2009)
I need to attach 2005 DB'd in 2008 server without the upgrade. Is this possible.
It is not possible. When a DB is restored or attached to SQL 2008 it has to be upgraded to the 2008 structure.
If you're encountering a problem with the upgrade scripts, I suggest that you contact Microsoft's customer support people. It's likely they're the only ones that will really be able to help you here.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 31, 2009 at 4:27 am
The upgrade is not the problem. I am attaching flashcopy from mirror on SAN. When I attache the DB in the job it gives that error. If I do it in management studio if give no errors
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
August 31, 2009 at 4:31 am
What's the script of the job?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 31, 2009 at 4:44 am
It is the same as the script I use to attach manualy. I just copy and past.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
September 1, 2009 at 12:37 pm
Can anyonde else help please
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
September 1, 2009 at 1:18 pm
Does this mean that the code in your original post works fine from SSMS but not when executed as a job by SQL Server Agent?
Just so that you know, we aren't mind readers and we can't see what you see. You really need to provide as much information as possible if you want any real help.
September 1, 2009 at 2:57 pm
please provide some more information so we can better understand the situation. Your last couple of posts indicate a job being run vs. in SSMS. Will you explain that a little better?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 2, 2009 at 10:56 am
That is correct. Code runs fine in SSMS but not in the job. It fails with the above mentioned message.
What can I post for you guys. I thought that it was enough but very willing to send more.
thanks
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply