March 7, 2008 at 7:13 am
Hello,
I was asked to provide pros & Cons of running a MS SQL Server 2005 on one hardware (VWare) for multiple groups of DBA's. The idea is to cut down the cost of server,maintenance etc...
The proposed plan was,
1) One big hardware with SQL Server 2005 standard edition installation
2) Systems administrators manage the server (install service pack,patching,manage backup files etc)
3) DBA's will not be allowed to logon directly to the server but through client management Studio to create and manage databases
my questions,
1) How can a database is segregated from other group of DBA's (even though we share a hardware I don't want other group of DBA's look at my databases and vice versa)
2) How do I prove this is not a best practice to manage the sql server 2005
3) What is deal with license if we run SQL Server 2005 on VMware ?. Say one big hardware but multiple SOL Server installation by using VMWare (multiple domain) ?
Please provide 5-10 bullet points for this pros & cons. I really appreciate your help in advance.
March 7, 2008 at 7:50 am
- if only hardware is your concern, maybe you should opt for a number of named instances of sqlserver.
With WSRM you can "guarantee" a percentage of processor(s) to any single sqlserver instance.
- db-dba role seggregation :
* this way your dbas cannot be sysadmin ! and they will loose
the ability of a bunch of management tools.
* this would make a dba restricted to db_owner db role.
* Are you going to allow the dba to run sqltraces ?
(will affect other instance users)
* the databases will share the memory of your sqlinstance.
meaning if one db-users runs a query, it may block your full
sqlinstance (cpu/io/tempdb)
* how are you going to handle sqlagent jobs ?
* Do your system engineers have sql2005 dba knowledge ? to check upgrades, support performance troubleshooting, ... ???
* if you open clr, abuse of it may bring down your instance
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
March 7, 2008 at 8:00 am
This is the constant battle between System administrators and DBAs. It normally happens when one of the positions is filled by a new person.
DBAs need to have some admin rights to the server, lets say you want to move a database because of disk IO issues and you want to spread it out over several files, can't be done if you don't have permission to copy/move files.
What about backups, sure you can perform and restore them, but again, will you be able to move them when needed.
How can you create folders for databases? Especially when you need to stripe them over different drives.
As for other DBAs, you should share your knowledge by at least letting them have read access, however, I agree, I don't want other DBAs changing my set up without talking to me first, because there is probably a good reason the way I have it set up.
I can't imagine being a DBA without System admin access on the database server.
Marvin Dillard
Senior Consultant
Claraview Inc
March 7, 2008 at 8:04 am
With 2005, it can get interesting licensing-wise with virtualization (Virtual Server, VMWARE, etc..). The cliff notes version is:
- if you're using Enterprise edition AND you've licensed ENTERPRISE edition for each physical processor in the box running the VM's - then you only need one instance of the licenses.
- in every other circumstance - you need to license each virtual instance separately (which would mean counting each virtual proc in each virtual instance if you're using the per proc licensing model).
This does NOT apply to multi-instancing (within the SAME OS instance). EE allows for 50 instances, all others 16 instances on the same OS instance, under a single instance of the licenses.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply