[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

Letting others to use my SQL Server and DBs

Hello experts,

I need some guidance and ideas about how to efficiently open my SQL Server data to be used by other people/teams. I have heavy read/write on my SQL Server as a part of the operational routine but that data is also required to be read (and used for reporting) frequently by others.

Any suggestions how I can address that?

I am thinking of in the lines of limiting transactions per one user, limiting concurrent connections for that login or at all possible, reject query requests based on real time statistics of my server (like high I/O, high CPU/RAM Usage, etc) Any of those ideas possible?

What is the best practice?

Thanks in advance
0
bozer
Asked:
bozer
  • 3
  • 2
  • 2
  • +2
1 Solution
 
Nico BontenbalCommented:
How about setting up a second SQL Server and replicate your data to that server. Then you can do the reading/reporting on that replicated server. That way heavy queries can never interfere with your read/write operations. Only extra load on your server will be for the replication but that load will be predictable, unlike the reporting load.
0
 
bozerAuthor Commented:
Hi Nicobo, thank you for your suggestion. Unfortunately, that is exactly what we are trying to avoid because of the second software/hardware cost and also not-so-up-to-date data.

I want to limit the 3rd party teams' impact on my server as much as possible. And still be able to provide the most updated data without jeopardizing the health of my server operations.
0
 
QuinnDexCommented:
you can replicate to the same instance new database, which cancels the cost, it wont reduce the load on the server but will reduce the load on the database ie table locks etc.

you haven't mentioned what your server setup is but if you put the replicated database on a different physical hard drive you will cut down i/o problems considerably
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
QuinnDexCommented:
sorry forgot to cover the up to date data point you raised

you can do transactional replication which is real time so data is up to date

here is a step by step guide on how to do that

http://www.databasejournal.com/features/mssql/article.php/1438201/Setting-Up-Transactional-Replication-A-Step-by-step-Guide.htm
0
 
tigin44Commented:
In your case replicating data to a secondary database and directing users to that database will be the preferred solution as suggested above post.  If you don't want to use a replicated database then you may use the policy based management. Here is a detailed explanation of policy based management

http://blog.sqlauthority.com/2009/06/30/sql-server-2008-policy-based-management-create-evaluate-and-fix-policies/
0
 
Nico BontenbalCommented:
I've never used it but it looks like the Resource Governor could also help solve your problem:
http://technet.microsoft.com/en-us/library/bb933866(v=sql.105).aspx
But it's only available in the Enterprise edition.

When you use QuinnDex's suggestion you can also limit the Memory and Processor resources for the second (reporting) instance in the Server Properties.

Depending on your reporting needs SQL Express might be sufficient for the replicated server, that way the software costs are minimal. You could also try to set up the replicated database in the cloud (Azure, AWS) and only pay what you use.
0
 
Scott PletcherSenior DBACommented:
If you license SQL by CPU, I suggest adding another SQL instance to your current server.  You could then replicate data to the other instance while limiting its CPU and memory use.

This also insures that the other instance's activity has no direct affect on your main instance.

If you need to, add RAM to the existing server.
0
 
bozerAuthor Commented:
Thank you for all your suggestions. The replication, additional instance ideas are good ones but I do not want to take that approach since all I am trying to do is to provide a safe path to a third party team into my server - not to increase scope of my part.

I checked the Policy Based Management, it does not help in my case I believe. But The Resource Governor may be what I am looking for.

I will keep you updated soon.
0
 
bozerAuthor Commented:
After a little bit of research, I realized SQL 2008 new 'Resource Governor' is exactly what I am looking for.

Thank you for all suggestions.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 3
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now