log-shipping | 易学教程

Upgrading from SQL 2000 - 2008 - Log Shipping

阅读更多关于 Upgrading from SQL 2000 - 2008 - Log Shipping

问题 I'm in the process of upgrading from SQL 2000 - SQL 2008 Would it be possible (or feasable) to set up log shipping from Server A - that has the sql 2000 database on, to Server B - that has the SQL 2008 instance on Or is there a better way of upgrading? I need to obviously test my application using the new SQL 2008 instance.... 回答1: You can certainly configure and script the steps that would be required manually, as Log Shipping is simply a copy of your transaction log file taken from the

T-SQL copy Logins, Users, roles, permissions etc

阅读更多关于 T-SQL copy Logins, Users, roles, permissions etc

问题 We have implemented log shipping as a database disaster recovery solution and want to know if there is a way I can use T-SQL to script all the logins, users, roles permissions etc to the master database on the secondary server so that the T-SQL can be sheduled to run as an SQL Job? My aim is that in the event of a D/R situation we can simply restore the transaction logs for each database to the secondary server and not have to worry about orphaned users etc. Thanks for you help! 回答1: There is

Creating Users on secondary server in log shipping

阅读更多关于 Creating Users on secondary server in log shipping

问题 I have a production Server say ServerA I have setup log shipping to ServerB which is left in read-only mode. The purpose of this log shipping is to lower the load on production server for some expensive queries (painful reports). Now if I have to create some logins using our domain accounts. I cannot do this because the secondary database is in standby mode . I thought if I create these logins on Primary server it will be copied over to secondary server then the logs are restored there but

Scripting Log Shipping Automation

阅读更多关于 Scripting Log Shipping Automation

问题 Is it possible to script All of the Log Shipping configuration? For example: I need to write a job that initiates Log Shipping from two databases from server A to server B. The job will run on Server A. By the way both are SQL 2008 R2 Enterprise. There's a share on server A. \serverA\Log I Believe this is all that is needed. Is it possible to do it just by script? Do I have to initialize the databases or is there a option like SSMS to auto initialize? Will I have to create the jobs manually?

Creating Users on secondary server in log shipping

阅读更多关于 Creating Users on secondary server in log shipping

I have a production Server say ServerA I have setup log shipping to ServerB which is left in read-only mode. The purpose of this log shipping is to lower the load on production server for some expensive queries (painful reports). Now if I have to create some logins using our domain accounts. I cannot do this because the secondary database is in standby mode . I thought if I create these logins on Primary server it will be copied over to secondary server then the logs are restored there but this isnt the case. I have done a lot of research online finding a way around to this. I found the

T-SQL copy Logins, Users, roles, permissions etc

阅读更多关于 T-SQL copy Logins, Users, roles, permissions etc

We have implemented log shipping as a database disaster recovery solution and want to know if there is a way I can use T-SQL to script all the logins, users, roles permissions etc to the master database on the secondary server so that the T-SQL can be sheduled to run as an SQL Job? My aim is that in the event of a D/R situation we can simply restore the transaction logs for each database to the secondary server and not have to worry about orphaned users etc. Thanks for you help! There is a login copy script here designed to copy logins to another server for disaster recovery purposes: http:/

Scripting Log Shipping Automation

阅读更多关于 Scripting Log Shipping Automation

Is it possible to script All of the Log Shipping configuration? For example: I need to write a job that initiates Log Shipping from two databases from server A to server B. The job will run on Server A. By the way both are SQL 2008 R2 Enterprise. There's a share on server A. \serverA\Log I Believe this is all that is needed. Is it possible to do it just by script? Do I have to initialize the databases or is there a option like SSMS to auto initialize? Will I have to create the jobs manually? or is it configured in a way that creates the jobs and manages them? Is it scriptable? Has anyone done