HELP error: could not allocate space for object 'sysdtspackages'

[Glowworm27]

HELP please,

I am receiving this error when trying to save my DTS Package.

could not allocate space for object 'sysdtspackages' in Database 'MSDB' Because the 'PRIMARY' Filegroup is full.

I have tried to increase the size of the MSDB database from the enterprise manager, but it will not get any bigger than 89 mb.

The drive has plenty of space on it for file growth, like 50 gigabyytes or so. So I don't know why this is happening.



George Oakes
Check out this awsome .Net Resource!

http://www.learnvisualstudio.net?referedby=54275&cam=Tek-Tips

 

[Corran007]

Have you checked in the msdb database properties to make sure that the max file size is not set to 89mb? my msdb is 354 right now so it can obviously grow. (we use dts alot)

 

[Glowworm27]

Yes, Max file size is not set, I'm sorry if I did not make that clear in the inital post.

The MSDB is setup so it "SHOULD" auto grow, not Max file Size is set, and the Drive has plenty of space for a larger msdb.

We have had similar issues with other databases on this server. Let me provide some background.

6 months ago we realized our current SQL server wasn't powerfull enough to handle the load, so we order a faster, big, stronger server.

A month ago we got the server, and set it up. Our Network Administrator performed the Database move, whereby he unattached the databases from the original server, and moved them over to the new server. Everything seemed fine.

I was trying to make an existing database bigger to accomadate some new data we were going to import. When I changed the size to the target size, (using enterprise manager) the change did not take place. we refreshed the database, and still it was the same size. SO I tried to make it only a little bigger to see if I was setting the size to big, that to did not work.

I went to our network adminstrator to see if there was enough drive space, and he said yes, 50 gigs. So he tried to make the db bigger, through enterprise manager. and he had the same results. On accident we tried to make the database 1 meg larger, and it accepted the new change. after that we were able to set the file size to whatever size we wanted.

This was the case with a couple of the other databases.

However I cannot seem to get msdb to grow by any amount I try. I can make the Transactionlog file larger without any trouble.

I even tryed to make the database larger using the query analizer, with the same results. it would wait a few seconds then say it completed succefully, and when you view the properties, it remained the same size.

Next Im going to try to put the Profiler on to see if there is some hidden message that Bill Gates doesn't want us to see. wish me luck





George Oakes
Check out this awsome .Net Resource!

http://www.learnvisualstudio.net?referedby=54275&cam=Tek-Tips

 

[Glowworm27]

Nope SQL profiler was absoulutly no help

No errors or nothing,

this command was executed, and said it completed successfully

ALTER DATABASE [msdb] MODIFY FILE (NAME = N'MSDBData', SIZE = 92)

no change in db size

George Oakes
Check out this awsome .Net Resource!

http://www.learnvisualstudio.net?referedby=54275&cam=Tek-Tips

 

[Glowworm27]

looking at the SQL log I did find this error

fcb::ZeroFile(): GetOverLappedResult() failed with error 2.

Any idea what this means, the time stamp cooresponds with the time I tried to increase the size.

George Oakes
Check out this awsome .Net Resource!

http://www.learnvisualstudio.net?referedby=54275&cam=Tek-Tips