September 10, 2003 at 3:41 pm
Any admins out there running multiple instances? How do you get Vendors to understand instancing when it comes to support questions? Every database we have runs on its own SQL Server box each with a default instance of SQL on it and only 1 user database. What a waste! But the sales/support reps of the vendor apps don't seem to understand instancing.
Any Help?
September 11, 2003 at 9:47 pm
Come on. Come on. There are a lot of brilliant people out here. Don't be shy.
Steve Jones - say my company was looking to purchase some JD Edwards CRM or ERP application and we had this large multi-processor SQL Server just waiting (yeh, right!) with enough excess capacity to handle the load. How would I get past your marketing/sales staff telling me "we require a stand-alone SQL server" (which I'm sure they wouldn't)? Surely you'd set the record straight with your staff. 😉
Brian Knight - holding a web cast using VMWare's product to create multiple virtual "stand-alone" servers on 1 physical server. How would you approach a JD Edwards vendor saying "we require a stand-alone server" knowing your SQL Server was only running at 2% usage and had more than enough horsepower for the new app?
Surely there are others out there who have moved beyond 1 app, 1 SQL server, 1 instance. How do you get application vendors to see beyond the "sales and marketing" specs and into the actual technical requirements?
September 12, 2003 at 5:59 am
I've been lucky(?) enough not to run into this so far. I'd rather run a single instance unless the security needs of the app would preclude that. For instance, recently I needed to host some replicated content with another company - they put up a named instance so that I could have SA access rather than call them each time. Perhaps not the best example and not quite answering your question. My strategy on all purchases is to make sure that we're buying something that works for us. Most times if you push, they'll bend - they want the sale.
Andy
September 12, 2003 at 7:01 am
Andy,
So then your configuration would go something like this: 1 SQL Server, 1 SQL Instance, multiple databases from the different vendors' applications?
How would you track performance items to determin which apps/databases are consuming resources?
BTW thanks for responding.
September 12, 2003 at 7:58 am
We have consolidated the SQL Serves for CRM application. We created named instance to host databases for both DEV and QA for the CRM applications. It is not recommended, probably not supported by vendor. The server also hosts databases for other applications in default instance.
It is strictly database server and no application components allow to be installed in it.
You can use performance monitor, servr task manager and SQL Server profiler to trace the performance of server, processes and databases.
September 12, 2003 at 9:22 pm
Partitioning to get perf data seems extreme, but I honestly haven't thought it out yet.
Andy
September 13, 2003 at 10:39 am
Paritioning makes sense in some cases. Not sold on it for the main db, but for cases where you can "archive" data, moving some of it makes sense.
For instances, you have to pay a license for each Standard instance, so I'm not sure about the benefits. The cost of a server may be low compared to support issues. If you have enterprise, then thre's no additional license cost.
The other place where instances can help with vendors is when the app requires a lot of tempdb useage. Multiple instances allow you to separate tempdb for different apps.
Steve Jones
http://www.sqlservercentral.com/columnists/sjones
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply