Home » SQL ServerRSS

Database Properties “Mirroring” and "Transaction Log Shipping" Pages Missing

I am having a problem with one database on my SQL Server 2005 production server.

A number of databases are already set up for mirroring, however when I right click and go to properties in SSMS, on one particular database there is no "Mirroring" property page available.

I have done the normal tasks, such as setting Full Recovery model, running a full backup of the database and backing up the logs.

I can't see that this is a server specific issue as other databases are happily mirroring.

I've looked around and I can't see that I'm missing a setting, any help would be appreciated.

Thanks.

EDIT: This is nothing to do with the Mirror Database yet, I can't get as far as specifying the Mirror Database , I cannot see the "Mirroring" page on the principle.

EDIT: I have managed to setup mirroring using t-sql commands. However I am still unable to see the "Mirroring Page".

UPDATE: This applies to the Transaction Log Shipping option as well. I can successfully set it up in SQL but not through SSMS.

 

18 Answers Found

 

Answer 1

Just a guess - what is the compatability level of that database?  Is it the same as the balance of your db's?
 

Answer 2

Hi the compatability level is set at SQL Server 2005 (90) just like all the other databases. I don't understand what "Is it the same as the balance of your db's" means, unless is it the same as the other databases, in which case yes.
 

Answer 3

Hi

to better understand the problem, we need to know the following
1 what is the edition and version of the database  you would like to mirroring.
2 could you set the database mirroring with another database on another sql  server instance?
3 if there are some error, please post the detail error message here.


Regards
 

Answer 4

1) sql  Server 2005
2) It's not specific to database  mirroring, I have other mirror databases setup on the server  and this is the only database that doesn't mirror.
3) I can't find a single exception raised in any logs when the pages  don't show in the property pages. 
 

Answer 5

Hi

since it is a GUI problem, let's us another SSMS to open the properties  of the database.

Also, please chekc if we could open properties of other databases in the sql  instance.

Besides, do you install sql 2005 sp3?

Regards
 

Answer 6

Yes the server  is using SP3 the full version is: 9.00.4035.00.

All other databases open the property pages  correctly.

I have tried opening the property paged in SSMS 2005 & SSMS 2008 and still have the same problem.

I have tried doing this on other colleagues machines as well, and still the same problem.....

I think I've tried everything obvious......

 

Answer 7

Hi

Based on the ccurrent situation, we could know the issue is related to the special databases. Therefore, please check what is the difference between the database  with other databases.

Also, please run sql  profiler trace while reproducing the problem; by ananlysis the sql profiler trace, we could know what actually runs in the sql when the problem  happens; and  by capturing the sql profiler trace, we could figure out the difference between the problematic process with the normal process.

Regards
 

Answer 8

I've looked at the databases and can see no obvious differences. Is there something specific I should be looking for?

I have run a trace on a database  that works when opening the Mirror Property Page and the database that doesn't. Less happens in the failing database trace, however there is a lot of SQL Event data, is it appropriate to post that here?

Thanks
 

Answer 9

Hi

we could use sql  profiler trace to capture the 2 processes; one is when you open the  Property Page of the special database; another is when you open other database; and then we could analysis the 2 processed to figure out the difference between the 2 processes;

if it is convenient to you, you could upload the 2 profiler trace files into you skydrive space and only share it with us(support-sqlforum@live.com). after that, please post the linke and I will analysis the process for you.

Regards
 

Answer 10

OK I've done as you said and added the event data from two traces to my skydrive, one on a database  that works and one that doesn't. I traced the process of right clicking a database clicking on Tasks and then clicking Mirror.

The database that works shows options for Mirroring and Transaction Log Shipping the database that doesn't, doesn't show either option.

Thank you for your help.
 

Answer 11

hi

please post the link to your skydrive.

Regards
 
 

Answer 13

Hi just wondering whether you managed to get anywhere with the trace files I stored?

Thanks
 

Answer 14

Hi, do you think you'll get chance to check those trace files, or should I consider raising a call at MS?

Thank you for your help.
 

Answer 15

OK, I guess I will have to raise a call through MS, thank you for your help.

Ed
 

Answer 16

I ended up having to have a Microsoft Support call for the problem  I was facing. Anyway after sometime and a number of support sessions they worked out that the database  with the problem had an ID of 4 in sys.databases. IDs 1-4 are usually reserved for the system databases and if a database has any of these ids the T-log or Mirroring properties  are not displayed. So somehow are database got the ID 3 and now I better get on and detach and reattach some databases to reassign IDs.
 

Answer 17

Yes , Ed is Correct , I worked with him and figured out that this was the root cause of the issue. I am not sure how could the User DB get a DBID of 4 though neither i beleive Ed is aware of that. So that is the root cause of the issue.

Regarding  how to we get around with this.
I would suggest detaching the MSDB as well as the User DB and then try attching MSDB first and see if it retains back the DB ID 4, once it does we can safely attach the UserDB.

HTH
Pranab
 

Answer 18

Hi

Based on the ccurrent situation, we could know the issue is related to the special databases. Therefore, please check what is the difference between the database  with other databases.

Also, please run sql  profiler trace while reproducing the problem; by ananlysis the sql profiler trace, we could know what actually runs in the sql when the problem  happens; and  by capturing the sql profiler trace, we could figure out the difference between the mxf problematic process with the normal process.

Regards

Now I'll try it, Thanks for your reply! I have the similar question.
 
 
 

<< Previous      Next >>


Microsoft   |   Windows   |   Visual Studio   |   Follow us on Twitter