High Availability solutions

Hi

We are using in our company an ERP system called iScala.

This software is using SQL server as DBMS.

We would like to use the SQL mirroring feature from SQL 2005.

The software is using the SQL server instance name to connect to databases and when the Main SQL server fails the application can't connect to the Mirror instance.

Unfortunatelly we can't change the connection string (the software is provided by another company).

Do you have a solution?

Thanks

I believe you have to contact the vendor to provide such changes, as this is application issue to talk to the mirror server in the event of failover. If the application is not db mirror aware then you have to find a route from connectivity to talk to other server in such cases.|||

Thanks

You are right.

I'm checking now some solutions for High Availability from Symantec (VERITAS Storage Foundation HA 4.3 for Windows) and Double-Take.

Do you have any information about them?

|||

You could solve this issue using a manual change to DNS.

i.e. MYLIVESQL -> 10.0.0.1 - connection string uses MYLIVESQL as the server name, in the event of a failure you update the DNS record to MYLIVESQL -> 10.0.0.2 (which is the IP address of the mirror server).

Andrew

|||

If the (former) principal instance is still up and running but the database failover occured, then SNAC will automatically learn the location of the mirror and redirect the connection to the mirror, as described here: http://msdn2.microsoft.com/en-us/library/ms366348.aspx. But this works only if the connection string specifies the database and if the principal instance is still running.

But if the vendor is not providing support for mirroring, is highly unlikely that the application will actually work with mirrored database, it may have dependencies outside the database that are not gonna failover (e.g. logins resulting in orphaned users, jobs in msdb etc)

HTH,
~ Remus

|||

Remus,

MOSS 2007 and WSS V3 fall into the category of not supporting mirroring in the connection strings, hence the need to use the cname approach. Microsoft recommend using stsadm to manually change the settings which I think is less elegant.

Andrew

Hiding duplicates in a details row and hiding the row when it's em

I have a report that is using the drill down feature. So i have 2 detail
rows. The first row is field labels for the 2nd details row. What i would
like to do is only show the first details row once. I know i can set the
properties for each field to hide duplicates but then i'm still stuck with it
showing the blank row. So if i could find a way to suppress the first row
when it's blank that would be good or find a way to only print the first
details row once.well i answered my own question. i moved the field labels to the bottom of
the last grouping before the details, made sure all of the textbox fields
were marked hide duplicates, set the row height to 0, set visibility for the
row to true, and set the toggle setting to be the same as the detail toggle
setting.
"deniseamat" wrote:
> I have a report that is using the drill down feature. So i have 2 detail
> rows. The first row is field labels for the 2nd details row. What i would
> like to do is only show the first details row once. I know i can set the
> properties for each field to hide duplicates but then i'm still stuck with it
> showing the blank row. So if i could find a way to suppress the first row
> when it's blank that would be good or find a way to only print the first
> details row once.