August 19, 2014 at 7:03 am
I'm trying to see if any one has attempted to use SQL Server Express to manage other Databases across an Enterprise. For a little background, the company I work for hasn't been eager to purchase the needed licenses for all the Database initiatives being tossed my way. Our current answer so far is going to be to go with a Hybrid Cloud provider (Rackspace, VMWare, and AWS are in mind), since they offer instances with SQL Server Standard licensing included in the cost of the VM's. To minimize on cost, I'm planning on having a management box, (I currently have a task box in windows do perform different maintenance and business tasks) with SQL Express installed. I currently use the Ola Hallengren scripts to perform a lot of my maintenance, and I want to be able to log printed information to a network folder. Since I already use Task Scheduler to run maintenance tasks, I don't see any problem with not having access to SQL Server Agent.
Anyone see any gotchas with my architecture?
Appreciate the feedback.
August 19, 2014 at 7:49 am
hiramjamador (8/19/2014)
Anyone see any gotchas with my architecture?
Apart from the resource limitations?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
August 19, 2014 at 8:26 am
I'm really trying to get my hands on SQL CMD. I'm thinking of having each of my databases loaded with a utility database, which will have the hallengren stored procedures installed. And I want to output the print out to file share, so I would be using SQL CMD to connect to the different servers to perform maintenance and output the print message from the hallengren sp's to a network log folder.
I don't really need the engine on the management box.
And the reason I'm not using SQL Server Agent is to minimize downtime in case there is a network failure in the cloud provider we use, or the host or Blocks fail that are used my the database VM. I'm planning on using mirroring for our production databases, and having the mirror in a different data centers that the primary (in AWS this would be different availability zones with the same regions). If a separate box is performing maintenance, (which can be we can periodically take a snapshot of), nothing would stop us from performing a manual or forced service failover in an emergency. The extra step of reloading msdb in an emergency situation is averted. I could be wrong, but the less steps you have to do in a disaster scenario, the less likely you are of making a mistake. I do realize an argument can be made for scripting a reload of the system databases as part of the recovery process.
The reason I'm not using AlwaysOn Availability Groups, is simply because of the cost of running enterprise. I'm trying to get the business to stay on the ball with licensing, and it seems that it's easier to lease VM's in the cloud that include standard licensing as part of the cost of the cloud VM, easier to justify in our corporate culture anyway.
Thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply