Moving DB to existing server, what to check?

Hi all,

this is some kind of "what would you do" question.

There's a one box installation of a repository system with IIS, a worker engine and SQL Server. Now there's the request to split the system and put the database onto an existing SQL server to free up the license on the 1st one.

So, what would you check to find out if you can place the database on another sql server which already exits in your environment?

Regards Dirk

asked Sep 24 '12 at 11:24 AM in Default

DirkHondong
1.3k ● 7 ● 14 ● 17

Thanks Magnus, Grant and Jonathan.

Now I have the problem that all three of you gave great answers and I don't know which one to choose as "the" answer. :-)

Sep 25 '12 at 09:26 AM DirkHondong

I'd go for @Magnus or @Jonathan. I only added a little. Probably should have been a comment.

Sep 25 '12 at 10:11 AM Grant Fritchey ♦♦

yep, you're right. I often overlook that button

Sep 25 '12 at 10:12 AM DirkHondong

(comments are locked)

3 answers:

Compatibility
- compare old and new OS, IE, .Net, other apps etc and make sure they are all compatible

Performance
- Does the existing SQL Server have a predictable trace on CPU, HDD and RAM that will fit within what is currently unused on target server?

Security
- Users, Shares, Admins, Applications, Roles all need to be compatible with target server. cross over of accounts between source and destination could leave a gap for a data breach

Backups/DR
- does the destination server have the right DR/backup infrastructure to cope with your new system

Other systems
- does the destination server have bespoke systems installed or does the source server have them, so meaning they will need to be installed on the destination. Will this cause problems in any way

Probably a few more but this list should get you thinking :)

answered Sep 24 '12 at 12:26 PM

Fatherjack ♦♦
38.8k ● 55 ● 69 ● 104

(comments are locked)

Check SQL Server versions and editions. If they differ, check that you don't use code or functionality which won't work on the new machine (compression etc) Look at network infrastructure between the two machines is good enough to handle the throughput between app and DB. Look to see that the DB machine has enough memory and disk. If you want to be sure that the DB gets enough dedicated memory you might want to put it in its own instance.

answered Sep 24 '12 at 11:36 AM

Magnus Ahlkvist
13.7k ● 13 ● 17 ● 30

(comments are locked)

In addition to @Magnus excellent set of checks, I'd want to be sure of the existing transaction load on that other server and what the anticipated load of the database you're moving will be (what it is currently). This could be a major problem, depending.

answered Sep 24 '12 at 11:48 AM