current community

your communities

more stack exchange communities

company blog
Stack Exchange Inbox Reputation and Badges
tour help
up vote 1 down vote favorite
1

We have a server running single instance of SQL SERVER in production environment.

We are planning to create another Instance of SQL SERVER in same server.

My question do we have to buy a new license or the existing license is good enough ?

share|improve this question
up vote 3 down vote

You can install as many instances of SQL Server as you like on a server, up to 50. The licensing is by the server, not by the instance (it used to be, once upon a time) so you have some freedom to do so.

The real question I would counter with is: Do you need another instance? Most people don't.

share|improve this answer
    
We have both UAT and Prod in single server. Load on UAT should not impact the performance of PROD. So we plan to split UAT and PROD into two different instance so that we allocate even amount of resources(memory) to both UAT and PROD. Is this a correct approach ? Actually this is my real question and problem – Prdp 22 hours ago
    
Well, there will be a perf impact if UAT ever does actually start to use load. I would prompt you to install the developer edition on the UAT server and set up another UAT server specifically to keep the databases separate. I don't believe that using developer edition violates the TOS for UAT, but I would need to defer to one of the other site SQL Server experts to make sure of that licensing question. In this case, I would think it's acceptable, as it is for development and not for production usage. – jcolebrand♦ 22 hours ago
    
Nobody ever expects UAT testing to overload production, but you have to remember this is an environment where code may have issues, so you may have bad queries that read too much data into cache, or that don't evict data appropriately, and for any of a dozen reasons actually do impact production. While you can do what you're suggesting, it's not recommended from a professional standpoint, and managing two servers is as easy as managing two instances. – jcolebrand♦ 22 hours ago
2  
"Other than this is there any other problem I should be aware of?" - Consider CPU, disk usage, disaster recovery (DR), the high likelihood of accidentally deploying data or code changes to the wrong environment, eg data fix to live you were meant to test in UAT. – wBob 21 hours ago
3  
Have you heard of Azure or AWS? Consider creating your non-production environments in the cloud. It could potentially be quite cheap, avoid overload on your server, maintain a healthy degree of isolation between your environments and prevent any unintended consequences. The elasticity of the cloud will allow you to power down your environments when not using them, thus not incur additional cost. – wBob 21 hours ago
up vote 1 down vote

Why would you want to have Prod and UAT on the same server? The best way to segregate UAT's workload from Prod is to have a dedicated server for each. It's safer and more convenient to separate them.

I'm almost positive UAT falls under development use so you wouldn't incur any extra cost to spin up a new server.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.