March 2, 2011 at 1:18 pm
Environment: Access 2003, SQL Server 2008
I have inherited several Access applications that use linked tables and linked Excel files as their datasource. Very slow since the files reside on Shared Network drives.
I want to convert the backend from these sources to SQL Server. To do this I need to tell the DBA what the initial DB size should be.
None of the Access apps are more than 16mb and everything probably totals up to less than 1gb.
Are there any Best Practice recommendations on initial SQL Server database sizing for a reporting database (read small data warehouse)?
I could waste my life away looking at every input file and figuring exact data sizes, which would probably be off anyway or I can have the DBA just assign a reasonable size to start and we can track growth and adjust from there.
DBA is not helpful in determining this without an approved project with $$ allocated. To get the project moving & approved, I need to have the initial sizing estimate so the DBA can create the darn DB
Thanks for any advice.
March 7, 2011 at 3:18 pm
First, make a copy of this database and import all the external data sources (as tables) that are NOT already on SQL Server. Then look to see if there are indexes in place that would be sufficient if carried over to SQL Server. For those tables you just imported, create appropriate indexes, and do the same for existing tables. Then, look at the total size of the database file after using Compact and Repair. That is your starting point. That's got to be faster than adding everything up and trying to figure out Excel data sizes.
Steve
(aka sgmunson)
:-):-):-)
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
March 8, 2011 at 10:03 am
We did a conversion about 2 years ago, the original Access file with data + forms etc. was 140 MB, the resulting SQL db was around 280. Now two years later the SQL db has doubled again.
HTH
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply