No Failover and client crashes ODBC DSN Setting for Failover in connection String

We have set up Mirroring with a witness server and everything works fine when we failover from the SQL Management console.

However, if we failover when our Maccola client is connected, the client blows up - clearly because it can no longer connect to the database.

The ODBC DSN used by the Maccola client shows a checkbox for the 'select a failover server' but the checkbox is grayed out.

Also the summary of settings for the DSN at the end of the wizard reveals that the failover to server (y/N) option is set to N.

The default setting for this DSN is 'populate the remaining values by querying the server' but it doesn't appear to be getting the settings for failover from the server or any other interactive DSN settings either. The server is clearly set for mirroring.

Another suspicious item is that the DSN cannot connect to the server with SA permissions, even though the server is set to mixed security and we use the correct authentication.

Is it possible that the client MACHINE is not authenticating with the domain or sql server properly. We are logged into the client with the domain account that is the SQL admin account on the sql server box.

We should be able to interact with the sql server settings through the ODBC DSN on the client shoulnd't we?

Are we missing a service pack on the client?

Thanks,

Kimball

Have you referred to Maccola vendor in this case about the compatibility, I would guess this is to with that drivers.

No Failover and client crashes ODBC DSN Setting for Failover in connection String

We have set up Mirroring with a witness server and everything works fine when we failover from the SQL Management console.

However, if we failover when our Maccola client is connected, the client blows up - clearly because it can no longer connect to the database.

The ODBC DSN used by the Maccola client shows a checkbox for the 'select a failover server' but the checkbox is grayed out.

Also the summary of settings for the DSN at the end of the wizard reveals that the failover to server (y/N) option is set to N.

The default setting for this DSN is 'populate the remaining values by querying the server' but it doesn't appear to be getting the settings for failover from the server or any other interactive DSN settings either. The server is clearly set for mirroring.

Another suspicious item is that the DSN cannot connect to the server with SA permissions, even though the server is set to mixed security and we use the correct authentication.

Is it possible that the client MACHINE is not authenticating with the domain or sql server properly. We are logged into the client with the domain account that is the SQL admin account on the sql server box.

We should be able to interact with the sql server settings through the ODBC DSN on the client shoulnd't we?

Are we missing a service pack on the client?

Thanks,

Kimball

Have you referred to Maccola vendor in this case about the compatibility, I would guess this is to with that drivers.

No Databases in Enterprise Manager

SQL - 2000 running on Win2k Server
I am unable to view my databases in enterprise manager but can see them in Query Analyzer/ODBC. I had deleted a bunch of unused databases last night and after reboot this morning Enterprise manager will not display any of my databases. What have I done?
rwjohn1@.sbcglobal.net
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
Try deleting the registered server and then register it
again in Enterprise Manager.
In Enterprise Manager, right click on the server, select
Delete SQL Server Registration. Then right click on the
server group and select new server registration to register
the server again.
-Sue
On Thu, 28 Oct 2004 12:04:36 -0700, SqlJunkies User
<User@.-NOSPAM-SqlJunkies.com> wrote:

>SQL - 2000 running on Win2k Server
>I am unable to view my databases in enterprise manager but can see them in Query Analyzer/ODBC. I had deleted a bunch of unused databases last night and after reboot this morning Enterprise manager will not display any of my databases. What have I done
?
>rwjohn1@.sbcglobal.net
>--
>Posted using Wimdows.net NntpNews Component -
>Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.

No Databases in Enterprise Manager

SQL - 2000 running on Win2k Server
I am unable to view my databases in enterprise manager but can see them in Q
uery Analyzer/ODBC. I had deleted a bunch of unused databases last night an
d after reboot this morning Enterprise manager will not display any of my da
tabases. What have I done?
rwjohn1@.sbcglobal.net
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine sup
ports Post Alerts, Ratings, and Searching.Try deleting the registered server and then register it
again in Enterprise Manager.
In Enterprise Manager, right click on the server, select
Delete SQL Server Registration. Then right click on the
server group and select new server registration to register
the server again.
-Sue
On Thu, 28 Oct 2004 12:04:36 -0700, SqlJunkies User
<User@.-NOSPAM-SqlJunkies.com> wrote:

>SQL - 2000 running on Win2k Server
>I am unable to view my databases in enterprise manager but can see them in Query An
alyzer/ODBC. I had deleted a bunch of unused databases last night and after reboot
this morning Enterprise manager will not display any of my databases. What have I d
one
?
>rwjohn1@.sbcglobal.net
>--
>Posted using Wimdows.net NntpNews Component -
>Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports P
ost Alerts, Ratings, and Searching.

No Commit at end of program processing on 2005

Hi All,
I have written some ETL software that allows the user to turn off
autocommit and then set the commit frequency. It is C++ talking via
ODBC.
We are testing on an SQL Server 2005 machine and the behavior we are
seeing is that the rows written after the last commit issued by the
program are not being reflected into the database. These are the
error messages...
It seems like 2005 is not performing a commit when the program
terminates successfully. So rows written between the last commit
issued by the program and program close are not showing up in the
database.
This seems strange as 2000 did issue a commit for these message at the
end of processing...that is...if we used autocommit turned off and
committed every say 10,000 rows...the messages that were written
after the last commmit have always been there...same on oracle and
other databases..
Is there a database level option to make a commit happen at the end of
processing? Or perhaps an option for the MSFT SQL Server ODBC driver
to commit when the connection is closed?
Thanks
Peter
www.peternolan.comHi Peter
"Peter Nolan" wrote:
> Hi All,
> I have written some ETL software that allows the user to turn off
> autocommit and then set the commit frequency. It is C++ talking via
> ODBC.
> We are testing on an SQL Server 2005 machine and the behavior we are
> seeing is that the rows written after the last commit issued by the
> program are not being reflected into the database. These are the
> error messages...
> It seems like 2005 is not performing a commit when the program
> terminates successfully. So rows written between the last commit
> issued by the program and program close are not showing up in the
> database.
> This seems strange as 2000 did issue a commit for these message at the
> end of processing...that is...if we used autocommit turned off and
> committed every say 10,000 rows...the messages that were written
> after the last commmit have always been there...same on oracle and
> other databases..
> Is there a database level option to make a commit happen at the end of
> processing? Or perhaps an option for the MSFT SQL Server ODBC driver
> to commit when the connection is closed?
> Thanks
> Peter
> www.peternolan.com
>
I am not sure why you are setting autocommit off!! If you have not
explicitly started a transaction or you are using implicit transaction any
data changed after the transaction (implicitly or explicitly) started will be
rolled back. If you allowed autocommit to be on and you did not explicitly
start the transaction then the data changed will be committed.
I don't think this behaviour has changed, but you it is not good practice to
assume that a feature of the driver is going be a shortcut to handling the
transactions properly.
Johnsql

nimdaE + ODBC

i was infected by nimdaE. when i eradicated it, i erased 3 odbc.dll files. from that time, i became unable to use my db connections (access and sqlserver).
what can i do ?
thanks.Download and install the MDAC components from this page:

http://www.microsoft.com/data/download.htm

If you are using Windows XP, then you need MDAC 2.7, otherwise you can use MDAC 2.6 RTM or MDAC 2.6 SP1.

This should restore the missing DLL files and update your drivers.