February 4, 2016 at 1:03 pm
Hi Guys,
Could you please give some guidance on selecting hardware for a new DB server. This will be a new Operational Data Store setup. Expecting moderate ETL load (SSIS on same db server). We do not have an expected workload/db growth at this point. Due to time constraints, we need to make a quick decision on selecting hardware/resources.
Any guidance is much appreciated.
Many thanks!
February 4, 2016 at 1:09 pm
So the initial size may be anything from 5MB to 200TB?
And the growth can be anything from none at all to 5000 Yottabytes per hour?
And you probably have no information about number of users and expected workload either?
My recommendation would be to buy a server and install a version of SQL Server on it.
If you / your managers need more specific advice, then they'll have to provide more specific information.
February 4, 2016 at 1:12 pm
PS: Yes, I know that was blunt. Please pass it on unchanged to whoever asked that question of you.
If you give a recommendation and it backfires, it will be your *** on the line.
If a manager gives you some projected numbers and you make a recommendation on that, it will be his/her *** on the line if the numbers are wrong.
A lot of managers shy away from making choices because that exposes them to risk. But they have no issue raking in their salary, that is higher because they are expected to take more responsibility. So I have no issue making sure that they take the responsibility they are paid to take.
February 4, 2016 at 1:16 pm
SQL!$@w$0ME (2/4/2016)
Hi Guys,Could you please give some guidance on selecting hardware for a new DB server. This will be a new Operational Data Store setup. Expecting moderate ETL load (SSIS on same db server). We do not have an expected workload/db growth at this point. Due to time constraints, we need to make a quick decision on selecting hardware/resources.
Any guidance is much appreciated.
Many thanks!
Consider using a cloud server: AWS, for example. You can start small and scale as necessary, without all the costs associated with buying a fixed piece of hardware and then finding that it's too small (or too large).
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
February 4, 2016 at 3:06 pm
Thanks!
February 4, 2016 at 3:06 pm
Thanks!
February 4, 2016 at 3:47 pm
SQL!$@w$0ME (2/4/2016)
Hi Guys,Could you please give some guidance on selecting hardware for a new DB server. This will be a new Operational Data Store setup. Expecting moderate ETL load (SSIS on same db server). We do not have an expected workload/db growth at this point. Due to time constraints, we need to make a quick decision on selecting hardware/resources.
Any guidance is much appreciated.
Many thanks!
First thing to clarify, what storage intentions do you have for this server, SAN or local?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 4, 2016 at 4:02 pm
It should be SAN. There will be only one DB. This DB will be eventually moved to SQL Azure.
February 4, 2016 at 4:06 pm
ok, so space wise you have no worries, as it's SAN presented you can grow the storage at will.
You're planning for a physical server then?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 4, 2016 at 4:10 pm
Hi Perry, I recommended to go with Physical since we had some VM issues recently.
Was looking similar to HP ProLiant DL380/DL180 Gen9 racks. Active/passive clustering for HA.
But I need to justify why we are choosing this option. This database will eventually be moved to cloud(SQL Azure). Not in the near future. Thanks.
February 4, 2016 at 4:25 pm
you will almost certainly be expected to justify for spending then money on physical tin, don't forget it's not just the cost of the server but the on-going maintenance costs, virtualisation saves on costs and power and rack space.
However, how well designed and configured is your Virtual Infrastructure?
VMs make great and I have worked on past projects where we virtualised practically a whole SQL Server estate with exceptions for some (such as GIS) as these were heavy hitters and hardware only IMHO.
Storage is a weak point with VMs even when using RDMs, again depends on the storage tier(s) backup up your datastores.
There's nowhere near enough information here to give a completely informed decision. At this point, your suggesting an expert be brought in on a contract basis may be a good idea. You'll need someone who can communicate at all levels from junior DBA to board members to get everybody on board with your ideas (which of course you can ratify with your contract SME resource). Knowing when to get the right help engaged is a great benefit, it's not a sign of weakness
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 4, 2016 at 4:35 pm
Thanks Perry.
Our VM Infrastructure is poorly designed (ESXi 6.0).
I have the option to start with VM and move to Physical if required.
If we go with VM, do you have any recommendations on how this should be setup (VMWare best practices).
Thanks!
February 5, 2016 at 2:57 am
VMware have a BP document on their website, google and you're sure to find it
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 5, 2016 at 9:43 am
I'm at the point where I want to try to specify VMs for everything SQL. It's so much easier to add/remove CPUs/RAM as necessary and depending on how complicated your server builds are, in development especially, it's much easier to snapshot a few versions of the VM as you build it, so there's no need to start from scratch with re-installs if you have a problem.
We're on a project now to move GIS from physical to VM/Citrix servers with host graphics cards. Maintenance is so much easier in the VM world. YMMV.
February 6, 2016 at 1:09 am
C Schaefer (2/5/2016)
it's much easier to snapshot a few versions of the VM as you build it, so there's no need to start from scratch with re-installs if you have a problem.
Be mindful with snapshots to only keep them short term, also reduce the number of snapshots you take
quote]C Schaefer (2/5/2016)
The GIS system I worked on was huge, we would have given any potential VM a large percentage of the host resources, at this point you know it needs to stay physical.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply