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?

Thank you!
Bosko

(bosko19 (AT) gmail (DOT) com) writes:
Eh, that looks bad. I haven't worked much with mirroring, or more precisely
not at all. But a syntax errors is not what I would expect. Could you
list the exact name of the servers and databases involved? My suspicion
is that there is a problem with special characters.


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

On Apr 13, 6:45 pm, Erland Sommarskog <esq... (AT) sommarskog (DOT) se> wrote:
LOL...I didn't think it looked good either

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 (AT) gmail (DOT) com) writes:
What service-pack level are you at? (For all three machines.)

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 (AT) sommarskog (DOT) se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Erland Sommarskog (esquel (AT) sommarskog (DOT) se) writes:
Sorry, I see now in your first post that you are on SP2.





--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

On Apr 16, 5:30 pm, Erland Sommarskog <esq... (AT) sommarskog (DOT) se> wrote:
Thank you for taking the time to look into the issue! I will submit
the case to Microsoft and hopefully get a resolution from them.

Bosko