MS SQL Server vs MySQL
am 02.03.2006 23:07:10 von John.Cook
Can someone give me some pointers and/or advise on MS SQL server vs
MySQL. Obviously in this group the bias will be towards MySQL and mine
is getting that way in a hurry.
I'm trying to do a Visual Basic database app, using VB .Net 2003. Yes,
I know about the guy who does all the VB-mySQL stuff and have read some
of his work.
The problem I'm having is just getting MS SQL to do what I want, when
MySQL does it without a problem. For example, I tried to import data
from a delimited file into MS SQL server. What a pain it was! Even
with their "wizard" it was harder than using a mySQL command line cause
the wizard didn't work as expected.
Once I finally got data into a table, I wanted to move it to another,
like this:
Insert into newtable select field1, field12, ... Field6 from oldtable;
Not rocket science, right? MS argued with me, said I couldn't insert a
NULL into one field, when I wasn't trying to. MySQL just did it and did
it right the first time.
Frustrated in New Hampshire.
--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org
Re: MS SQL Server vs MySQL
am 03.03.2006 04:33:03 von bk
Quoting John.Cook@bench.com:
> The problem I'm having is just getting MS SQL to do what I want, when
> MySQL does it without a problem. For example, I tried to import data
> from a delimited file into MS SQL server. What a pain it was! Even
> with their "wizard" it was harder than using a mySQL command line cause
> the wizard didn't work as expected.
Take a look at bcp. There is also the BULK INSERT command. Both of
those can be
run without using the data import/export wizard, which, by the way, is Data
Transformation Services, an add-on to SQL Server. It gets beefed up as SQL
Server Integration Services in SQL Server 2005.
>
> Once I finally got data into a table, I wanted to move it to another,
> like this:
>
> Insert into newtable select field1, field12, ... Field6 from oldtable;
>
I'm assuming you used SELECT INTO. You can specify a NULL value, however, you
must still give the column name using an alias. An example would be:
USE Northwind
GO
SELECT OrderID, CustomerID, EmployeeID, NULL [NullableColumn]
INTO OrderTransfer
FROM Orders
--
K. Brian Kelley, bk@warpdrivedesign.org
Enterprise Systems Architect/DBA, AgFirst Farm Credit Bank
Author: Start to Finish Guide to SQL Server Performance Monitoring
Contributing Author: Best of SQLServerCentral.com Series
Regular Columnist (Security): SQLServerCentral.com and SQL Server Standard
Magazine
Member, SANS GIAC Advisory Board
http://www.truthsolutions.com/
--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org
RE: MS SQL Server vs MySQL
am 03.03.2006 15:49:37 von John.Cook
I tried bcp too. It behaved just like the wizard did: hard to use,
cryptic error messages if any, etc.
*sigh* This sounds like all my previous experience with "real" software
tools. They assume you already know what you are doing and don't really
want to explain it to you if you don't.
-----Original Message-----
From: K. Brian Kelley [mailto:bk@warpdrivedesign.org]=20
Sent: Thursday, March 02, 2006 10:33 PM
To: win32@lists.mysql.com
Subject: Re: MS SQL Server vs MySQL
Quoting John.Cook@bench.com:
> The problem I'm having is just getting MS SQL to do what I want, when=20
> MySQL does it without a problem. For example, I tried to import data=20
> from a delimited file into MS SQL server. What a pain it was! Even=20
> with their "wizard" it was harder than using a mySQL command line=20
> cause the wizard didn't work as expected.
Take a look at bcp. There is also the BULK INSERT command. Both of=20
those can be
run without using the data import/export wizard, which, by the way, is
Data Transformation Services, an add-on to SQL Server. It gets beefed up
as SQL Server Integration Services in SQL Server 2005.
>
> Once I finally got data into a table, I wanted to move it to another,=20
> like this:
>
> Insert into newtable select field1, field12, ... Field6 from oldtable;
>
I'm assuming you used SELECT INTO. You can specify a NULL value,
however, you must still give the column name using an alias. An example
would be:
USE Northwind
GO
SELECT OrderID, CustomerID, EmployeeID, NULL [NullableColumn] INTO
OrderTransfer FROM Orders
--=20
K. Brian Kelley, bk@warpdrivedesign.org
Enterprise Systems Architect/DBA, AgFirst Farm Credit Bank
Author: Start to Finish Guide to SQL Server Performance Monitoring
Contributing Author: Best of SQLServerCentral.com Series Regular
Columnist (Security): SQLServerCentral.com and SQL Server Standard
Magazine Member, SANS GIAC Advisory Board http://www.truthsolutions.com/
--=20
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe:
http://lists.mysql.com/win32?unsub=3Djohn.cook@bench.com
--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org
RE: MS SQL Server vs MySQL
am 03.03.2006 15:51:52 von Leif Johnston
Yep SQL Books online...
-----Original Message-----
From: John.Cook@bench.com [mailto:John.Cook@bench.com]
Sent: Friday, March 03, 2006 9:50 AM
To: bk@warpdrivedesign.org; win32@lists.mysql.com
Subject: RE: MS SQL Server vs MySQL
I tried bcp too. It behaved just like the wizard did: hard to use,
cryptic error messages if any, etc.
*sigh* This sounds like all my previous experience with "real" software
tools. They assume you already know what you are doing and don't really
want to explain it to you if you don't.
-----Original Message-----
From: K. Brian Kelley [mailto:bk@warpdrivedesign.org]
Sent: Thursday, March 02, 2006 10:33 PM
To: win32@lists.mysql.com
Subject: Re: MS SQL Server vs MySQL
Quoting John.Cook@bench.com:
> The problem I'm having is just getting MS SQL to do what I want, when
> MySQL does it without a problem. For example, I tried to import data
> from a delimited file into MS SQL server. What a pain it was! Even
> with their "wizard" it was harder than using a mySQL command line
> cause the wizard didn't work as expected.
Take a look at bcp. There is also the BULK INSERT command. Both of
those can be
run without using the data import/export wizard, which, by the way, is
Data Transformation Services, an add-on to SQL Server. It gets beefed up
as SQL Server Integration Services in SQL Server 2005.
>
> Once I finally got data into a table, I wanted to move it to another,
> like this:
>
> Insert into newtable select field1, field12, ... Field6 from oldtable;
>
I'm assuming you used SELECT INTO. You can specify a NULL value,
however, you must still give the column name using an alias. An example
would be:
USE Northwind
GO
SELECT OrderID, CustomerID, EmployeeID, NULL [NullableColumn] INTO
OrderTransfer FROM Orders
--
K. Brian Kelley, bk@warpdrivedesign.org
Enterprise Systems Architect/DBA, AgFirst Farm Credit Bank
Author: Start to Finish Guide to SQL Server Performance Monitoring
Contributing Author: Best of SQLServerCentral.com Series Regular
Columnist (Security): SQLServerCentral.com and SQL Server Standard
Magazine Member, SANS GIAC Advisory Board http://www.truthsolutions.com/
--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe:
http://lists.mysql.com/win32?unsub=john.cook@bench.com
--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe:
http://lists.mysql.com/win32?unsub=leif@technologycatalyst.c om
--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org
Re: MS SQL Server vs MySQL
am 04.03.2006 01:17:38 von Stephen Cook
it feels the same when going the other way too (MS SQL Server ->
MySQL)... the fact of the matter is you have to learn new things, not
just assume your old knowledge will work on a different product by a
different vendor just because they do *basically* the same thing.
if you have specific questions rather than general complaints, look for
a MS SQL Server message board and ask (with details) there. I recommend
http://www.sqlservercentral.com/
John.Cook@bench.com wrote:
> I tried bcp too. It behaved just like the wizard did: hard to use,
> cryptic error messages if any, etc.
>
> *sigh* This sounds like all my previous experience with "real" software
> tools. They assume you already know what you are doing and don't really
> want to explain it to you if you don't.
>
> -----Original Message-----
> From: K. Brian Kelley [mailto:bk@warpdrivedesign.org]
> Sent: Thursday, March 02, 2006 10:33 PM
> To: win32@lists.mysql.com
> Subject: Re: MS SQL Server vs MySQL
>
>
> Quoting John.Cook@bench.com:
>
>
>>The problem I'm having is just getting MS SQL to do what I want, when
>>MySQL does it without a problem. For example, I tried to import data
>>from a delimited file into MS SQL server. What a pain it was! Even
>>with their "wizard" it was harder than using a mySQL command line
>>cause the wizard didn't work as expected.
>
>
> Take a look at bcp. There is also the BULK INSERT command. Both of
> those can be
> run without using the data import/export wizard, which, by the way, is
> Data Transformation Services, an add-on to SQL Server. It gets beefed up
> as SQL Server Integration Services in SQL Server 2005.
>
>
>>Once I finally got data into a table, I wanted to move it to another,
>>like this:
>>
>>Insert into newtable select field1, field12, ... Field6 from oldtable;
>>
>
>
> I'm assuming you used SELECT INTO. You can specify a NULL value,
> however, you must still give the column name using an alias. An example
> would be:
>
> USE Northwind
> GO
>
> SELECT OrderID, CustomerID, EmployeeID, NULL [NullableColumn] INTO
> OrderTransfer FROM Orders
>
--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org
RE: MS SQL Server vs MySQL
am 06.03.2006 14:14:20 von John.Cook
Actually I just went out and bought an Oreilly book on T-Sql which is MS
SQL specific. It details all the little things that MS does so I should
be OK now.
-John C.
-----Original Message-----
From: Stephen Cook [mailto:sclists@gmail.com]=20
Sent: Friday, March 03, 2006 7:18 PM
To: Cook, John
Cc: bk@warpdrivedesign.org; win32@lists.mysql.com
Subject: Re: MS SQL Server vs MySQL
it feels the same when going the other way too (MS SQL Server ->=20
MySQL)... the fact of the matter is you have to learn new things, not=20
just assume your old knowledge will work on a different product by a=20
different vendor just because they do *basically* the same thing.
if you have specific questions rather than general complaints, look for=20
a MS SQL Server message board and ask (with details) there. I recommend=20
http://www.sqlservercentral.com/
John.Cook@bench.com wrote:
> I tried bcp too. It behaved just like the wizard did: hard to use,=20
> cryptic error messages if any, etc.
>=20
> *sigh* This sounds like all my previous experience with "real"=20
> software tools. They assume you already know what you are doing and=20
> don't really want to explain it to you if you don't.
>=20
> -----Original Message-----
> From: K. Brian Kelley [mailto:bk@warpdrivedesign.org]
> Sent: Thursday, March 02, 2006 10:33 PM
> To: win32@lists.mysql.com
> Subject: Re: MS SQL Server vs MySQL
>=20
>=20
> Quoting John.Cook@bench.com:
>=20
>=20
>>The problem I'm having is just getting MS SQL to do what I want, when
>>MySQL does it without a problem. For example, I tried to import data=20
>>from a delimited file into MS SQL server. What a pain it was! Even=20
>>with their "wizard" it was harder than using a mySQL command line=20
>>cause the wizard didn't work as expected.
>=20
>=20
> Take a look at bcp. There is also the BULK INSERT command. Both of
> those can be
> run without using the data import/export wizard, which, by the way, is
> Data Transformation Services, an add-on to SQL Server. It gets beefed
up
> as SQL Server Integration Services in SQL Server 2005.
>=20
>=20
>>Once I finally got data into a table, I wanted to move it to another,
>>like this:
>>
>>Insert into newtable select field1, field12, ... Field6 from oldtable;
>>
>=20
>=20
> I'm assuming you used SELECT INTO. You can specify a NULL value,=20
> however, you must still give the column name using an alias. An=20
> example would be:
>=20
> USE Northwind
> GO
>=20
> SELECT OrderID, CustomerID, EmployeeID, NULL [NullableColumn] INTO=20
> OrderTransfer FROM Orders
>=20
--=20
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe:
http://lists.mysql.com/win32?unsub=3Djohn.cook@bench.com
--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org