R: connecting SQL server on W and PHP/MYSQL on Unix

Views from linked server are really "equivelant to link tables in
Access" ??
I have not found yet the mean to write data on MySQL linked server ... 
Someone can explain me ?

Really really many thanks for every suggestion.

Pier


> -----Messaggio originale-----
> Da: Mike Harknett [mailto:MikeH@xxxxxxxxxxxxxx] 
> Inviato: mercoledì 10 marzo 2004 23.13
> A: Daniel Kasak; lalit jairath; myodbc@xxxxxxxxxxxxxxx
> Oggetto: RE: connecting SQL server on W and PHP/MYSQL on Unix
> 
> 
> I found that if I set up views in SQL Server using My SQL as 
> a linked server (which is equivelant to link tables in 
> Access) the I could create queries that joined the data from 
> both sources, this, for me, gave the advantage of a single 
> data source for Crystal. which is what the dbrief I had was, 
> performance seems ok and it gives me the advantage (such as 
> it is) of being able to use stored procs etc in SQL server
>  
> cheers
>  
> Mike
> -----Original Message-----
> From: Daniel Kasak [mailto:dkasak@xxxxxxxxxxxxxxxxxxxx]
> Sent: Thursday, 11 March 2004 11:12
> To: lalit jairath; myodbc@xxxxxxxxxxxxxxx
> Subject: Re: connecting SQL server on W and PHP/MYSQL on Unix
> 
> 
> lalit jairath wrote: 
> 
> Hi Mike,
> 
>  
> 
> So is it possible to communicate both ways- accessing MSSQL 
> from MySQL (unix
> machine) as well as MySQL from MSSQL. I'm more interested in 
> accessing MSSQL server from MySQL.
> 
>  
> 
> Could you  please point me to a detailed doc/code. I'm not 
> very familiar with MSSQL (un)fortunately.
> 
>  
> 
> Thank you much.
> 
>  
> 
> Lalit
> 
>   
> 
> MySQL can't talk to MS SQL directly.
> You have to do the communication via a language which has 
> drivers for both. I use the FreeTDS libraries to talk to SQL 
> Server from both Perl and PHP. It works in the limited cases 
> I've had to do it in, but note that you can't run 
> cross-database queries ... MS Access is the only app I know 
> of that lets you do that.
> 
> As for examples, if you can talk to MySQL in Perl, then it's 
> exactly the same deal with SQL Server. Under PHP, it's a 
> little different. There are separate, db-specific functions, eg:
> 
> MySQL:
> mysql_connect, mysql_query, mysql_fetch_array
> 
> SQL Server:
> mssql_connect, mssql_query, mssql_fetch_array
> 
> Pretty annoying if you want to move your data elsewhere. 
> There are a couple of wrappers around php's db functions that 
> give you a db-neutral set of tools. I think one of them is 
> ADODB ( not to be confused with M$'s ADO / ADODB stuff ). 
> Have a look at it if you don't want pain when migrating your data.
> 
> For speed ( query speed and development speed ) I recommend 
> having all your data in one database, or at the least all of 
> the data that is typically queried together. Running queries 
> against multiple DBs is a major pain, inefficient, and yucky.
> 
> Dan
> 
> 
> -- 
> Daniel Kasak 
> IT Developer 
> NUS Consulting Group
> Level 5, 77 Pacific Highway
> North Sydney, NSW, Australia 2060 
> T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 
> email: dkasak@xxxxxxxxxxxxxxxxxxxx 
> <mailto:dkasak@xxxxxxxxxxxxxxxxxxxx>  
> website: 
> http://www.nusconsulting.com.au <http://www.nusconsulting.com.au>  
> 
> -- 
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe:    
> http://lists.mysql.com/myodbc?> unsub=diPierre@xxxxxxxxxxxxxxxxxxxxx
> 
> 


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:    http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@xxxxxxxxxxx