Upgrade path to add SQL Server

HCHTech

Well-Known Member
Reaction score
4,225
Location
Pittsburgh, PA - USA
I have a growing Chiropractor client. Their current server is SBS2011 Standard and will be 3 years old in January. When that server was installed, they had 6 employees. They have a practice management software that currently runs in an instance of SQL-Express.

In the past year, they have grown to 14 employees, and performance of the practice management software has suffered greatly because they have outgrown SQL-Express (It has a maximum usage of 1GB of RAM per instance). The rest of the server is not working hard. They only use 3 email addresses in Exchange for the management users.

The vendor's recommendation is add SQL Standard to remove the RAM limitation.

I believe I'm correct that SQL-Standard cannot run on the same box as SBS2011, so I'm wondering what the best recommendation would be for them.

The SBS box is a single Opteron processor with 16GB of RAM, a 2TB RAID1 for the OS, and a 2TB RAID5 for the data. They've got about 700GB used on the OS volume and 1.2TB used on the data volume. They have a procurve switch with a 10Gb connection to the server. The rest of the network is Gigabit.

Of course, they see patients 6 days a week, so we're looking at a Saturday night through Monday morning install window for whatever solution we propose.

We could just put in a 2nd server for SQL and leave the SBS box as the DC, but I think there is a compatibility issue surrounding which OS is on the SQL box. If we can still get the Premium add-on for SBS2011, we might build a new box to virtualize both servers - but that is out of my wheelhouse for sure.

They have money to spend, but this was kind of a surprise, so I don't really know if we'll have budgetary limitations or not yet. I think they are waiting for me to quote a solution before weighing in.

How would you approach this upgrade?
 
You can install SQL Server on a DC, BUT...it is against "best practice"...and for performance purposes, it's best to not have it on SBS. SBS is bloated and very CPU and RAM intensive already.

I recommend a second server...just for SQL. I have many clients that have been (or are still on) SBS....and I have one or two or three or more additional member servers.

You can have a separate physical server to install it on, or...beef up existing server ...and skin it with hyper-v....virtualize SBS and the second server for SQL. Just...plan those disks well...spread out the virtual disks across separate spindles, beef up rammage.

Stick to volume licensing...and you can install prior versions of Windows...gives you good flexibility. Getting a volume license for Server 2012 R2 Standard may be a good idea, since it gives you room for upgrades down the road...a good investment.
 
Out of interest what hard drives does the server have? You might find that the issue is with them and not the memory limit
 
Thanks, YOSC - I think the 2nd physical server will be the quickest to install and minimize downtime. I'd love to get into virtualization more, but need to do that on my own nickel, not for a high-volume client.

The drives are enterprise seagate SAS, I believe. I didn't put the server in and haven't taken it apart to see as they never seem to close, so it's in use pretty much 24/7.
 
Thanks, YOSC - I think the 2nd physical server will be the quickest to install and minimize downtime. I'd love to get into virtualization more, but need to do that on my own nickel, not for a high-volume client.

Yeah, and it will be the an immediate performance benefit. Assuming that the existing 1 gig limit is the cause of the problem...which support should be able to tell for sure. And even if not, SBS is a memory and CPU hog...and so is SQL...and SQL does not like to share. SBS already has Exchange, and quite a few native SQL instances..plus all the other infrastructure roles.

You could do a pretty good physical server for the SQL box without a ton of money, get a 6 or 8 core Xeon, 32 gigs of RAM, 4x 10k or 15K drives...pair of 300 RAID 1 up front, pair of 300 or 600 on the back end for the data. If the client wants a rip roaring system, stick a 3rd pair in...for yet a 3rd volume, just for the SQL logs. (but at under 20 users...I don't see the need for that yet).
 
Yeah we had a client in the exact same situation about 2-3 years ago. SBS2011 and an accountancy/practice management package using SQL.

Set them up with a 2nd server using the premium-add on. Still using it now and works great.
 
Back
Top