Why Move to MySQL from Microsoft SQL Server?

 
Thread Tools Search this Thread
Top Forums Web Development MySQL DevZone RSS Why Move to MySQL from Microsoft SQL Server?
# 1  
Old 05-04-2009
Why Move to MySQL from Microsoft SQL Server?

Before we get started, let me say that I always liked being a SQL Server DBA. My database experience started with DB2, then Teradata, followed by Oracle, and then SQL Server (and then a little bit of Sybase after that, followed by MySQL). Coming from the other databases, I found SQL Server the easiest and quickest to learn at the time, but of course, a lot of that had to do with the fact that Microsoft was really the only database vendor around then (I started with version 4.2 of SQL Server) that shipped any decent GUI management tools with their server. Take the tools away, and you basically had Sybase on Windows with the ISQL command line tool, which was not pretty by any means.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. SuSE

Syslog-ng 3.0.7 fails to insert into microsoft sql server

Dear All, Im currently configuring syslog-ng on SUSE Linux 10 SP2 to communicate with microsoft sql server 2005. I have installed freeTds 8.0. Tested TSQL ..works fine ISQL works fine. when testing with syslog-ng destination d_mssql { sql(type(mssql) host("ip address")... (0 Replies)
Discussion started by: SystemEng
0 Replies

2. Shell Programming and Scripting

Connection to Microsoft SQL Server

Hi, I am using "ksh" and trying to connect to the Microsoft SQL Server but it gives an error that is: DB-LIBRARY error: Unexpected EOF from SQL Server. Can any one please help me to resolve this issue. And i am using Putty to connect to the Unix server. Thanks (3 Replies)
Discussion started by: anupdas
3 Replies

3. Shell Programming and Scripting

(perl) Microsoft SQL Server client for solaris. cant find it...

let me save everyone the pain that it caused me. This is all free. And make sure it is in this order 1) make sure you have the latest version of perl installed 2) make sure you have NET:aemon installed 3) make sure you have RPC::PlServer & PlClient (the bundle has both) 4) make sure... (3 Replies)
Discussion started by: Optimus_P
3 Replies
Login or Register to Ask a Question
ODBC_PREPARE(3) 							 1							   ODBC_PREPARE(3)

odbc_prepare - Prepares a statement for execution

SYNOPSIS
resource odbc_prepare (resource $connection_id, string $query_string) DESCRIPTION
Prepares a statement for execution. The result identifier can be used later to execute the statement with odbc_execute(3). Some databases (such as IBM DB2, MS SQL Server, and Oracle) support stored procedures that accept parameters of type IN, INOUT, and OUT as defined by the ODBC specification. However, the Unified ODBC driver currently only supports parameters of type IN to stored procedures. PARAMETERS
o $connection_id -The ODBC connection identifier, see odbc_connect(3) for details. o $query_string - The query string statement being prepared. RETURN VALUES
Returns an ODBC result identifier if the SQL command was prepared successfully. Returns FALSE on error. EXAMPLES
Example #1 odbc_execute(3) and odbc_prepare(3) example In the following code, $success will only be TRUE if all three parameters to myproc are IN parameters: <?php $a = 1; $b = 2; $c = 3; $stmt = odbc_prepare($conn, 'CALL myproc(?,?,?)'); $success = odbc_execute($stmt, array($a, $b, $c)); ?> If you need to call a stored procedure using INOUT or OUT parameters, the recommended workaround is to use a native extension for your database (for example, mssql for MS SQL Server, or oci8 for Oracle). SEE ALSO
odbc_execute(3). PHP Documentation Group ODBC_PREPARE(3)