Increasing the Size of the Sybsystemprocs Database

If your current sybsystemprocs database does not have the minimum space required, two options exist for creating a new database with sufficient space for the upgrade. Learn about these option here.

The first option is to drop the old database and device and create a new sysprocsdev device.
The second option is to leave the old database and device alone and add a new device large enough to hold the additional megabytes, and alter the sybsystemprocs onto the new device. Sybase recommends that you expand the current device.

To increase the size of the sybsystemprocs database:

If you do not have a current backup of your old database, create one now.
In isql, use alter database to increase the size of the sybsystemprocs database. For example:
```
1> use master
2> go
1> alter database sybsystemprocs on sysprocsdev=40
2> go
```
In this example, “sysprocsdev” is the logical name of the existing system procedures device, and “40” is the number of megabytes of space to add.
If the system procedures device is too small, you may receive a message similar to the following when you try to increase the size of the sybsystemprocs database:
```
Could not find enough space on disks to extend
database sybsystemprocs
```
1. If there is space available on another device, expand sybsystemprocs to a second device, or initialize another device that is large enough. See the Increasing Device and Database Capacity for System Procedures topic for more information.
To verify that Adaptive Server has allocated more space to sybsystemprocs, issue:
```
1> sp_helpdb sybsystemprocs
2> go
```

When the system procedures database is large enough to accommodate the increased size of the sybsystemprocs database, continue with the other pre-upgrade tasks.