Maximum rows in SQL Server Express 2008 / schema recommendations

Posted on 2010-01-08
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

    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

    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.
    LVL 5

    Assisted Solution

    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

    Top 6 Sources for Identifying Threat Actor TTPs

    Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

    Join & Write a Comment

    This article describes some very basic things about SQL Server filegroups.
    Entity Framework is a powerful tool to help you interact with the DataBase but still doesn't help much when we have a Stored Procedure that returns more than one resultset. The solution takes some of out-of-the-box thinking; read on!
    Video by: Steve
    Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
    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…

    728 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

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now