Dev and UAT environment


hello,
not know sql server dba tasks next project setup dev, uat environment.
there production server.
there allocated 1 server dev , server uat environment.
as far know, should install sql server on each of dev , uat server, latest backup production , restore dev , uat servers.
questions:
1- assumption above correct?
2- should consider , have successful setup start finish these environment?
3- thing can add me learn?
4- there link y ou can guide me kind of setup me study before start t project?
kind regards

hi,

1. yes correct. backup , restore correct approach. question sql server version , edition same on dev/uat of production. if same makes task easy. install sql server on dev /uat , make sure service pack level of dev/uat same prod, mean after installing sql server install sp well. after take backup of user , system databases , restore on dev/uat. restoring user database easy can refer this link restore system databases. if not true follow below. point 1 make sure dont need move logins,jobs , ssis packages if any

2. after have moved database using backup restore, need fix orpahned users. or can migrate logins using how transfer logins between sql server. create sp_help_revlogin. , follow procedure mentioned

3. move database 1 server other

4. link added. need move jobs scripting out.

cheers,

shashank

please mark reply answer if solved issue or vote helpful if helped other forum members can benefit

my technet wiki articles
mvp



SQL Server  >  SQL Server Setup & Upgrade



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more