You are viewing limited content. For full access, please sign in.

Question

Question

Migrating version 7 DB to version 9 DB not enough disk space

asked on December 31, 2014

In the process of migrating a Version 7 Database to Version 9 Database. We are receiving the following message during the pick of existing database step.

What disk is this message referring to? The SQL Server has both a data drive (161 GB free )and log drive (108 GB free). We have successfully tested the migration in the past without issues.

 

Also, what is the expected growth for the migration from a Version 7 DB to a Version 9 DB.
 

2 0

Answer

SELECTED ANSWER
replied on January 2, 2015

Are you having the migration utility create the database for you or is the LF 9 database already created with the data and log files on separate drives and you are just pointing to that existing database to use as the destination for the migration?

0 0

Replies

replied on December 31, 2014

This wouldn't happen to be a SQL Express edition, would it? If so, it might be referring to the db size max limit imposed by SQL. Otherwise, I'd suggest double checking where new databases are created. If that doesn't provide any insight, you'll probably want to log the migration and provide that to Support. 

0 0
replied on January 2, 2015

This is not a SQL Express version. SQL is setup to separate the data and log files on different drives.

Are you suggesting that we click to continue and run the migration then pass the log to support? I already brought this to the attention of support and they told me to go to pre-sales and answers.

What is the  expected growth of the database for 1 million documents in V7 compared to V9 with a template of about 7 fields? In a previous successful migration the restored V7 was approximately 45 GB  and when migrated the V9 database expanded to 130 GB.

 

0 0
replied on January 2, 2015

It turns out that the user that we were using to run the migration utility did not have access to the master database. The security on the user was setup with dbcreator only. We had an empty database created and were able to get through the migration utility without the prompt.

 

Thanks for all support!

0 0
replied on January 2, 2015

Sounds good. We'll follow up with our development team still as you should be presented with a more accurate error message in that situation.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.