Viewing 15 posts - 46 through 60 (of 366 total)
I restored the master, msdb and 5 user db's in that order for dr testing yesterday. No problems at all.
Yes the non-existant db's where suspect until I restored those, but...
July 16, 2004 at 12:02 pm
With Steps 1 & 2, you are running the jobs.
In Step 3 it is scheduled, hence running under the job owner. (You can view/change the job owner by right clicking...
July 16, 2004 at 11:33 am
As you can chain sql commands together with a ;
You can add other code along with the database backup eg setting the autoclose, hence doing it one db at a time
June 11, 2004 at 3:35 pm
You don't need the autoclose, I only mentioned it because you said auto the lack of resources, and that closes the db down after the last connection ends that uses...
June 11, 2004 at 10:03 am
I have had problems with maintenance plans when memory is short on the server, hence the first solution of backup up all databases using t-sql (of course you need to...
June 11, 2004 at 8:39 am
I have used DTS jobs to connect to sysbase 11.5 and 12.5. In both cases I installed the adaptive server PC client software on the sql server, then setup an odbc...
June 11, 2004 at 8:11 am
What about setting the 'autoclose' parameter on all the databases prior to the backups, then using something like
exec sp_msforeachdb 'if db_name() <> ''tempdb'' backup database [?] to disk=''d:\backups\?.bak'' with...
June 11, 2004 at 2:04 am
If this is running sql 2000, when you rename the machine the sql server won't run.
You would need to use sp_dropserver <servername>, then sp_addserver <newname>,local to bring it back
Also last...
June 10, 2004 at 6:37 am
Thanks, but I had found that artitle and it relates to SQL 7 not 2000, hence the server doesn't use the dll versions mentioned in the article.
June 1, 2004 at 1:13 am
Microsoft provide a tool to identify the MDAC version. Download the MS component checker from http://www.microsoft.com/downloads/details.aspx?familyid=8f0a8df6-4a21-4b43-bf53-14332ef092c9&displaylang=en
May 26, 2004 at 1:49 am
SQLSecurity.com maintains a list with references back to the Microsoft Q article
See http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37 for more details
May 25, 2004 at 2:41 am
If it is a one off trace for a relatively short amount of time, I would use 'sql profiler'. You can set the filters to a database and a user, hence...
April 13, 2004 at 1:14 pm
You can just stop and restart the sql server, but the transaction will just carry on rolling back/forward if it can.
If the process was running an extended stored procedure...
April 13, 2004 at 12:36 pm
In Enterprise manager you can set the default location of both the data files and the transaction log files (for new databases).
Right Click on the server
Choose properties
Choose the database settings...
April 7, 2004 at 10:17 am
Viewing 15 posts - 46 through 60 (of 366 total)