So I successfully got the mirroring to run and now I'd like to see what's going on between the two servers ( i'm not using a witness). I launch the Database Mirroring Monitor and its showing the two servers but when I go to the history column I'm not seeing any data movement. I've done a an update on a db with 1500 rows so I was expecting to see this show up.
Also, is there anyway to query the database thats acting as the mirrored db?
thanks
daniel
Can you verify that you are connecting to the Partner server as SA or in the DBM_Monitor role?
You leave the monitor up and running, correct?
Do you have a periodic job running on the server to update the base table?
You cannot query the mirror database. You can create a snapshot on the mirror database and query that. I'm assuming you want to verify that the data has actually moved over to the other side.
Thanks,
Mark
|||
I'm seeing a value of 20KB/sec in the Send Rate column now. I updated one column in a table of 1500 rows.
How do I assign someone the dbm_monitor role?
thanks for your response, seems as if your the only MS tech on this specific forum.
|||
Search BOL for information on assigning a principal (a login in this case) to a role.
The role should have been created in MSDB when one of the monitoring stored procedure's was run.
Database Mirroring is my feature.
Thanks,
Mark
|||I am new to Microsoft SQL Server 2005 and i would like to make use of its database mirroring feature. My question though is: is database mirroring supported by the JDBC driver and if so how would you implement/code a connection to principal and mirror servers i.e. how would i implement a client - redirect in case of failures.Any help will be greatly appreciated.|||
You may want to read the BOL http://msdn2.microsoft.com/en-US/library/ms131373(SQL.90).aspx .
If your using the new 2.0 framwork for programming e.g. vb.net, c#, you may be able to have to specify in your connection string the failover and primary.
|||
This is great!! Others are posting answers here as well!!
The JDBC support for database mirroring should be in V1.1. That should ship a CTP soon and an RTM version in the middle of the year.
Now, you can always put the redirect logic into the application. This allows you to control which server you would like to connect to. More work for you the application developer, but it allows more control.
Thanks,
Mark
|||So Microsoft's JDBC driver does not currently support MS SQL 2005 's database mirroring?|||
Currently Microsoft's JDBC driver does not have automatic client redirect for database mirroring. It is in development. If you would like to be a beta tester for this feature, let me know.
You can still use the JDBC driver and connect to a database that is used in mirroring, but after a failover, you will be required to somehow get the client to connect to the other server.
Thanks,
Mark
|||
No support as of yet for "dual databases" in your connection string for jdbc.
Mark, we just discussed this today (jdbc probs) in our weekly db meeting. I'm glad that microsoft will be releasing this. Are we going to see the sp1 before the end of April Mark?
SQL Native Client OLE DB Provider
The SQL Native Client OLE DB provider supports database mirroring through connection and connection string attributes. Specifically, the SSPROP_INIT_FAILOVERPARTNER property has been added to the DBPROPSET_SQLSERVERDBINIT property set; and the Failover Partner keyword has been added as a new connection string attribute.
The failover cache is maintained as long as the provider is loaded, which is until CoUninitialize is called or as long as the application has a reference to some object managed by the SQL Native Client OLE DB provider such as a data source object.
For details about SQL Native Client OLE DB provider support for database mirroring, see Initialization and Authorization Properties.
SQL Native Client ODBC Driver
The SQL Native Client ODBC driver supports database mirroring through connection and connection string attributes. Specifically, the SQL_COPT_SS_FAILOVER_PARTNER attribute has been added for use with the SQLSetConnectAttr and SQLGetConnectAttr functions; and the Failover Partner keyword has been added as a new connection string attribute.
The failover cache is maintained as long as the application has at least one environment handle allocated. Conversely, it is lost when the last environment handle is deallocated.
| Note: |
| The ODBC Driver Manager has been enhanced to support the specification of the failover server name. |
|||
SP1 will be released soon. I mean soon. Real soon. So, so soon. I can almost taste it.
However, the JDBC driver will RTM in "the middle of the year."
Thanks,
Mark
|||Hey Mark, thanks for your response. I will like to be a beta tester for the JDBC driver, how do I go about that?|||
Contact Shelby Goerlitz. He is the Program Manager for the JDBC.
His email is shelbyg (at) microsoft (dot) com
This should start the process, but there are no guarantees, etc.
Thanks,
Mark
