Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

To Create or Not Create new instances

Posted on 2008-10-13
4
Medium Priority
?
216 Views
Last Modified: 2012-05-05
We are currently using Sql Server Standard Ed. Database Eng. for :
-Data Processing: (moderate-high daily transactions, weekly uploads for Report Processing)
-Data Storage: (weekly transactions, source for ReportProcessing)
-Report Processing: (moderate daily transactions [queries], load into non-sql Reporting Software)

1. Related to licensing, overhead [maintenance]) for the above, would it be better to have multiple instances of Sql Server or just one instance?

2. If leave in same instance, best way to manage databases, tables, indexes (partitioning? views?)

0
Comment
Question by:ND_2007
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
4 Comments
 
LVL 143

Accepted Solution

by:
Guy Hengel [angelIII / a3] earned 2000 total points
ID: 22706695
it's quite a broad/vague question, but anyhow:

1) it does not matter, in regards to licensing. either you license the end-users/devices (CAL) or the CPU (processor license).
what does matter is how you configure/share the memory usage between the 2, because if you allowed both instances to use all the memory, you will be both instances to crawl like dogs due to paging...

when to use multiple instances, hence: when you NEED to have several instances for different versions/service packs (at least, that is the only real reason I know of)


2) here is where it is vague, or in short has nothing to do with single or multipe instance stuff.
database implementation needs to gather lots of information about the data itself (amount, usage) to know what will be best.
partitioning is a nice feature, but you won't use it on all the tables.
indexing is REALLY a basic feature, but putting indexes on all fields/field combinations is overkill...
views/functions are useful to reduce code, but can be peformance killers...



0
 
LVL 1

Author Comment

by:ND_2007
ID: 22712687
Thanks angelIII for your response, apologies if question not very clear.

Okay here is better explanation of what we are trying to accomplish I hope.
-We want to make it so when you log into sql, you only see production databases or reporting databases.
-Want to allocate resources for production more than reporting
How can we accomplish this is the most efficient manner?
0

Featured Post

Will your db performance match your db growth?

In Percona’s white paper “Performance at Scale: Keeping Your Database on Its Toes,” we take a high-level approach to what you need to think about when planning for database scalability.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
Ever wondered why sometimes your SQL Server is slow or unresponsive with connections spiking up but by the time you go in, all is well? The following article will show you how to install and configure a SQL job that will send you email alerts includ…
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.

671 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question