I've always heard it best to keep processes separate when dealing with Application servers etc. My question is this:


Are there any best practices associated with creating a website that queries a SQL Database?


My thought is to separate the web element from the SQL Server and host it on it's own due to having 4 intranet sites total and the load it is imposing on our SQL Server.

Thanks in advance for any information.

Up to you, but you would be AMAZED at the abilities of Microsoft SQL... 4 sites probably isn't that taxing. Some shared hosting providers have (literally) hundreds of SQL databases serving hundreds of sites...

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.