Recent content by kishy

Dont you have backups of the database ? I guess if it was retrieved from a bad disk, its difficult to get back. --Kishore

I guess there is some problem with your database itself. Your queries are frequently getting hung which should not be the case. Do you have a backup of your database. If yes, first restore your database to normal state. Then run some DBCC checkdb commands to see whats going on your database...

I think it will be upgraded to SQL 2000 automatically. However, I would recommend taking a backup of your ERP database, msdb database(if you have jobs/alerts defined) on SQL 7.0, uninstall SQL 7,0, install SQL 2000 and restore your database on SQL 2000. I have seen issues when upgrading...

Had you properly detached it from your original server ? Ar eyou copying it to the same location as the original server ? Have a look at the BOL on attach/detach. --Kishore

Make sure you have the proper access and rights on the folders you are copying your backup files to. It should make you to move forward. --Kishore

A shortcut way of doing this is : select * into [people] from [users] where 1=2 --Kishore

What kind of operating system is running on the file server? If Windows 2000 or 2003, are you using named pipes? If yes, then check out this article : http://support.microsoft.com/default.aspx?scid=kb;en-us;827452 --Kishore

Yes. I use the Performance Monitor on regular basis to test if my server is running well under the current work load. I at times sit at nights to see what is my server status when the workload is less and what other things I can accompalish to use up this time to tasks which take up most of the...

The job will fail giving you details what caused it to fail. Like what page of database has the problem or sumthing like that. You could run the job manually first to check if you are getting any issues, and then you could schedule it. --Kishore

Well there are a number of tasks that a DBA can perform in his day to day tasks. One foremost thing is to understand your logical design of the database, if you have not been the db designer. To understand the db design is of utmost important to know how your data logic flows. Another important...

Yes. All server participating in Log shipping need to have SQL Server 2000 Enterprise Editions.

One more reason for your increase in your transaction log may be if you are Maintainence plans to reindex your tables. Reindexing would considerably increase your transaction log size.

YOu could use DB Maintainence Planner to create a backup and restore job with the time interval you want. This will create 2 jobs. You can monitor the jobs. --Kishore

Chris -- I would suggest you 2 options here : 1. I would recommend to run a DBCC CHECKDB on your original server and check if any part of the database is not corrupt. 2. If you have a test sql machine wherein you could restore your backup file and check if it is getting restored there...

Looks like you have a corrupted backup file with you. Probably you can have one more copy from your original database and try restoring it on the new server. One more way would be to take the database offline, detach the data and log files from your original server, copy them to the new server...