April 23, 2009 at 1:05 am
Dear Experts,
We are currently working on the log shipping servers which works for application.
The technology currently we are working is Logshipping. Now our client needs DB Mirroring to be implemented not Log Shipping.
Can anyone please help me, what will be the painful areas if we go for Mirroring comparing Log Shippings.
As per my knowledge our LS process is working fine which supports for our application. But still our client need Mirroring.
I would like to know the areas to be well understood. I need the complete differences, areas to be analysed before implementing Mirroring, painful areas in Mirroring etc..
Suggest me please......
Thanks,
CH&HU.
Cheers,
- Win
"Dont Judge a Book by its Cover"
April 23, 2009 at 1:31 am
Can you post requirement ?
Are the primary servers and secondary servers are in same domain ?
Does the nw response between the server < 10ms without packet loss ?
Purpose of the secondary server , are they going to use as stand-by option or want real time data for user to pull report with some delay ?
These ome more questions needs to be clear to define the goal before you embark on data mirroring. The data mirroring FAQ in MSDN good place to start your work.
-Sat
Cheer Satish 🙂
April 23, 2009 at 1:45 am
Dear,
Can you post requirement ?
Are the primary servers and secondary servers are in same domain ?
Does the nw response between the server < 10ms without packet loss ?
Purpose of the secondary server , are they going to use as stand-by option or want real time data for user to pull report with some delay ?
1. We have to make the data LIVE, as the secondary server is using for application.
2. Yes both are in domain
3. Yes its <10ms hope so. But there is a network issues often.
4. The seconday server is the real server and the live server for Application.
5. Yes we are using the secondary server for pulling SharePoint & reports.
Can you please suggest me....
Cheers,
- Win
"Dont Judge a Book by its Cover"
April 23, 2009 at 2:04 am
CH&HU (4/23/2009)
5. Yes we are using the secondary server for pulling SharePoint & reports.
I'm not sure you can run sharepoint against a database snapshot. Have you tried?
The mirror db is not readable. It's in recovery, just like the log shipping secondary. You can put a database snapshot on the mirror to get a point in time, read only 'copy' of the principle database, but it is read only.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 23, 2009 at 2:21 am
Thanks for your reply Gail Shaw,
Now we are using our Secondary database (LS) for generating the BI Reports for client , business.
LS Secondary DB is in 'Standby / Readonly'. We do not proposed BI to work on Primary server DB.
However i would like to know about the painful areas of Mirroring without MONITOR server. As, Failover, Network issues, Synchronization, issues , resolution time if any as like that.
I have exposure on Log Shipping / Replication but not on Mirroring.
Thanks.
Cheers,
- Win
"Dont Judge a Book by its Cover"
April 23, 2009 at 3:15 am
With mirroring, I would recommend you have a witness server to make full use of the technology. We've run tests to similate a hardware loss (yanked the power out the back) and it's quite surreal to see your app pause, then carry on as if nothing has happened. If you want to go without then you'll have to manually instruct the mirror db to take over the lead role on the loss of the primary. This isn't fun at 3am.
As far as I've ever been able to, you will not be able to read from the mirrored copy. Any attempt to connect have been met with "The database "YourDatabase" cannot be opened. It is acting as a mirror database."
I would, however, be a bit concerned over the "network issues" which occur "often". I don't know how the mirroring will react to flakey network connections. It's not something (thankfully) I've had to test.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply