Is it indeed a requirement that database mirrors have the same name on a server? The reason I ask is that I have several servers with the same database name, and I'd like to mirror all of them to a single (disaster) server and, by necessity, have each mirror to a distinct db name.
Thanks
The database MUST have the same name on both the Principal and the Mirror. Mirroring will not work in your scenario unless you provide distinct names for the databases.
Various posts have noted that mirroring over distance is not advisable or that either async connections should be used.
Are there any limits/recommendations i.e. if two datacenters are a couple of files part with 10GBs fibre links and <50ms response times would this be acceptable for high-availability mirroring?
Hi Andrew,
I think you have good network links.
The best thing to do is to test it in synchronous mode first. See what the performance is like.
If the performance is not acceptable, you can then switch the safety off.
Please note that Wtiness server should not be used when running with safety off option.
cheers
Jag
|||Andrew,
Please include re-indexing and large bulk inserts in your testing as well.
cheers
Jag
|||jag,
Thanks for the response, although I think I will need to look at another solution as mirroring has a very small limit on the number of Databases that can be mirrored (10 recommended, people maxing out at 60) and with a large SharePoint installation the number of content databases can exceed these limits relatively quickly.
Options: More SQL servers (x2 to mirror) or use Clustering in live datacenter with Log Shipping to redundant center.
Andrew
We have recently set up two SQL Server 2005 Standard Edition servers with database mirroring. The mirrors function and fail over without a problem, but the Database Mirroring Monitor Job fails every time with the following error message:
Incorrect syntax near '.'. [SQLSTATE 42000] (Error 102) Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon. [SQLSTATE 42000] (Error 319). The step failed.
Both SQL Servers are running SP2 with the latest patches.
Can you please let me know what we have to do to resolve this issue?
Thank you!
Bosko
Is this been like this since the invocation of Database mirroring on these instances?
If not see what has been changed since the last successful occurence.
|||The problems started upon implementation of the database mirroring|||I'm also facing the same issue.
Did anyone find a solution or workaround?
|||I posted this in a couple different forums/newsgroups and never got an answer. We are still having this problem.
Bosko
We have recently set up two SQL Server 2005 Standard Edition servers with database mirroring. The mirrors function and fail over without a problem, but the Database Mirroring Monitor Job fails every time with the following error message:
Incorrect syntax near '.'. [SQLSTATE 42000] (Error 102) Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon. [SQLSTATE 42000] (Error 319). The step failed.
Both SQL Servers are running SP2 with the latest patches.
Can you please let me know what we have to do to resolve this issue?
Thank you!
Bosko
Is this been like this since the invocation of Database mirroring on these instances?
If not see what has been changed since the last successful occurence.
|||The problems started upon implementation of the database mirroringsqlIncorrect syntax near '.'. [SQLSTATE 42000] (Error 102) Incorrect
syntax near the keyword 'with'. If this statement is a common table
expression or an xmlnamespaces clause, the previous statement must be
terminated with a semicolon. [SQLSTATE 42000] (Error 319). The step
failed.
Both SQL Servers are running SP2 with the latest patches.
Can anyone help with the resolutionto this this issue?
Thank you!
Bosko(bosko19@.gmail.com) writes:
Quote:
Originally Posted by
We have recently set up two SQL Server 2005 Standard Edition servers
with database mirroring. The mirrors function and fail over without a
problem, but the Database Mirroring Monitor Job fails every time with
the following error message:
>
Incorrect syntax near '.'. [SQLSTATE 42000] (Error 102) Incorrect
syntax near the keyword 'with'. If this statement is a common table
expression or an xmlnamespaces clause, the previous statement must be
terminated with a semicolon. [SQLSTATE 42000] (Error 319). The step
failed.
>
Both SQL Servers are running SP2 with the latest patches.
>
Can anyone help with the resolutionto this this issue?
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||On Apr 13, 6:45 pm, Erland Sommarskog <esq...@.sommarskog.sewrote:
Quote:
Originally Posted by
(bosk...@.gmail.com) writes:
Quote:
Originally Posted by
We have recently set up two SQL Server 2005 Standard Edition servers
with database mirroring. The mirrors function and fail over without a
problem, but the Database Mirroring Monitor Job fails every time with
the following error message:
Quote:
Originally Posted by
Incorrect syntax near '.'. [SQLSTATE 42000] (Error 102) Incorrect
syntax near the keyword 'with'. If this statement is a common table
expression or an xmlnamespaces clause, the previous statement must be
terminated with a semicolon. [SQLSTATE 42000] (Error 319). The step
failed.
Quote:
Originally Posted by
Both SQL Servers are running SP2 with the latest patches.
Quote:
Originally Posted by
Can anyone help with the resolutionto this this issue?
The database server has a dash in it (i.e. CompanyName-SQL1 and SQL2
respecitvely). All databases are just alpha characters except for one
that begins with a number sequence (i.e. 1000DatabaseName).
Thank you in advance!
Bosko|||(bosko19@.gmail.com) writes:
Quote:
Originally Posted by
The database server has a dash in it (i.e. CompanyName-SQL1 and SQL2
respecitvely). All databases are just alpha characters except for one
that begins with a number sequence (i.e. 1000DatabaseName).
If you are on SP2, you should definitely submit a bug on
http://connect.microsoft.com/SqlServer/. And if it's not an acceptable
workaround to rename the servers, I think you should open a case with
Microsoft, and demand that you get a hotfix.
If you are not on SP2, I recommend you to download it to see if it addresses
the problem. Note there is a rollup to SP2 which addresses two serious
bugs with maintenance plans. Make sure you get the rollup, if you use
maintenance plans.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Erland Sommarskog (esquel@.sommarskog.se) writes:
Quote:
Originally Posted by
What service-pack level are you at? (For all three machines.)
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||On Apr 16, 5:30 pm, Erland Sommarskog <esq...@.sommarskog.sewrote:
Quote:
Originally Posted by
Erland Sommarskog (esq...@.sommarskog.se) writes:
Quote:
Originally Posted by
What service-pack level are you at? (For all three machines.)
Bosko
