[KLUG Members] MySQL acting as if it is SQL Server

[Chris Hansen]

>>But if I had
>>to do it I'd look into ODBC.
>>    
>>
>OK, so you are thinking that the SQL Server client piece of software has
>configurable enough settings in it to get it to work in ODBC mode, and just
>happen to point its DSN at the MySQL box then, and see if things just magically
>work.
>  
>
The purpose of ODBC is to provide a standard API layer onto different 
database management systems.  It does the translation, and would be a 
good fit for something like this, provided the application was designed 
to use a ODBC DSN.  Setting up an ODBC data source on each workstation 
that requires access to a SQL server is kind of a pain though, and a bit 
messy, so having ADO / RDO get it's DSN, Data Provider type, and other 
info straight from the code seems to be preferred, and probably posses a 
problem for your plans for a seemless and painless drop in replacement.  
If you can configure not only the server IP, but also what data provider 
to use in the applications configuration you might be ok, although, 
probably not.  As for passing off a mySQL server as a MS SQL server, as 
you probably realize; besides listening on different ports (mysql 
tcp/3306, mssql tcp/1433), the data transmitted by clients to interact 
with / query the server is different too =(  Since RDO, DAO, ADO, or 
whatever it is your application is using calls libs to deal with the 
nitty gritty of that convo for you what you'd need (I would think 
anyhow) in order to not change your code in the least would be some kind 
of message-twisting-proxy-server-from-heck to translate what RDO/DAO/ADO 
is saying into something mysql would like to hear.  If you manage to 
summon such a beast to do your bidding it would probably be something of 
interest to other folks on the list, but I'm skeptical as to the 
existence of such a thing.  If you're using .NET there are third party 
Data Provider modules you can get that let ADO.NET speak to mySQL, and I 
would think the same could be true for non- .NET framework apps,  
however, in either case, it'd still likely mean a required change to 
your code.  I'm not one of those super smart MS developers though, so if 
someone corrects me on any of this, I'd suggest you listen to them ;)  
Hope this is helpful non-help.