I didn’t until half an hour ago when a customer had a problem expanding their database. Microsoft can not cut a license to allow you to use a database larger than this.
Oh well i had just better move them to SQL then, If only moving a half tera byte database was as easy as that.
Paul Baxter
I think it’s a limitation of native database server, not a license problem.
Check this http://dynamicsuser.net/forums/thread/52073.aspx
I wonder how long will it take for them to move to SQL. And I wonder how big the database would get if they migrate to SQL.
Probably double size of native.
Or also 2.5 times the native size.
Except when the DB is prepared for SQL (Index+SIFT fixes).
The database will be at least twice the size of the C/SIDE one, and you will need to have at least 2-3 times that much space for the initial transaction log when you create the database. It will probably take 3 or 4 days to create a database that big.
Can you imagine the time taken to backup and restore the database.
I don’t think it is possible to tell the customer sorry you can not use your system for the next week or so!!
What we will do is delete old invoices and sales transactions that should release a few hundred gig and they have all the data in a data warehouse and cube for reporting on any way.
Paul Baxter
Even then, the data deletion will take some time to do as well…
Just curious, what line of business are they in that generates 510gb worth of data?
probably retail. We are implementing for a customer that will have such big db. 20K POS transaction per week.
How times change,
I did a performance tuning and training job for a client running on Navision 1.3. (about 10 years ago) They averaged 53,000 sales invoice line per day, and their database growth was “only” about 40Gig per year. Mind you, at that time the Max database size was 32 Gig, but Navision cut a “special” 64 gig license for them.
We are compressing the entries into a single entry per item per week. The actual transaction 1 million transaction per week.