Vault import - is it still working?

James Jeffers · Post by **James Jeffers** » Tue Aug 30, 2005 2:40 pm

I'm going to upgrade the SQL Server to 3a, unless there is another preferred version.

lbauer · Post by **lbauer** » Tue Aug 30, 2005 2:49 pm

That should be fine.

lbauer · Post by **lbauer** » Tue Aug 30, 2005 3:34 pm

The error in your latest log shows the repository couldn't be deleted because SQL Server ran out of disk space:

----8/30/2005 3:34:26 PM admin--brinks.acciptier.com(172.31.70.239)--SSL Disabled System.Data.SqlClient.SqlException: Could not allocate space for object '(SYSTEM table id: -122213000)' in database 'TEMPDB' because the 'DEFAULT' filegroup is full.

Make sure tempdb.mdf (usually in C:\Program Files\Microsoft SQL Server\MSSQL\Data) has enough space, and that tempdb is configured to allow it to grow (SQL Enterprise Manager->tempdb->Properties->Data files).

James Jeffers · Post by **James Jeffers** » Tue Aug 30, 2005 6:04 pm

I actually had to split the DB data files into another disk. The first disk set was capped for growth, but the second one is unlimited.

James Jeffers · Post by **James Jeffers** » Wed Aug 31, 2005 11:59 am

After a re-install and reorganization of MS SQL Server and Vault, I'm cautiously optimistic.

The same import into Vault is now much faster by appearances. The estimated time for import is on the order of 8-10 hours, as opposed to over 30 for the same set of files and folders.

Linda, thank you for your patience and assistance.

lbauer · Post by **lbauer** » Wed Aug 31, 2005 12:22 pm

Good news so far . . .

As always, contact us if you run into any issues.