September 25, 2005 at 10:47 pm
Hi,
Is anyone aware of liscening requirements for MSDE regarding a single application using multiple databases?
What happens in this application will fill up one database and when it has reached that 2GB limit it will create a new database and fill that one up and then when finished that will create a new one and fill that up and keep going...
Does this breach the Microsoft liscence for MSDE?
September 26, 2005 at 12:37 am
I don't think new database will be automatically created when you get to the 2gig limit. All the detailed info about MSDE and other SQl Server editions are covered in Maximum Capacity Specifications. Runs a search for Maximum Capacity Specifications in the BOL (books online). Hope this helps.
Kind regards,
Gift Peddie
Kind regards,
Gift Peddie
September 26, 2005 at 12:40 am
The application will create a new database when the current one hits 2GB.
September 26, 2005 at 12:52 am
I would not let an application create a new database for my users, I would check and shrink the database as needed by running DBCC Shrinkfile and create a new one when the current one grows to 1.7gig so you will not loose data. Hope this helps.
Kind regards,
Gift Peddie
Kind regards,
Gift Peddie
September 26, 2005 at 7:58 pm
Ok thanks, I was more after if this is ok within Microsoft liscense for the use of MSDE as far as I can see it is ok to do this?
September 26, 2005 at 11:41 pm
See: http://www.microsoft.com/sql/msde/howtobuy/redistregister.mspx
I think you'll find that while the *number* of databases held in MSDE is not an issue, the other limitations (such as concurrent connections etc...) will affect you.
If your databases are growing that large, why are you not considering SQL Server?
September 26, 2005 at 11:44 pm
The databases hold documents, a large amount of documents that take up a lot of room. (this is not my application by the way ) It won't have many users but a large amount of data.
September 26, 2005 at 11:47 pm
The concurrent users issue is only related to write users not read, people have tested MSDE for more than 2500 read users. Hope this helps.
Kind regards,
Gift Peddie
Kind regards,
Gift Peddie
September 27, 2005 at 9:19 am
As far as I know this is not true - 5 concurrent users is the limit at which MSDE starts throttling back its performance. The more concurrent CONNECTIONS to the server the slower it gets.
The DBCC command with CONCURRENCYVIOLATION (or something like that - see BOL) lets you know how often you have exceeded the number of concurrent connections.
If you have used connection pooling, etc and are running your app via an application server (eg web server or other n-tier arrangement) you could have up to 20-50 users using MSDE with no noticable drop in performance because the same few connections are being pooled.
No distinction is made between readers & writers though - please correct me if I am wrong though as it would be useful to know....
And - back on topic - I have hit a similar issue with my app this very evening and will be "spilling" over into a seperate database. I don't think MS have a problem with it. At the site in question, we have 3-4 users using the documents database but they have been VERY busy scanning over the past couple of months. For the couple of users, full SQL is hard to justify...
September 27, 2005 at 10:09 am
Read this thread for Microsoft own documentation and how you can get more out of MSDE. Thona knows how you can get more out of MSDE. Hope this helps.
http://forums.asp.net/612379/ShowPost.aspx
Kind regards,
Gift Peddie
Kind regards,
Gift Peddie
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply