Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 223
  • Last Modified:

To Create or Not Create new instances

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
ND_2007
Asked:
ND_2007
1 Solution
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
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
 
ND_2007Author Commented:
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

Ask an Anonymous Question!

Don't feel intimidated by what you don't know. Ask your question anonymously. It's easy! Learn more and upgrade.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now