Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-04-25 : 12:24:30
|
| David writes "I work as tech support for a software company that has a product that can run on sql server if they wish. I have one client that is running sql 6.5. All other clients have been notified that they need to move to 7.0 or above. Here is the problem:They were receiving numerous sql errors with our newest upgrade due to the fact that they were on sql server 6.5 (sp 3). I, as before when I take calls from clients on 6.5, strongly recommended that they have a local tech upgrade them to 7.0 or 2000. They called their tech and told her what they need to do. The tech downloaded the eval version of 2000 (fully functional) to see if it would alleviate the errors. The server she was trying to load it on did not have enough storage capacity to load 2000. She did this on a Sunday night so no one from our tech support was available to help. When she could not clear enough space for the install, she decided she would reload SBS for NT 4.0 which, by default, loads 6.5. She loaded SQL 6.5 to the C drive. The current databases were on the F drive. If that wasn't bad enough, during the reload, she re-designated the F drive as the D drive. This compounded the problem.Now, I'm looking at the working copy of SQL 6.5 on the C drive with the database for our software on a backup. After much stress, I was able to make the new copy see the old master database. I did this by starting sql from the command prompt with no configurations and running sp_config to reset the tempdb and memory. I then ran queries to update the locations of the other databases in the sysdevices table to point to the correct location. When I did this, sql server started normally with no errors.Now, I come to the main problem. I have a good backup of the database. I recreated the devices for the database (data and log). After I recreated the database with the correct devices, I tried to restore. I received a message saying that it could not restore because it needed at least a 950 mb database to dump into. I then went and tried to expand the database. I set the device size to 950 mb (succeeded), the log size to 100 mb (succeeded). I then tried to expand the database but I kept receiving a message saying that I was exceeding the max database cumulative size of 1051 mb. If I tried to set the size to anything but 1 mb, I got this message.I've worked on this problem for two days. I've finally come to the point where I feel like I almost have it and I run into this. The database I'm trying to import is part of the master database so it can see it. What am I missing?" |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-04-26 : 01:46:15
|
| Please post the exact error number/message.-Chad(SP 3?? C'Mon, does this customer have running water?) |
 |
|
|
|
|
|
|
|
SQL Server 6.5 db restore from backup