Viewing 10 posts - 1,156 through 1,165 (of 1,165 total)
I believe Job will fail...
and don't configure to repair it because sometimes your db may with single user mode.
You can corrupt the table in a db manually and test it.
December 1, 2006 at 7:47 pm
The user which can create proc. may be the member of some other role which has higher access.
December 1, 2006 at 7:31 pm
One month or one week should be fine depends on the data size...
Make sure you have the index on time column and you have enough allocatted free space in db...
December 1, 2006 at 1:47 pm
You said db growth 10 times but you didn't mentioned which file data/log grew?
Your db might be in FULL recovery mode...
December 1, 2006 at 1:40 pm
1. Create a server list on Report server and create table RestorHistory_All table as RestorHistory table with one additional column server name.
2. create a procedure get the restorehistory into a...
December 1, 2006 at 1:37 pm
Are you using History Cleanup task in your Maint. plans?
December 1, 2006 at 1:27 pm
As Robert mentioned you can give any extesion to it.
When you get the backup file from some one else, it is always better to run RESTORE HEADERONLY command to check...
December 1, 2006 at 1:10 pm
Most of the configurations are dynamic in SQL2005 but this server name change is not dynamic...
May be in next release
December 1, 2006 at 1:03 pm
Just create a job on your developement server to run the restore.
Step1: Kill the connections in restoring db.
Step2: Run the restore command.
Step3: Create/Sync the db users...
November 27, 2006 at 11:16 pm