LocalDB over 10GB
I have a LocalDB database that is currently at 9GB, and the application will ultimately consume 20-30GB. Moving to Standard SQL is not an option.
My original plan was to move the largest table (5GB) into its own LocalDB database so that my Access 2010 front end talks to 2 LocalDB back ends. However, the 10GB limit is based on the size of the MDF file. Is it possible to move the big table into a secondary file group stored in an NDF file without having to split the database? If so, is there any limit to the total size of a LocalDB database with MDF file + NDF file(s), each <10GB?
My original plan was to move the largest table (5GB) into its own LocalDB database so that my Access 2010 front end talks to 2 LocalDB back ends. However, the 10GB limit is based on the size of the MDF file. Is it possible to move the big table into a secondary file group stored in an NDF file without having to split the database? If so, is there any limit to the total size of a LocalDB database with MDF file + NDF file(s), each <10GB?
Moving to Standard SQL is not an option.
What about the Web Edition?
However, the 10GB limit is based on the size of the MDF file.
Actually, I suspect you will find that the limit is based on the size of the database and not on the allocated size of the data file. In other words, you should be able to create a file that is 100 GB, you just cannot use more than 10GB.
What about the Web Edition?
However, the 10GB limit is based on the size of the MDF file.
Actually, I suspect you will find that the limit is based on the size of the database and not on the allocated size of the data file. In other words, you should be able to create a file that is 100 GB, you just cannot use more than 10GB.
ASKER
Surendra
Thanks for the MySQL suggestion, I had a look at that. For the time being I just want to get what I have working. However, it may be worth learning for future projects.
Anthony
Microsoft site not too helpful on the Web Edition.
@ the limit is based on the size of the database and not on the allocated size of the data file.
I want to know whether actual NDF file sizes are added to the actual MDF file size to see whether the total is >10GB. I know log files are excluded from the database size calculation.
Thanks for the MySQL suggestion, I had a look at that. For the time being I just want to get what I have working. However, it may be worth learning for future projects.
Anthony
Microsoft site not too helpful on the Web Edition.
@ the limit is based on the size of the database and not on the allocated size of the data file.
I want to know whether actual NDF file sizes are added to the actual MDF file size to see whether the total is >10GB. I know log files are excluded from the database size calculation.
Microsoft site not too helpful on the Web Edition.
I am not sure what that means, but I will take your word for it.
Again it does not have to do with the file size of either the mdf, ndf or whatever you decide to name it, but rather the actual size used.
I am not sure what that means, but I will take your word for it.
Again it does not have to do with the file size of either the mdf, ndf or whatever you decide to name it, but rather the actual size used.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
@Synonyms
This looks really interesting - Synonyms are available in LocalDB.
I plan to move '5GB_Table' to a new database and call it '5GB_Table1', then create a Synonym called '5GB_Table' in the original database. That way no code in the original database needs to change. If, as is possible, I need to create a third database later on I'll use the same method. So my Access front-end will just point to the original back-end as if it held all the data. I'll need to test that everything works before closing the question, but thanks for the suggestion.
This looks really interesting - Synonyms are available in LocalDB.
I plan to move '5GB_Table' to a new database and call it '5GB_Table1', then create a Synonym called '5GB_Table' in the original database. That way no code in the original database needs to change. If, as is possible, I need to create a third database later on I'll use the same method. So my Access front-end will just point to the original back-end as if it held all the data. I'll need to test that everything works before closing the question, but thanks for the suggestion.
You're welcome. That was the easiest, cleanest method I could think of :-) .
ASKER
Sorry about the delay in closing the question - disk space problems held me up.
Yes, it works nicely - I'll add Synonyms to my armoury :)
Thanks for the help, Scott
Yes, it works nicely - I'll add Synonyms to my armoury :)
Thanks for the help, Scott
MS will not allow you to use the express edition to go more than 10 GB of database for free.
incase moving standard edition is not an option.. you can find the below alternatives
1) install MYSQL server (free edition) and migrate all your databases to it as well the code, i.e. the sp's and all..
2) install MYSQL server (free edition) and migrate all your data... keep your SQL server and inplace of the tables use Views in localDB... point these views to MYSQL server.... it might hamper your performance a little bit.. but it should be fine..