• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 674
  • Last Modified:

multiple sql 2008 r2 instances

Best practices stacking multiple SQL 2008 R2 Instances on a host connected to NetApp Mount points.

Any info is appreciated
1 Solution
Ryan McCauleyCommented:
Are you talking about using the Netapp mount points for your back-end storage of the data? Though it's not really clear, I don't believe Netapp does any kind of front-end access, so you must mean doing remote storage.

The best practice for multiple instances of SQL Server is the same as a single instance, except that you add more drives for each additional instance of SQL to keep them separate (though separating the drives doesn't help if they're sharing spindles on the netapp box, so be careful there). In that case, just the standard advice - logs/tempdb on one partition and data files on another (with any highly active data files on their own). Where you'd have 2 extra partitions in a single instance SQL server, you'd have 4 in a two instance, 6 in a three-instance - you get the idea.

Pretty straightforward, but make sure you're putting them on different sets of spindles on the NetApp - you can divide all the data across 100 partitions on your SQL server, but they share spindles on the NetApp, you'll be hurting when the SQL box is under pressure.

Featured Post

Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now