Vault upgrade (MSDE to SQL2005)

[hachiihcah]

Hi, we have been running Vault 2.06 for some time now on a server with MSDE on it. Recently we ran into an issue with adding new files to the vault. I immediately did a backup (~2gigs) and we were thinking that upgrading vault and getting SQL2005 up and running was a good idea (and may solve our problem). So we bought Vault 3.18 for .Net 2.0, restored the backup file from msde onto sql2005 and ran the 3.18 installer. We got the following install log (which may also shed some light on our earlier issues). Any insight on whats going on, and how we can get our repository/new vault server up and running?
thanks,
ee

Vault Install Log:

OK
Configuring your new Vault Installation
Checking for IIS Version...Requesting Vault Admin user password...OK
Connecting to the SQL Server...OK
Verifying the SQL Server requirements...OK
Checking for an existing Vault database...Found.
Asking for database's fate...Keep existing.
Upgrading the existing Vault database...
This may take a long time. Do NOT stop this process!
Checking the installed database version...OK
Grant database access to SKYBOX\ASPNET...OK
Upgrading SourceGear Vault database schema...Could not allocate space for object '(SYSTEM table id: 3)' in database 'sgvault' because the 'PRIMARY' filegroup is full.
Vault Setup is exiting due to a failure or cancellation. Error Code = -1280

[hachiihcah]

Ok, after some more investigation (and attempting to manually increase the size of the sgvault database), there appears to be a hard limit of 2048 megs for our particular sql license. Luckily we were grown to only 2020 megs so i have manually expanded to precisely 2048 and i may be able to squeak through the upgrade.

Phase 2 (i guess) is to delete unnessary items and find out what it takes to increase the file size restriction. *shrug*

[hachiihcah]

Ok, so that approach worked. I am upgraded, squeaking by on a few extra MB, and now i have licenses installed and am deleting the extra junk. It appears that this was a solo effort, but hopefully someone else can benefit from me posting

[jclausius]

I'm not sure why you are seeing this problem. With SQL Server 2005 Express, you now have a four GB limit.

From Microsoft's SQL Server 2005 Express Edition Features page -

Scalability and Performance

• Supports 1 CPU, but can be installed on any server
• 1 gigabyte (GB) addressable RAM
• 4 GB maximum database size

[jclausius]

Another possibility here is that the sgvault database resides on a disk partition that is just out of space?