Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
petek
Posting Yak Master
192 Posts |
 Posted - 2008-12-18 : 06:28:00
|
| Hi all Firstly thank you for looking at this post.....We are looking to expand the amount of databases on our Sharepoint SQL servers to manage the space allocation shared amongst various teams. This will entail creating a new database and then mirroring it over to our DR solution.Does anybody know what limitations there are in SQL server to maintain an effectively performing database server with many databases that are at the same time mirrored to another server? Are there limitations on the number of databases and the size of the database before it has any detrimental effect on performance? If there are any white papers on a Microsoft site that discusses this, we would be interested to know also. Thanks in advanceKind RegardsPete. |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-12-18 : 09:23:20
|
| Remember in synchronous Mirroring, always transaction has to commit in mirror before it gets commit in Principal. So there is a 2-phase commit and which when applied to high OLTP databases can nail down your server. I would suggest if company can bear expense,use clustering in local area and Asynchronous mirroring to DR(where there is no 2 phase commit). Also it depends many factors? as How far will be DR location,How high is transaction rate and network bandwidth. |
 |
|
|
cat_jesus
Aged Yak Warrior
547 Posts |
Posted - 2008-12-22 : 15:45:46
|
| What's an "effectively performing database server"?An infinite universe is the ultimate cartesian product. |
|
|
|
|
|
|
Database Mirroring....