February 7, 2018 at 5:14 am
Dear Friends
I was able to back up my database in sql 2000 and restore in sql 2008, but the objects, jobs, and logins are not coming
Can someone help me?
thanks
Almir
February 7, 2018 at 5:19 am
Which objects have not been restored? You can bring the logins across using sp_help_revlogin and as for the jobs you can just script those out.
Thnanks
February 7, 2018 at 5:22 am
Just to add, why are you using 2008? It's 10 years old now and not supported. Do you have the option to use a more up to date version or are you using 2008 as a stepping stone to then restore to a higher version?
Thanks
February 7, 2018 at 5:41 am
NorthernSoul - Wednesday, February 7, 2018 5:22 AMJust to add, why are you using 2008? It's 10 years old now and not supported. Do you have the option to use a more up to date version or are you using 2008 as a stepping stone to then restore to a higher version?Thanks
im will upgrade to sql 2012, but im need to send to 2008 first
Thanks
Almir
February 7, 2018 at 5:41 am
NorthernSoul - Wednesday, February 7, 2018 5:19 AMWhich objects have not been restored? You can bring the logins across using sp_help_revlogin and as for the jobs you can just script those out.Thnanks
Logins and Jobs
how im can use this script? can send me script and instructions ?
February 7, 2018 at 5:42 am
almirfiorio - Wednesday, February 7, 2018 5:41 AMNorthernSoul - Wednesday, February 7, 2018 5:22 AMJust to add, why are you using 2008? It's 10 years old now and not supported. Do you have the option to use a more up to date version or are you using 2008 as a stepping stone to then restore to a higher version?Thanks
im will upgrade to sql 2012, but im need to send to 2008 first
Thanks
Almir
That's what I thought it would be. Post back if you have any problems.
Thanks
February 7, 2018 at 5:46 am
NorthernSoul - Wednesday, February 7, 2018 5:42 AMalmirfiorio - Wednesday, February 7, 2018 5:41 AMNorthernSoul - Wednesday, February 7, 2018 5:22 AMJvst to add, why are you using 2008? It's 10 years old now and not supported. Do you have the option to use a more up to date version or are you using 2008 as a stepping stone to then restore to a higher version?Thanks
im will upgrade to sql 2012, but im need to send to 2008 first
Thanks
AlmirThat's what I thought it would be. Post back if you have any problems.
Thanks
You have the step to step to upgrade sql 2000 to sql 2012 with logins and jobs ?
February 7, 2018 at 5:50 am
almirfiorio - Wednesday, February 7, 2018 5:41 AMNorthernSoul - Wednesday, February 7, 2018 5:19 AMWhich objects have not been restored? You can bring the logins across using sp_help_revlogin and as for the jobs you can just script those out.Thnanks
Logins and Jobs
how im can use this script? can send me script and instructions ?
Google sp_help_revlogin and you will find the script and instructions for how to use it. You will execute it on your source and it will produce a script of the logins to run on your target.
As for the jobs you can right click on the job and 'script job as'.
Thanks
February 7, 2018 at 6:34 am
NorthernSoul - Wednesday, February 7, 2018 5:50 AMalmirfiorio - Wednesday, February 7, 2018 5:41 AMNorthernSoul - Wednesday, February 7, 2018 5:19 AMWhich objects have not been restored? You can bring the logins across using sp_help_revlogin and as for the jobs you can just script those out.Thnanks
Logins and Jobs
how im can use this script? can send me script and instructions ?
Google sp_help_revlogin and you will find the script and instructions for how to use it. You will execute it on your source and it will produce a script of the logins to run on your target.
As for the jobs you can right click on the job and 'script job as'.
Thanks
im create script and try to execute in another databade
but im receive this error
Obs : triggers, views, and store procedures come automatically?
February 7, 2018 at 6:40 am
almirfiorio - Wednesday, February 7, 2018 6:34 AMNorthernSoul - Wednesday, February 7, 2018 5:50 AMalmirfiorio - Wednesday, February 7, 2018 5:41 AMNorthernSoul - Wednesday, February 7, 2018 5:19 AMWhich objects have not been restored? You can bring the logins across using sp_help_revlogin and as for the jobs you can just script those out.Thnanks
Logins and Jobs
how im can use this script? can send me script and instructions ?
Google sp_help_revlogin and you will find the script and instructions for how to use it. You will execute it on your source and it will produce a script of the logins to run on your target.
As for the jobs you can right click on the job and 'script job as'.
Thanks
As for the jobs you can right click on the job and 'script job as'.
how im can do that ?
In management studio expand the Jobs tree under SQL Server Agent--> Right click on the job you want to script out-->Script Job As-->Create to-->Then select where you want the save/send the script for creating the job
Thanks
February 7, 2018 at 6:47 am
Jobs and logins are not part of the database, they're part of the instance (server).
Jobs are stored in the msdb database and logins are stored in the master database. I believe that you shouldn't backup and restore those databases for an upgrade, but I might be wrong as I don't have real experience with upgrades.
Some other things that you might want to consider:
Roles, Linked Servers, Backup devices, Server wide triggers, etc.
February 7, 2018 at 6:59 am
Luis Cazares - Wednesday, February 7, 2018 6:47 AMJobs and logins are not part of the database, they're part of the instance (server).
Jobs are stored in the msdb database and logins are stored in the master database. I believe that you shouldn't backup and restore those databases for an upgrade, but I might be wrong as I don't have real experience with upgrades.
Some other things that you might want to consider:
Roles, Linked Servers, Backup devices, Server wide triggers, etc.
im use Script Job as and try to apply in new database, but i mreceive and error
February 7, 2018 at 6:59 am
almirfiorio - Wednesday, February 7, 2018 6:59 AMLuis Cazares - Wednesday, February 7, 2018 6:47 AMJobs and logins are not part of the database, they're part of the instance (server).
Jobs are stored in the msdb database and logins are stored in the master database. I believe that you shouldn't backup and restore those databases for an upgrade, but I might be wrong as I don't have real experience with upgrades.
Some other things that you might want to consider:
Roles, Linked Servers, Backup devices, Server wide triggers, etc.im use Script Job as and try to apply in new database, but i mreceive and error
What error are you getting?
Thanks
February 7, 2018 at 7:05 am
NorthernSoul - Wednesday, February 7, 2018 6:59 AMalmirfiorio - Wednesday, February 7, 2018 6:59 AMLuis Cazares - Wednesday, February 7, 2018 6:47 AMJobs and logins are not part of the database, they're part of the instance (server).
Jobs are stored in the msdb database and logins are stored in the master database. I believe that you shouldn't backup and restore those databases for an upgrade, but I might be wrong as I don't have real experience with upgrades.
Some other things that you might want to consider:
Roles, Linked Servers, Backup devices, Server wide triggers, etc.im use Script Job as and try to apply in new database, but i mreceive and error
What error are you getting?
Thanks
See the error in image
Cannot execute Script : unable to start the Tansact-SQL debugger. the Transact-SQL debugger does not support SQL Server 2005 or earlier versions of SQL Server
February 7, 2018 at 7:14 am
almirfiorio - Wednesday, February 7, 2018 7:05 AMNorthernSoul - Wednesday, February 7, 2018 6:59 AMalmirfiorio - Wednesday, February 7, 2018 6:59 AMLuis Cazares - Wednesday, February 7, 2018 6:47 AMJobs and logins are not part of the database, they're part of the instance (server).
Jobs are stored in the msdb database and logins are stored in the master database. I believe that you shouldn't backup and restore those databases for an upgrade, but I might be wrong as I don't have real experience with upgrades.
Some other things that you might want to consider:
Roles, Linked Servers, Backup devices, Server wide triggers, etc.im use Script Job as and try to apply in new database, but i mreceive and error
What error are you getting?
Thanks
See the error in image
Cannot execute Script : unable to start the Tansact-SQL debugger. the Transact-SQL debugger does not support SQL Server 2005 or earlier versions of SQL Server
What version of SSMS are you using and are you definitely connected to a SQL Server 2008 instance?
Thanks
Viewing 15 posts - 1 through 15 (of 22 total)
You must be logged in to reply to this topic. Login to reply