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 |
|
delpiero
Yak Posting Veteran
98 Posts |
 Posted - 2005-04-07 : 21:35:57
|
| Hi all, I am planning to migrate a database into production. The production server already has SQL Server 2000 installed, with an instance running a database for another application. This application and our application are completely distinct with different database administrators. Usually, do you migrate into an existing instance, and create a new database on it, or do you create a new instance for the new application? I think there are issues related to security, patches, backup/restore .... Let's forget about licensing, is there any practical concerns for using the same instance?Thanks,delpiero |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-04-07 : 21:58:03
|
| The only concerns really are security and stability. An instance let's you have more granularity on who can have server/instance level access. You can also bring an instance down if one of the applications has database issues without affecting the other instance. There can be issues if you don't set up the instances correctly though. Be sure to use a set memory size for each instance and have both patched.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
delpiero
Yak Posting Veteran
98 Posts |
Posted - 2005-04-07 : 22:30:55
|
| Thanks for the reply. I have one question about applying patch. Assume we have 2 SQL Server 2000 instances on a machine. If we are to apply SQL Server patch (e.g. 3a) on ONLY ONE of the instance, we would stop the services for this instance and apply the patch. Do we need to stop the services for the other instance? I don't think we need to reboot after the patch applying finishes. So, is that the services provided by the other instance would not be affected? Also, if we apply patch only on one instance, is that it is completely isolated from the other instance? I mean is that the other instance won't get affected in any way. Thanks,delpiero |
|
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2005-04-07 : 23:15:09
|
| One thing you shold be aware of is that SQL Server doesn't share memory across instances. The memory within an instance is available to all databases, so there is better allocation of memory buffers for maximum total throughput with a only single instance.CODO ERGO SUM |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-04-07 : 23:24:09
|
| You don't need to stop the other instance for that particular patch because it doesn't require a reboot. The other instance isn't affected. The patch only applies to the one instance. If you don't have both those instances already up to 3a though, you need to get them there quick.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
delpiero
Yak Posting Veteran
98 Posts |
Posted - 2005-04-08 : 00:06:35
|
| The existing instance is already on SP3a. I am planning to install a new instance on the server and apply SP3a. I was just asking about the future service packs. Is there any known problem/bug/issue if the patch levels of the instances on the same server do not match?Thanks,delpiero |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-04-08 : 01:02:57
|
| NoMeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
|
|
|
|
|
One instance with many databases VS Many instances