Maximum rows in SQL Server Express 2008 / schema recommendations

Posted on 2010-01-08
Medium Priority
Last Modified: 2012-05-08
I have a c# windows application which tracks the time it takes to assemble widgets on a production line.  The line is given a job to do which specifies which widget and how many to assemble.  The job completed by one or more assembly sessions.  The job being closed when the final session completes the last widget. For each session the average number of seconds to complete a widget is stored.    So I have a table Job and associated table Session.

The customer wants more granularity.  Instead of the average seconds per session they want to know by hour so they can compare the average time from 8:30 to 9:30 Monday to the same time on Tuesday.

To give them the ultimate granularity I am considering creating a table Assembled with the fields SessionID, CompletetionDateTime and Seconds.  With up to ten jobs running simultaneously and each job completing up to 1000  units a day this could result in 10,000 rows created daily.  Should this be a concern?  Each row will be small but I am concerned about performance impact etc.

Grateful for any input!
Question by:canuckconsulting
LVL 21

Accepted Solution

JestersGrind earned 668 total points
ID: 26209380
10k over the course of a day is not that much.  Of course, it depends on the server that it's running on.  So, performance shouldn't be an issue, but you may eventually run into storage limits unless you occasionally prune old data.


LVL 15

Assisted Solution

by:Faiga Diegel
Faiga Diegel earned 668 total points
ID: 26211325
I never heard of maximum limit rows in SQL 2008 Express edition, but take in consideration that Express edition can only be upto 4 GB of file size. adding 10K per day, imagine how much data would that be in a year (not including the "real/production" data). So do archiving or deleting old records to trim space.

Assisted Solution

tsells earned 664 total points
ID: 26245870
I would say it really depends on what type of data you are storing.  If you are not storing any binary or nvarchar type of data you should never have a problem.  You are looking at 3 million records per year.  If you have a decent server and properly formed indexes / queries to retrieve and store the data then you are fine.  Stored Procedures may be best for you.  

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this blog post, we’ll look at how using thread_statistics can cause high memory usage.
Backups and Disaster RecoveryIn this post, we’ll look at strategies for backups and disaster recovery.
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB. To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…

850 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question