December 6, 2017 at 10:28 am
I have a client that has some of their prod sql servers as part of the workgroup edition and basically looking to use LogShipping configured through SQLSafe in order to perform migration from one server to another having the same SQL version. I was testing this based on the steps as listed by the DBA and I couldn't proceed post step 1. After disabling LogShipping policies through SQLSafe the next step was to alter the database to bring it to read/write state on the secondary but even after disabling the policy I cannot push the database into read/write mode as it is part of LogShipping and is in standby/readonly mode and the operation would definitely fail. I tried doing it manually taking tail of the log on the primary and then leaving it in recovery state and then tried to restore the backup on the secondary but it failed as it says that I don't have appropriate permissions as these accounts are local to the server and cross server copy and backups would definitely fail. I am about to get back to them and force them to move those servers into domain and use domain account for SQL services. Also, I still don't get it why would they place prod servers into workgroup and how can I convince them to move their servers into using AD.
December 6, 2017 at 10:38 am
The simple answer is security, in a workgroup you will need to leap through hoops to lower security, open ports etc etc. How valuable is their data? It would seem not very much! I am only addressing your last point, there may be some who think the setup is good but I doubt it.
...
December 6, 2017 at 11:26 am
If the servers are in a Workgroup, then the only way their going to be able to "talk" to each other is via a SQL Login. If they need to do things like access another Server's storage, however, then you've got no chance.
SQL Servers, at least in a multi-user/multi-workstation environment work A LOT better inside a Domain, using Domain Authentication.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
December 18, 2017 at 6:33 am
ffarouqi - Wednesday, December 6, 2017 10:28 AMI have a client that has some of their prod sql servers as part of the workgroup edition and basically looking to use LogShipping configured through SQLSafe in order to perform migration from one server to another having the same SQL version. I was testing this based on the steps as listed by the DBA and I couldn't proceed post step 1. After disabling LogShipping policies through SQLSafe the next step was to alter the database to bring it to read/write state on the secondary but even after disabling the policy I cannot push the database into read/write mode as it is part of LogShipping and is in standby/readonly mode and the operation would definitely fail. I tried doing it manually taking tail of the log on the primary and then leaving it in recovery state and then tried to restore the backup on the secondary but it failed as it says that I don't have appropriate permissions as these accounts are local to the server and cross server copy and backups would definitely fail. I am about to get back to them and force them to move those servers into domain and use domain account for SQL services. Also, I still don't get it why would they place prod servers into workgroup and how can I convince them to move their servers into using AD.
Please see my article at the following link
http://www.sqlservercentral.com/articles/Log+Shipping/76757/
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply