Database mirroring with SQL Server 2005

[Ali Soylu]

Well, first of all mirroring is not yet officially supported in sql2005.

And microsoft has a JDBC driver that supports mirroring that should work
with CF although I have not tried it:

[url]http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/jdbc.mspx[/url]

ALi

"tonyweeg" <webforumsuser@macromedia.com> wrote in message
news:dnupnu$t45$1@forums.macromedia.com...

> eddie... any luck with this yet?
> i know that .NET has a parameter in its connection string for "Failover"
> and
> you specify the failover database, but im not sure cfmx will be able to
> handle
> this...
>
> anyone from macromedia / adobe have any ideas?
>

[eddieralph]

What I am going to do is use the standard DataDirect JDBC driver, which has a
url connection string argument 'AlternateServers' that you can supply that will
connect you to the specified alternate db server in the event that it cannot
connect with the primary db server specified.

Currently you have to change the neoquery.xml file config map to fix a bug
whereby anything you supply in the connection string box doesn't actually get
appended to the connection string. Once you have got over that, just supplying
'AlternateServers=(\\alternate-server:1433)' does the trick.

[rgrossha]

Did this work?

What is the neoquery.xml bug, and how do you fix it. I was unable to find anything in support about it.

Thanks in advance.

Rob

[eddieralph]

The neoquery.xml bug is that if you enter anything into the (advanced)
connection string box, they don't get properly appended to the connection
string. In order for any connection string arguments to be appended properly
to the connection string you have to modify the neoquery.xml file as follows:

Find


jdbc:macromedia:sqlserver://:;databaseName=;SelectMethod=;sendStringParameters As
Unicode=

you need to add ";" to the end


jdbc:macromedia:sqlserver://:;databaseName=;SelectMethod=;sendStringParameters As
Unicode=;

Ed

[eddieralph]

I forget where I found the fix for this bug, but I have spoken to a MM engineer about it - they said it was being worked on... (it isn't hard to fix so would have expected a hotfix by now...)

[rgrossha]

Thanks.

No fix that I've found either, but there is documentation for your workaround,
plus guidance on the latest released data direct drivers:

[url]http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=42dcb10a[/url]