December 1, 2008 at 3:45 am
Hi Dear all,
I have migrated my dts packages by using wizard. But i want to know 'what is the process to transfer a SQL 2000 job to a SQl 2005 server?
I have many jobs, to create it manually its very long process, is there any simple and quick magic to transfer all jobs at the same time.
sorry for my bad english.
Thanks in advance.
Regards,
m.i.'
________________________________________
M.I.
[font="Times New Roman"]
December 1, 2008 at 4:06 am
You could use the SSIS transfer jobs task (on the 2005 server) to pull the jobs over.
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
December 1, 2008 at 1:09 pm
You could also script out the jobs in Enterprise Manager and run the script in a SQL 2005 query window.
Greg
February 18, 2010 at 3:45 pm
Hi all,
When i am running sql 200 job scripts in sql 2005, i am getting the following error.
Msg 515, Level 16, State 2, Procedure sp_add_job, Line 137
Cannot insert the value NULL into column 'owner_sid', table 'msdb.dbo.sysjobs'; column does not allow nulls. INSERT fails.
The statement has been terminated.
Any idea on this error? I have migrated DTS packages to sql 2005, now i am planning to move jobs. I generated script for one job and ran it. Then this error occured. Any help please....
Thanks in advance....
February 19, 2010 at 3:15 am
harsha_you (2/18/2010)
Hi all,When i am running sql 200 job scripts in sql 2005, i am getting the following error.
Msg 515, Level 16, State 2, Procedure sp_add_job, Line 137
Cannot insert the value NULL into column 'owner_sid', table 'msdb.dbo.sysjobs'; column does not allow nulls. INSERT fails.
The statement has been terminated.
Any idea on this error? I have migrated DTS packages to sql 2005, now i am planning to move jobs. I generated script for one job and ran it. Then this error occured. Any help please....
Thanks in advance....
Hi harsha,
pls check ur script that should be tru for the following conditions,
1) A string concatenation is done in the WHERE clause against a character column.
2) This column is used in an ORDER BY clause.
3) This column contains a NULL.
4) This column is not indexed.
5) The concat_null_yields_null option is not set for this connection or this database. This condition can be met by any one of the following:
a) Explicitly issuing the command set concat_null_yields_null off.
b) Using a client application that uses DB-Library or an ODBC driver older than version 3.70.0623.
c) Running the database in SQL Server 6.x compatibility mode.
Check It may help u.
________________________________________
M.I.
[font="Times New Roman"]
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply