SQL Server Performance Forum – Threads Archive

Multiple instances

I am creating a standby server in which I want to make it a also a developer server. Can some one please give me some tips on this, such as which sould be the default instance and that kind of stuff.

After install SQL2000 for first time, you should install it again.
This second time ask for new instance. You can choose new name, differentes directories for data an so on.
Also you can stop or star each instance as you wish. Luis Martin …Thus mathematics may be defined as the subject in which we never know what we are talking about, nor whether what we are saying is true.
Bertrand Russell

You can have only one default instance to maintain as STANDBY server with the help of Log shipping and if you want to use that instance for query purposes only then you can use without any issues. And as mentioned by Luis you can have other instances as NAMED where it will work as individual installations. Review information from this technet linkhttp://www.microsoft.com/technet/tr…prodtechnol/sql/deploy/prodspecs/logship1.asp about settingup log shipping where you can re-direct to 2 servers where one can be used as exclusively for reporting purposes. Bear in mind if any updation made to the database that is on log shipping then LS process will break and the STANDBY server concept is only for READONLY queries. HTH Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Sorry, I missundertand the question.
Luis Martin …Thus mathematics may be defined as the subject in which we never know what we are talking about, nor whether what we are saying is true.
Bertrand Russell

Thanks. So the plan should be to make the default instance my standby server and the second instance should be for the developers? Purpose is I want to keep my developers off my production server would keeping two intances on the same box affect stand by server procedures?

With SQL Server 2000, you can run multiple instances of SQL Server on the same machine. Multiple instance support lets you do basic tasks, such as maintain two independent SQL Server environments for development and testing teams on the same physical machine. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Hi Lazy DBA What I do at my place is we create another exactly copy of the database When Developer login then database = gDevDbname (developer database) ortherwise it is the Production Database. Private Sub DevloperLogin(Optional bLogin As Boolean = True) gAdoConnectStr = "driver={SQL Server};OLE DB Services=-1;" & _ "server=" & gDevServer & ";uid=" & gDevUserID & "<img src=’/community/emoticons/emotion-4.gif’ alt=’;p’ />wd=" & gDevPwd & ";database=" & gDevDbname If bLogin Then DoLogin End If End Sub May the best cheaters win

For security reasons it is better to not have a default instance at all, unless you have a mixed SQL7/SQL2K box in which case you have no choice. A default instance gives any would be intruders one less thing to have to figure out… A default instance is only really there to allow backward compatibility… Cheers
Twan

True, valuable suggestion by Twan and anyway you can have only ONE default instance as its ideal to maintain the environment with named instance and open selective ports on the network to communicate between SQL server and other applications, when it comes to security. Another suggestion is never run DEVELOPERs environment on the same box of production, whether it may be a live or standby server. Keep off all testing database from the production server. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Well so should I just leave the server only for standby purposes? I just thought it would be a good idea to also create another instance on the same server and have the developers play around with it, since there developer server is very slow, they have the tendancy to run ad-hoc queries on my production server.

In my experience better not to create another instance for the testing purposes.
Standby server purpose will be dented if resources are shared for other productive work.
If the developers have real work to do for MIS purposes then yes you can create another instance and restore backup until last night for the work. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

]]>