Is SQL 2008 R2 coexisting with Terminal Services on 2008 R2 VM, a supportable configuration?
I'm looking at a single, physical Windows Server 2008 R2 server, that is running both Hyper-V (5 virtual machines) and SQL Server 2008 R2. Is this a supportable configuration. I saw a Microsoft article that said it wasn't, but it only applied to clustered environments...this is not one of them.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Having serious performance penalities does not count? A 95%+ memory usage hints towards a dog-fight between the different services.
If it is an existing and running environment, they do not experience significant lags in using anything? If so, then we need to find something else :D.
If it is an existing and running environment, they do not experience significant lags in using anything? If so, then we need to find something else :D.
One of the things to be very concerned about with SQL Server is making sure the data isn't lost if your VM is reset. For instance, going back to an old checkpoint would lose the current data. To minimize the need to do that, one would normally keep the SQL Server in a different VM from other apps.
You'll also want to make sure the SQL Server data is backed up on another machine. Making backups in the VM is not a good idea. Same for another VM on the same machine. At the very least, backups should be on a different Hard Disk. Ideally, offsite as well.
Hope this helps.
You'll also want to make sure the SQL Server data is backed up on another machine. Making backups in the VM is not a good idea. Same for another VM on the same machine. At the very least, backups should be on a different Hard Disk. Ideally, offsite as well.
Hope this helps.
ASKER
Good morning!
I do apologize for the delay in getting back to you folks. Luke, thank you for your input, kind sir. While it makes great sense (and I do agree with what you're saying), it's more procedural and best practice in general, but doesn't specifically answer my question. I was looking for a definitive answer that either supports this environment, or something that specifies it's unsupportable (like having Hyper-V on a DC...that's a Microsoft support-killer for sure, by their own words).
Qlemo and David, I am grateful for your input, which sounds more of an opinion-based observation, but not something that definitively speaks to a Microsoft best practice (see above paragraph). However, I get what you're both stating. Bottom line is that there isn't anything that says this is unsupportable. But in-between the time I posted this question and now, I've found what I needed in order to invalidate this configuration and drive home options for the client.
Thanks so much for your time and patience! Have an outstanding day, guys. :-)
I do apologize for the delay in getting back to you folks. Luke, thank you for your input, kind sir. While it makes great sense (and I do agree with what you're saying), it's more procedural and best practice in general, but doesn't specifically answer my question. I was looking for a definitive answer that either supports this environment, or something that specifies it's unsupportable (like having Hyper-V on a DC...that's a Microsoft support-killer for sure, by their own words).
Qlemo and David, I am grateful for your input, which sounds more of an opinion-based observation, but not something that definitively speaks to a Microsoft best practice (see above paragraph). However, I get what you're both stating. Bottom line is that there isn't anything that says this is unsupportable. But in-between the time I posted this question and now, I've found what I needed in order to invalidate this configuration and drive home options for the client.
Thanks so much for your time and patience! Have an outstanding day, guys. :-)
ASKER
I'm looking for a best practice or unsupported environment argument, to convince this client to pay for moving the SQL server off this host.