limitedburan

• • Find product guides, documentation, training, onboarding information, and support articles. • • • Submit a ticket for technical and product assistance, or get customer service help. • • • • • Learn through self-study, instructor-led, and on-demand classes with the SolarWinds Academy. • • • Download the latest product versions and hotfixes. Manage your portal account and all your products. • • Renew to download the latest product features, get 24/7 tech support, and access to instructor-led training.

My company is working on a development project using SQL Server 2008 Express. The amount of data we plan to store in our main table will quickly exceed the 4GB size limit of Express. X Art Marry Queen on this page. We can buy ourselves some time with SQL Server 2008 R2, but eventually we will surpass the 10GB limitation as well. The team lead wants to hear all available options before purchasing licenses for Standard Edition. The expertise available in our company is SQL Server and Oracle, so using MySQL or PostgresSQL would be considered a last resort.

The only alternative I can think of is a design where the main table is horizontally partitioned into separate, distinct databases. In addition, there would be a central database to store the information about where the data was stored. For example, all of the table data for 2008 would be stored in DB_2008, 2009 data in DB_2009, and so on. The metadata table might look like this: PKStartDate PKEndDate DBName ----------- ---------- ---------- 2008--12-31 DB_2008 2009--12-31 DB_2009 2010--12-31 DB_2010 This table would be used to determine the database location of the data for our stored procedures.

Most of our code already uses parameterized, dynamic SQL, so this would not be difficult to implement. Has anyone ever done this before? Is there an established model for this type of design or is it just a horrible idea?

Nov 02, 2011 Is there a way to find max allowed size of the database? The limit is 4GB for SQL Server 2005-2008 Express and. Trying to hack the limits. I am confused. AFAIK SQL Server 2005 Express has a limit of 4GB database data size. However I have the following results from sp_spaceused: How can I check if my DB. Is SQL Express enough? The stated memory limit is for the buffer pool only. There are actually no connection count limits with SQL Server Express. How to check if I am hitting the Express Edition size limit? Only the actual data and indexes count towards the SQL Server Express limits.

I realize this doesn't address your question exactly, but in my experience it's always more expensive to hack up a nasty kludge like this--think dollars per hour for development and maintenance, plus the time you've lost developing features that really matter--than to buy the right tools in the first place. EDITED: And why Standard edition instead of Workgroup?

If Express satisfies your feature requirements, so will Workgroup, and it's ~$3500 cheaper than Standard. Still, either is a bargain compared to saddling yourself as described above -- doubly so if you can license by CAL instead of by Processor.:-). The only way I would consider doing anything like this is if I was guaranteed that • reports wouldn't cross those boundaries, and • when querying data, the user would be limited to current year. The reality is that those constraints rarely work.

Consider someone wanting a 12 month report in march, from the previous march. You'll have to aggregate the results in code. At the end of the day you are going to spend a LOT more in development time making this work than a sql standard license will cost you. EDIT: I take that last sentence back: it will cost more to do than a sql enterprise license would.