May 14, 2018 at 8:54 am
Hey,
I've been tasked with determining how many cores, how much memory, and how much disk space we'll need for a SQL Server Express instance on a virtual machine, and eventually a sql server standard version when we upgrade? Does anyone have any quick reference on the best scenario there? I dug around for a bit but didn't find a solid resource. Thanks
May 14, 2018 at 9:39 am
brad.estep - Monday, May 14, 2018 8:54 AMHey,
I've been tasked with determining how many cores, how much memory, and how much disk space we'll need for a SQL Server Express instance on a virtual machine, and eventually a sql server standard version when we upgrade? Does anyone have any quick reference on the best scenario there? I dug around for a bit but didn't find a solid resource. Thanks
The limits are at https://docs.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2017?view=sql-server-2017#Cross-BoxScaleLimits
However, what you actually *need* - it depends. What are you doing? How many users? How much data? How much activity?
Thomas Rushton
blog: https://thelonedba.wordpress.com
May 14, 2018 at 11:28 am
We are going to start off with a pilot program for a security camera setup. It will house the data from the camera system, so we are talking a minimal amount of data to begin with. There will be less than 10 users to start with, with less than a gig of data, with little access per day. So I'm thinking of just going for the system maximums for the express database, they're small enough to not be too big of data hogs for the VM environment.
But when we switch to Standard that will be bringing in 4-5 more gigs of data, and will require and will keep growing so I'll need a more articulated system parameters for size, speed, and cores. In this environment we'll have still 10-20 users, upwards of 10 gigs of data, and daily use by at least 10 people. Thanks
May 14, 2018 at 1:18 pm
Have someone knowledgeable about database apps in your IT department check with the vendor(s), they should be able to manage some guidance on the direction to take.
May 15, 2018 at 9:27 am
yeah except I'm not requesting aid with code. And I am that guy, just don't know anything about systems, but will have to learn.
May 15, 2018 at 11:14 am
brad.estep - Tuesday, May 15, 2018 9:27 AMyeah except I'm not requesting aid with code. And I am that guy, just don't know anything about systems, but will have to learn.
Ok sorry to have bothered you, good luck!
May 15, 2018 at 11:43 am
brad.estep - Tuesday, May 15, 2018 9:27 AMyeah except I'm not requesting aid with code. And I am that guy, just don't know anything about systems, but will have to learn.
I believe what Patrick was suggesting is, contact the vendor of the security camera application to find out what they would recommend based on your stated pilot program requirements. They're the ones who know their system and how much it uses CPU etc.
Because, as with many things, and this does sound like a cop-out answer, it depends. It depends on the application on the front end, it depends on how much of the heavy lifting is done on the database side. If all the DB is doing is handling a user table, maybe the user preferences, and saving a URL to saved / recorded video files, then that's a fairly lightweight backend and it won't need a lot of power. On the other hand, if it's doing more, perhaps some reporting, maybe storing the video files in blobs or FileStream, etc, then you'll likely need a more powerful database server.
We here on the forum don't know anything about the application, so any answer we give is going to be only a bit more accurate than if you threw darts at the wall. You need to check with the application vendor, they're the only ones who can give you more than a WAG estimate of what you might need.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply