Another issue with SQLServer 2005

Remote servers.

Our main database is an Ingres database, the web database is now SQLServer 2005. Occasionally we need to link data from both(for checks etc). Unfortunately Ingres cannot do cross catalog queries(no idea why, but as Postgres can't either, I blame the designer). Fortunately if you link in a remote server in SQLServer you can perform cross catalog selects. Simply set up a remote server for each Ingres catalog and use :

select *

from ingresdb1..owner.table_name

union all

from ingresdb2..owner.table_name


making sure you have set ansi_null and ansi_warnings to on.

However after I set up an ODBC connection to Ingres on the SQLServer 2005 database(which is no fun either as you need to set up IngresNet first and log in using the admin password) and then set up a remote server to Ingres in the SQLServer manager I ran a test query, it brought the whole server down.

Now MySQL cannot link to remote servers(that I know of), but I have yet to ask it to do something I know it can do and have it crash completely, I used to be able to say that was mostly true of SQLServer, but the 2005 server has been online for two weeks and crashed more than a dozen times in that period.

DON'T USE IT! EVER!