Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
CanadaDBA
583 Posts |
 Posted - 2005-10-17 : 10:15:46
|
| There was a problem in production and I had to FTP previous day's BAK file into development to find out the problem. (Don't ask why I hadn't have the BAK available in development. In fact, the FTP had failed on that specific day!! )I was wondering, is it a good idea to create another instance in the production and copy all the databases from default instance into the new instance every night? The new instance then would be available for support team to work on a database in case of any incident. What is Pros and Cons of this idea? Canada DBA |
|
|
Vivaldi
Constraint Violating Yak Guru
298 Posts |
Posted - 2005-10-17 : 10:20:31
|
| We have jobs that copy the databases to a development db server and then refresh the databases nightly. This allows developers to use production copies to check on issues, or test queries with fresh data if need be. We find it useful every week.________________________________________________SQL = Serious Quaffing of Liquor |
 |
|
|
CanadaDBA
583 Posts |
Posted - 2005-10-18 : 13:14:08
|
| Do I have to reboot the server after installing the second instance?Environment: SQL2k, Win2k3Canada DBA |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-10-18 : 13:18:44
|
| I don't like the idea of the installing a development instance on a production server even if it's only used for when there is a problem. This should be installed on another box. You don't always have to reboot after installing the instance, but often you do to apply the service pack. You can avoid the reboot if you shutdown all services that access the SQL Server files.Tara |
|
|
|
|
|
|
Another instance in production