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
SQLSRV_ERRORS(3)														  SQLSRV_ERRORS(3)

sqlsrv_errors - Returns error and warning information about the last SQLSRV operation performed

SYNOPSIS
mixed sqlsrv_errors ([int $errorsOrWarnings]) DESCRIPTION
Returns error and warning information about the last SQLSRV operation performed. PARAMETERS
o $errorsOrWarnings - Determines whether error information, warning information, or both are returned. If this parameter is not supplied, both error information and warning information are returned. The following are the supported values for this parameter: SQLSRV_ERR_ALL, SQL- SRV_ERR_ERRORS, SQLSRV_ERR_WARNINGS. RETURN VALUES
If errors and/or warnings occurred on the last sqlsrv operation, an array of arrays containing error information is returned. If no errors and/or warnings occurred on the last sqlsrv operation, NULL is returned. The following table describes the structure of the returned arrays: Array returned by sqlsrv_errors +---------+---------------------------------------------------+ | Key | | | | | | | Description | | | | +---------+---------------------------------------------------+ |SQLSTATE | | | | | | | For errors that originate from the ODBC driver, | | | the SQLSTATE returned by ODBC. For errors that | | | originate from the Microsoft Drivers for PHP for | | | SQL Server, a SQLSTATE of IMSSP. For warnings | | | that originate from the Microsoft Drivers for PHP | | | for SQL Server, a SQLSTATE of 01SSP. | | | | | code | | | | | | | For errors that originate from SQL Server, the | | | native SQL Server error code. For errors that | | | originate from the ODBC driver, the error code | | | returned by ODBC. For errors that originate from | | | the Microsoft Drivers for PHP for SQL Server, the | | | Microsoft Drivers for PHP for SQL Server error | | | code. | | | | |message | | | | | | | A description of the error. | | | | +---------+---------------------------------------------------+ EXAMPLES
Example #1 functionname(3) example <?php $serverName = "serverName/sqlexpress"; $connectionInfo = array( "Database"=>"dbName", "UID"=>"username", "PWD"=>"password"); $conn = sqlsrv_connect( $serverName, $connectionInfo); if( $conn === false ) { die( print_r( sqlsrv_errors(), true)); } /* Set up a query to select an invalid column name. */ $sql = "SELECT BadColumnName FROM Table_1"; /* Execution of the query will fail because of the bad column name. */ $stmt = sqlsrv_query( $conn, $sql ); if( $stmt === false ) { if( ($errors = sqlsrv_errors() ) != null) { foreach( $errors as $error ) { echo "SQLSTATE: ".$error[ 'SQLSTATE']."<br />"; echo "code: ".$error[ 'code']."<br />"; echo "message: ".$error[ 'message']."<br />"; } } } ?> NOTES
By default, warnings generated on a call to any SQLSRV function are treated as errors. This means that if a warning occurs on a call to a SQLSRV function, the function returns FALSE. However, warnings that correspond to SQLSTATE values 01000, 01001, 01003, and 01S02 are never treated as errors. For information about changing this behavior, see sqlsrv_configure(3) and the WarningsReturnAsErrors setting. SEE ALSO
sqlsrv_configure(3). PHP Documentation Group SQLSRV_ERRORS(3)