| Newsgroups |
gmane.comp.db.mysql.windows |
| Message-ID |
<[email protected]> |
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/[email protected]