August 29, 2015 at 3:47 am
[font="Arial"]
Hello. I need to implement a Lab environment and in order to do this i have installed a new Virtual Machine with the same configuration and Software releases.
I've performed a Full Backup of the application production DB using SQL Server Management Studio. The SQL Server is the 2014 Edition.
How can i restore this DB into the Lab machine? Using the "restore" function is enough? or is better to do something else in some other ways?
The application i need to start in the Lab Environment is BMC Remedy.
Thanks a lot
Alessandro
[/font]
Alessandro Feltrin
Information Security Professional
CISA Certified
ITIL v.3 Foundation Certified
BooleServer 3.2 Certified
August 29, 2015 at 5:23 am
alessandro.feltrin (8/29/2015)
[font="Arial"]Hello. I need to implement a Lab environment and in order to do this i have installed a new Virtual Machine with the same configuration and Software releases.
I've performed a Full Backup of the application production DB using SQL Server Management Studio. The SQL Server is the 2014 Edition.
How can i restore this DB into the Lab machine? Using the "restore" function is enough? or is better to do something else in some other ways?
The application i need to start in the Lab Environment is BMC Remedy.
Thanks a lot
Alessandro
[/font]
Quick thought, using the RESTORE (Transact-SQL) is the normal way of doing this. In addition you may want to script out logins, permissions, jobs etc. from the production DB as those are not included in the backup.
😎
August 29, 2015 at 6:51 am
Once you get the logins created on the destination server, you can restore from your backup. The only caution is that the SQL Server logins and database user SIDs won't match. If you're on the same domain, the Windows users should be fine.
To handle the mismatched SIDs, you can use execute sp_change_users_login.
August 29, 2015 at 10:23 am
[font="Arial"]
I don't use Windows authentication but SQL "sa" authentication, so i this case there should be no problem i feel. So, i should be able to restore my original DB also using Enterprise Management Studio ... If you suggest that it should be better to use T-SQL i have to find some appropriate script in order to submit a query ...
Alessandro
[/font]
Alessandro Feltrin
Information Security Professional
CISA Certified
ITIL v.3 Foundation Certified
BooleServer 3.2 Certified
August 29, 2015 at 9:01 pm
alessandro.feltrin (8/29/2015)
[font="Arial"]I don't use Windows authentication but SQL "sa" authentication, so i this case there should be no problem i feel. So, i should be able to restore my original DB also using Enterprise Management Studio ... If you suggest that it should be better to use T-SQL i have to find some appropriate script in order to submit a query ...
Alessandro
[/font]
I strongly recommend that you change your application to use a least-privilege login. It most likely only needs permission to execute procedures, and possibly data reader / data writer access.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
August 31, 2015 at 2:30 am
[font="Arial"]
Yes ... this sounds good. I will move to this direction.
Thanks a lot.
[/font]
Alessandro Feltrin
Information Security Professional
CISA Certified
ITIL v.3 Foundation Certified
BooleServer 3.2 Certified
August 31, 2015 at 6:01 am
I think the goal of moving in that direction is to arrive at a place where the "sa" login can be disabled and left that way. It's a well-known login that has sysadmin privileges, so it's a normal attack target.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply