Viewing 8 posts - 1 through 8 (of 8 total)
We were having the same issue. A couple of things you should try:
1. If your environment is co-existing (i.e. SQLS 2k and 2k5) and you're getting this error then try...
October 22, 2007 at 2:31 pm
Thanks Markus...that worked...I also found in BOL "Database Mail Configuration Wizard"
Note: |
---|
Enabling SQL Server Service Broker in any database requires a database lock. If Service... |
August 9, 2007 at 9:42 pm
Couple of things in question:
1. DB on the report server will be in No Recovery mode when using log shipping
2. The t-logs of the prod server are taken every 15...
August 1, 2007 at 9:10 am
The logs on the prod (source) server are huge! So when the DB is restored on the reporting server the logs are restored along with it.
Any suggestion on how the...
July 31, 2007 at 9:56 pm
I am configuring the log shipping and getting the same error:
"During startup of warm standby database <db_name> (DB ID 5), its standby file (C:\windows\system32\<db_name_20070727025522.TUF)was inaccessible to the Restore statement. The OS...
July 26, 2007 at 9:15 pm
My total overall score was ~ 600. Someone else that wrote many MS exams was telling me the same thing about the breakdown of details...Maybe every exam center have their own...
July 10, 2007 at 9:51 am
Thanks for all the info...I did get a print out and it has 2 general items marked on it...it wasn't in details though...
1. Non-Performance based items
The highlighted line was a very close...
July 10, 2007 at 8:31 am
Does the replication needs to be stopped or this could be done on a live replicated DB?
June 20, 2007 at 10:30 am
Viewing 8 posts - 1 through 8 (of 8 total)