March 11, 2015 at 2:36 pm
Questions on what best practice / practical practice is. Our financial system software requires that it be installed on the same server as the databases. Currently it has its own server, but id like to combine them into our production database server, but in order to do that id had to install the financial server software on the DB server.
Technical support tells me that even if i could get the database separate from the software that they wouldnt support it.
How do others handle this ? I dont really like the idea of installing this software on my database server, but it would be nice to reduce overhead.??
March 11, 2015 at 3:41 pm
Generally speaking, SQL Server didn't do well in kindergarten. It doesn't play at all well with others.
If you already have an isolated production server and you're considering consolidating this other server with the existing one, I'd only recommend that if you can separate it from the software. If you can't, I'd leave the two as they are. I can count on one hand the number of times I've put software other than SQL Server on the same box in the last 20 years. It's to be avoided.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 11, 2015 at 5:48 pm
Clear as mud, just wanted to confirm my intuition.
March 12, 2015 at 4:03 am
Well, let me know if you want drill down on this. Happy to try to help.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply