I have a Dell Latitude D505 running a fresh copy of XP SP2. I am trying to
create an ODBC System DSN to our SQL 2k server. The SQL Server has about 6
instances installed on it. When I pull down the drop down box to select a
server, only the server name exists, but none of the instances. This is
working on 180 desktops configured off the same image of XP.
Basically, I am seeing:
<Server Name> instead of <Server Name>\<Instance>
<Server Name>\<Instance 2>
Just so you know, I have already updated the MDAC version, so that cannot
be the issue.
|||This is all set now. My issue was the wireless network being enabled. As
soon as I disabled it, it worked fine.
Showing posts with label odbc. Show all posts
Showing posts with label odbc. Show all posts
Monday, March 26, 2012
Named Instance not Displaying Only Server Name
I have a Dell Latitude D505 running a fresh copy of XP SP2. I am trying to
create an ODBC System DSN to our SQL 2k server. The SQL Server has about 6
instances installed on it. When I pull down the drop down box to select a
server, only the server name exists, but none of the instances. This is
working on 180 desktops configured off the same image of XP.
Basically, I am seeing:
<Server Name> instead of <Server Name>\<Instance>
<Server Name>\<Instance 2>Just so you know, I have already updated the MDAC version, so that cannot
be the issue.|||This is all set now. My issue was the wireless network being enabled. As
soon as I disabled it, it worked fine.
create an ODBC System DSN to our SQL 2k server. The SQL Server has about 6
instances installed on it. When I pull down the drop down box to select a
server, only the server name exists, but none of the instances. This is
working on 180 desktops configured off the same image of XP.
Basically, I am seeing:
<Server Name> instead of <Server Name>\<Instance>
<Server Name>\<Instance 2>Just so you know, I have already updated the MDAC version, so that cannot
be the issue.|||This is all set now. My issue was the wireless network being enabled. As
soon as I disabled it, it worked fine.
Monday, March 12, 2012
mySQL to MS SQL 2005 - ODBC?
Hi,
Posted this at the tail end of another thread but that one appears to have died. Thought I'd try again since my question was a little distinct from that one anyway, but apologies if I've committed forum sacrilege.
I am having a heck of a time trying to migrate a fairly simple MySQL DB to SQL Server I am using SQL Server 2005 Standard Edition SP1.
I tried following MS' instructions in this article:
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/mysql.mspx
hoping that what worked for 2000 would work for 2005, since the principles seem sound. No luck. I can create the ODBC link, but SQL Management Studio, the '.NET provider for ODBC' option doesn't give me the choice to copy tables - only to write a query.
I tried making sense of the on-line help and was able to create the ODBC connection in the 'Business Intelligence Development Studio' but I have no idea what I am looking at with respect to creating control & data flow in an SSIS package. All I know is that I could do what I am trying to do in SQL Server 2000 quite easily - the MySQL database in question is quite simple (but not small). I am pretty amateurish when it comes to SQL administration, but this seems to me unnecessarily difficult.
I tried the MySQL OLE connector from sourceforge and was able to properly set up a test connection and get the 'copy tables' option, but then when I hit 'next' I get:
MYSqlProv 3.9 failed with no error message available, result code E_ABORT(0x80004004) (System.Data)
Am I missing some stupendously easy way around this, or did I torpedo this client when I promoted moving them from MySQL to MS SQL Server on account of my not being a full-time SQL Server DBA who knows how to use the Business Intelligence Development Studio?
did you try using the import/export wizard in management studio?|||Yes. The instructions in the support kb link above basically say to use the import/export function (though it's referring to 2000, so it's not the studio) and that the ODBC link should be there. In Management Studio, the only reference to the ODBC link is the '.NET Provider for ODBC' which 'works' in that I can query the data source, but I can't copy tables directly. There are dozens of tables.
What I am really looking for is a simple, straightforward ODBC data link provider that works with Management Studio. SQL Server 2000 had it.
|||After trying to find a solution to this that didn't involve writing over three dozen queries, I installed MS Access, used a regular ODBC link to import the MySQL database to Access (this took about ten seconds), and then the SQL Server 2005 import/export wizard to import from Access.
SQL Server lost this round. I'll be the first to admit I'm no pro with the myriad of things SQL Server does tremendously well, but this one is so basic it's astonishing that two earlier products can perform this basic task with much more ease and simplicity than SQL Server can - assuming SQL Server can do it at all. I certainly couldn't get it to.
|||I wholeheartedly agree. Importing data from a mySQL database should be a matter of a few seconds in setup, and I'm sitting here requisitioning a copy of MS Access so I can get data out of a database I used to be able to import easily.
They seriously dropped the ball on not having *real* ODBC support for import services like they've had in previous versions.
Wake up! If I'm migrating TO SQL Server you should be HAPPY and do everything in your power to ensure that the import experience is as seamless as possible. Because now, if I don't get approved for Access, well we're going to use MySQL instead of SQL Server 2005, or any later version thereof.
I hope someone there recognizes the size of this... blunder.
mySQL to MS SQL 2005 - ODBC?
Hi,
Posted this at the tail end of another thread but that one appears to have died. Thought I'd try again since my question was a little distinct from that one anyway, but apologies if I've committed forum sacrilege.
I am having a heck of a time trying to migrate a fairly simple MySQL DB to SQL Server I am using SQL Server 2005 Standard Edition SP1.
I tried following MS' instructions in this article:
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/mysql.mspx
hoping that what worked for 2000 would work for 2005, since the principles seem sound. No luck. I can create the ODBC link, but SQL Management Studio, the '.NET provider for ODBC' option doesn't give me the choice to copy tables - only to write a query.
I tried making sense of the on-line help and was able to create the ODBC connection in the 'Business Intelligence Development Studio' but I have no idea what I am looking at with respect to creating control & data flow in an SSIS package. All I know is that I could do what I am trying to do in SQL Server 2000 quite easily - the MySQL database in question is quite simple (but not small). I am pretty amateurish when it comes to SQL administration, but this seems to me unnecessarily difficult.
I tried the MySQL OLE connector from sourceforge and was able to properly set up a test connection and get the 'copy tables' option, but then when I hit 'next' I get:
MYSqlProv 3.9 failed with no error message available, result code E_ABORT(0x80004004) (System.Data)
Am I missing some stupendously easy way around this, or did I torpedo this client when I promoted moving them from MySQL to MS SQL Server on account of my not being a full-time SQL Server DBA who knows how to use the Business Intelligence Development Studio?
did you try using the import/export wizard in management studio?|||Yes. The instructions in the support kb link above basically say to use the import/export function (though it's referring to 2000, so it's not the studio) and that the ODBC link should be there. In Management Studio, the only reference to the ODBC link is the '.NET Provider for ODBC' which 'works' in that I can query the data source, but I can't copy tables directly. There are dozens of tables.
What I am really looking for is a simple, straightforward ODBC data link provider that works with Management Studio. SQL Server 2000 had it.
|||After trying to find a solution to this that didn't involve writing over three dozen queries, I installed MS Access, used a regular ODBC link to import the MySQL database to Access (this took about ten seconds), and then the SQL Server 2005 import/export wizard to import from Access.
SQL Server lost this round. I'll be the first to admit I'm no pro with the myriad of things SQL Server does tremendously well, but this one is so basic it's astonishing that two earlier products can perform this basic task with much more ease and simplicity than SQL Server can - assuming SQL Server can do it at all. I certainly couldn't get it to.
|||I wholeheartedly agree. Importing data from a mySQL database should be a matter of a few seconds in setup, and I'm sitting here requisitioning a copy of MS Access so I can get data out of a database I used to be able to import easily.
They seriously dropped the ball on not having *real* ODBC support for import services like they've had in previous versions.
Wake up! If I'm migrating TO SQL Server you should be HAPPY and do everything in your power to ensure that the import experience is as seamless as possible. Because now, if I don't get approved for Access, well we're going to use MySQL instead of SQL Server 2005, or any later version thereof.
I hope someone there recognizes the size of this... blunder.
MySql SSIS Hangs with ODBC Drivers
Hi, we are writting a SQL Server Integration Services package to import data from a MySql database to a Sql Database.
We are using ODBC 3.51 Drivers to connect to the MySql Database in SSIS. The package runs perfectly in design mode. When we schedule the package to run, the package seems to hang about 1/3 of the times.
What can this be. We used to the package and ran it from a Sql Server 2005 to a Sql Server 2005 database. This setup works perfectly. When i'm doing MySql to Sql Server 2005, 1/3 of the times, it does not work.
Can anyone help me with this?
Giovan Gentile
Ayuda Media Systems
Implementation of ODBC is different by different vendors and for each different data source (after all, that was the goal of it). Therefore because an ODBC connection works fine with a particular source database is no guarantee an ODBC connection against a different database will work for your purposes- _the implementation code is totally different_.
Also, allowing implicit data type conversions (in my experience) is often the source of problems in moving data between different RDBMS implementations. Create views in the source to explicitly make any data type conversions required for the Sql Server destination. That can only help...
Ken
|||Hello Ken,
Importing from mySQL with the 3.51 works fine for me.
Does your package "hangs" on big resulsets specifically ? If so, it could be that your datasource in configured to cache results from mySQL before making them available to the consumer. That's the default behavior.
Turning on "Allow big results" and "Don't cache result (forward cursor only)" options at the ODBC datasource level fixed the pb for me.
Hope it helps.
--
Jerome
Friday, March 9, 2012
MySQL linked in SQLServer
:confused: Hallo! I'm trying to link a MySql 's DB in SQLServer with ODBC: the operation was susseful but I'm not able to read and write/update the data.
HELP ME PLEASE!!!
silvia, ItalyI'm confused by "the operation was successful" followed by "I'm not able to read and write/update the data". I don't understand what you mean.
Check out sp_addlinkedserver (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sp_adda_8gqa.asp). If you tinker with the link a bit, you ought to be able to get it in Italian if that helps.
The quickest and easiest way is to use the ODBC link that uses a system DSN. That way if you change MySQL servers all you do is fix the DSN and your SQL Server link works.
A more complex but more powerful way is to use the ODBC with a connection string. It is kind of like a car with a manual transmission... You have more control, but you have to pay more attention to how you use it.
-PatP|||IF I RIGHT CLICK IN A TABLE IN THE REMOTE SERVER, I FIND ONLY "COPY" AND "?". IT'S CORRECT??
ciao e molte grazie!!!
silvia|||Without knowing a lot about your system(s), I can only guess. What you describe is one possible outcome of a linked server to MySQL that is actually fairly common.
There are two problems that commonly interfere with cross-server operations.
The most common problem is that the MySQL login used by the ODBC connection doesn't have sufficient permissions within MySQL. The only real solution for that problem is to get more permissions by either changing the MySQL login used by the ODBC connection to one that has more permissions, or by getting the MySQL administrator to grant the MySQL login used by the ODBC connection more permissions.
The next most common problem is that the MySQL ODBC driver on the SQL Server itself is old. The ODBC drivers have improved a lot over time. Older drivers (sometimes even a few months can make a real difference) are often a problem. Visit the MySQL site to see if you can get newer ODBC drivers.
-PatP|||I have set up a link server to MySQL 5
Sometimes mySQL do require a password. The following link server works for me.
EXEC sp_addlinkedserver ‘mysqlDB’, ‘MySQL’, ‘MSDASQL’, Null, Null, ‘Driver={MySQL ODBC 3.51 Driver};DB=mysql_db;SERVER=mysql_server;uid=userna me;pwd=password’
If MSDTC is running you can use the following to create a view without a link server.
SELECT * FROM OPENROWSET(’MSDASQL’,'Driver={MySQL ODBC 3.51 Driver};DB=mysql_db;SERVER=mysql_server;uid=userna me;pwd=password’, ‘SELECT * from table’)
If you get an error like
OLE DB provider 'MSDASQL' returned an unexpected data length for the fixed-length column '[MSDASQL].pensionNo'. The expected data length is 7, while the returned data length is 5.
You can resolve this using the option tag
'Driver={MySQL ODBC 3.51 Driver};DB=mysql_db;SERVER=mysql_server;option=512 ;uid=username;pwd=password'
Notice the option=512
HELP ME PLEASE!!!
silvia, ItalyI'm confused by "the operation was successful" followed by "I'm not able to read and write/update the data". I don't understand what you mean.
Check out sp_addlinkedserver (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sp_adda_8gqa.asp). If you tinker with the link a bit, you ought to be able to get it in Italian if that helps.
The quickest and easiest way is to use the ODBC link that uses a system DSN. That way if you change MySQL servers all you do is fix the DSN and your SQL Server link works.
A more complex but more powerful way is to use the ODBC with a connection string. It is kind of like a car with a manual transmission... You have more control, but you have to pay more attention to how you use it.
-PatP|||IF I RIGHT CLICK IN A TABLE IN THE REMOTE SERVER, I FIND ONLY "COPY" AND "?". IT'S CORRECT??
ciao e molte grazie!!!
silvia|||Without knowing a lot about your system(s), I can only guess. What you describe is one possible outcome of a linked server to MySQL that is actually fairly common.
There are two problems that commonly interfere with cross-server operations.
The most common problem is that the MySQL login used by the ODBC connection doesn't have sufficient permissions within MySQL. The only real solution for that problem is to get more permissions by either changing the MySQL login used by the ODBC connection to one that has more permissions, or by getting the MySQL administrator to grant the MySQL login used by the ODBC connection more permissions.
The next most common problem is that the MySQL ODBC driver on the SQL Server itself is old. The ODBC drivers have improved a lot over time. Older drivers (sometimes even a few months can make a real difference) are often a problem. Visit the MySQL site to see if you can get newer ODBC drivers.
-PatP|||I have set up a link server to MySQL 5
Sometimes mySQL do require a password. The following link server works for me.
EXEC sp_addlinkedserver ‘mysqlDB’, ‘MySQL’, ‘MSDASQL’, Null, Null, ‘Driver={MySQL ODBC 3.51 Driver};DB=mysql_db;SERVER=mysql_server;uid=userna me;pwd=password’
If MSDTC is running you can use the following to create a view without a link server.
SELECT * FROM OPENROWSET(’MSDASQL’,'Driver={MySQL ODBC 3.51 Driver};DB=mysql_db;SERVER=mysql_server;uid=userna me;pwd=password’, ‘SELECT * from table’)
If you get an error like
OLE DB provider 'MSDASQL' returned an unexpected data length for the fixed-length column '[MSDASQL].pensionNo'. The expected data length is 7, while the returned data length is 5.
You can resolve this using the option tag
'Driver={MySQL ODBC 3.51 Driver};DB=mysql_db;SERVER=mysql_server;option=512 ;uid=username;pwd=password'
Notice the option=512
MySQL compatibility
I have a Windows XP application that uses MSDE as its DB engine. If I
create an identical database in MySQL and include the correct ODBC
"driver", is it be possible to replace MSDE with MySQL?
What does it take for them to be compatible? After all both engines
process SQL commands.
Thanks for any input.
- Alex
"claw" <claw@.hotmail.com> wrote in message
news:2005032101053516807%claw@.hotmailcom...
>I have a Windows XP application that uses MSDE as its DB engine. If I
>create an identical database in MySQL and include the correct ODBC
>"driver", is it be possible to replace MSDE with MySQL?
> What does it take for them to be compatible? After all both engines
> process SQL commands.
> Thanks for any input.
> - Alex
Here's a quote from Google:
<quote>
You will need to use MyOLEDB, MyODBC or the MySQL .NET drivers. All links
given below:
MyOLEDB http://www.mysql.com/portal/siXtes/item-142.html
MyODBC http://www.mysql.com/downloadsX/api-myodbc-3.51.html
MySQL .NET drivers http://sourceforge.net/projectXs/mysqlnet/
I have found that MyODBC gives the most consistent results with .NET,
but others may have had different experiences. I haven't tried the open
source MySQL .NET driver yet, but it looks very promising (and hopefully
speedier than MySQL ODBC).
</quote>
You should also crosscheck data type compatibility.
Peter [MVP Visual Developer]
Jack of all trades, master of none.
|||On Mon, 21 Mar 2005 00:05:35 GMT, claw wrote:
>I have a Windows XP application that uses MSDE as its DB engine. If I
>create an identical database in MySQL and include the correct ODBC
>"driver", is it be possible to replace MSDE with MySQL?
>What does it take for them to be compatible? After all both engines
>process SQL commands.
Hi Alex,
In addition to Peter's reply, here are some other things to consider.
SQL is a highly standardized language. The ANSI standard is based on
SQL-92; the later standards SQL-99 and SQL-2003 (IIRC) are not (yet?)
adopted by ANSI. However, it is entirely up to the manufacturers to
decide to what extend they want to adhere to the standards.
MSDE is quite close to SQL-92 - most, but not all features of SQL-92 are
available. In addition, MSDE also offers a wagonload of proprietary
extra features. While these features can make programs easier to write
and maintain and faster to executed, they will also limit portability.
If the program you are using uses many of these prorietary features,
then it is quite unlikely that it will run without modification on any
other database.
I'm not sure about MySQL, since I have no experience with it. But I've
read lots of comments indicating that MySQL is not very close to the
standards. I've never attempted to verify these comments, though. But if
they're true, then switching from MSDE to MySQL might prove to be very
hard.
Another issue is that some parts of SQL are not very standardised yet.
Procedural code, for instance, like triggers or stored procedures. Or
the declaration of supporting indexes - the options available are often
tied closely to the architecture of the database; some options available
for indexes on MSDE make sense only in the context of the mechanics of
how tables and indexes are stored in MSDE.
If you have no access to the source of the application and you can't
change the exact queries submitted, then I don't think you'll succeed.
SQL being a standardized and portable language does not imply that you
can just plug any database into an application and expect it to run.
What it does mean, is that *IF* the application is written with
portability in mind, it can be adapted to a new database with only
minimal changes.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||It takes quite a lot. MySQL has no stored procedures, and only the last
version has foreign keys. Then there is the following:
http://sql-info.de/mysql/gotchas.html
1.13 is a special favourite of mine...
Jacco Schalkwijk
SQL Server MVP
"claw" <claw@.hotmail.com> wrote in message
news:2005032101053516807%claw@.hotmailcom...
>I have a Windows XP application that uses MSDE as its DB engine. If I
>create an identical database in MySQL and include the correct ODBC
>"driver", is it be possible to replace MSDE with MySQL?
> What does it take for them to be compatible? After all both engines
> process SQL commands.
> Thanks for any input.
> - Alex
create an identical database in MySQL and include the correct ODBC
"driver", is it be possible to replace MSDE with MySQL?
What does it take for them to be compatible? After all both engines
process SQL commands.
Thanks for any input.
- Alex
"claw" <claw@.hotmail.com> wrote in message
news:2005032101053516807%claw@.hotmailcom...
>I have a Windows XP application that uses MSDE as its DB engine. If I
>create an identical database in MySQL and include the correct ODBC
>"driver", is it be possible to replace MSDE with MySQL?
> What does it take for them to be compatible? After all both engines
> process SQL commands.
> Thanks for any input.
> - Alex
Here's a quote from Google:
<quote>
You will need to use MyOLEDB, MyODBC or the MySQL .NET drivers. All links
given below:
MyOLEDB http://www.mysql.com/portal/siXtes/item-142.html
MyODBC http://www.mysql.com/downloadsX/api-myodbc-3.51.html
MySQL .NET drivers http://sourceforge.net/projectXs/mysqlnet/
I have found that MyODBC gives the most consistent results with .NET,
but others may have had different experiences. I haven't tried the open
source MySQL .NET driver yet, but it looks very promising (and hopefully
speedier than MySQL ODBC).
</quote>
You should also crosscheck data type compatibility.
Peter [MVP Visual Developer]
Jack of all trades, master of none.
|||On Mon, 21 Mar 2005 00:05:35 GMT, claw wrote:
>I have a Windows XP application that uses MSDE as its DB engine. If I
>create an identical database in MySQL and include the correct ODBC
>"driver", is it be possible to replace MSDE with MySQL?
>What does it take for them to be compatible? After all both engines
>process SQL commands.
Hi Alex,
In addition to Peter's reply, here are some other things to consider.
SQL is a highly standardized language. The ANSI standard is based on
SQL-92; the later standards SQL-99 and SQL-2003 (IIRC) are not (yet?)
adopted by ANSI. However, it is entirely up to the manufacturers to
decide to what extend they want to adhere to the standards.
MSDE is quite close to SQL-92 - most, but not all features of SQL-92 are
available. In addition, MSDE also offers a wagonload of proprietary
extra features. While these features can make programs easier to write
and maintain and faster to executed, they will also limit portability.
If the program you are using uses many of these prorietary features,
then it is quite unlikely that it will run without modification on any
other database.
I'm not sure about MySQL, since I have no experience with it. But I've
read lots of comments indicating that MySQL is not very close to the
standards. I've never attempted to verify these comments, though. But if
they're true, then switching from MSDE to MySQL might prove to be very
hard.
Another issue is that some parts of SQL are not very standardised yet.
Procedural code, for instance, like triggers or stored procedures. Or
the declaration of supporting indexes - the options available are often
tied closely to the architecture of the database; some options available
for indexes on MSDE make sense only in the context of the mechanics of
how tables and indexes are stored in MSDE.
If you have no access to the source of the application and you can't
change the exact queries submitted, then I don't think you'll succeed.
SQL being a standardized and portable language does not imply that you
can just plug any database into an application and expect it to run.
What it does mean, is that *IF* the application is written with
portability in mind, it can be adapted to a new database with only
minimal changes.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||It takes quite a lot. MySQL has no stored procedures, and only the last
version has foreign keys. Then there is the following:
http://sql-info.de/mysql/gotchas.html
1.13 is a special favourite of mine...
Jacco Schalkwijk
SQL Server MVP
"claw" <claw@.hotmail.com> wrote in message
news:2005032101053516807%claw@.hotmailcom...
>I have a Windows XP application that uses MSDE as its DB engine. If I
>create an identical database in MySQL and include the correct ODBC
>"driver", is it be possible to replace MSDE with MySQL?
> What does it take for them to be compatible? After all both engines
> process SQL commands.
> Thanks for any input.
> - Alex
MySql 64 bit driver and SSIS
If anyone have been able to install the MySql ODBC driver on XP 64 bit and get it to work with SSIS, PLEASE tell me how you accomplished it.
Duplicate post (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2055272&SiteID=1)
Some related posts that might help :
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=165801&SiteID=1
MySql 64 bit driver and SSIS
If anyone have been able to install the MySql ODBC driver on XP 64 bit and get it to work with SSIS, PLEASE tell me how you accomplished it.
Duplicate post (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2055272&SiteID=1)
Some related posts that might help :
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=165801&SiteID=1
MySQL 5.0 Views wont work with crystal reports
I can access my view data through the application, but when i try to create the report in crytal reports and set up the database through an odbc driver 3.51.
If i click on a normal table its fine, but with the views it says
"Error Opening File: There are no fields in the file: "[View name]".Hi,
I've got a similar problem but using a stored proc. (See earlier posting for more info)
After much hair-pulling and soul searching i think that their might be a compatibility problem with MySQL5, MyODBC 3.51 and Crystal.
Have you tried MyODBC 5.0 yet? If it installs and works on yr side that might take yr problem away. And if it does, please let us know what you did cause it dont wanna install here.
Thanks and good luck|||Thanks
I have tried the 5.0 ODBC Connector, but unfortunatly i had no joy. Still the same error.
If i click on a normal table its fine, but with the views it says
"Error Opening File: There are no fields in the file: "[View name]".Hi,
I've got a similar problem but using a stored proc. (See earlier posting for more info)
After much hair-pulling and soul searching i think that their might be a compatibility problem with MySQL5, MyODBC 3.51 and Crystal.
Have you tried MyODBC 5.0 yet? If it installs and works on yr side that might take yr problem away. And if it does, please let us know what you did cause it dont wanna install here.
Thanks and good luck|||Thanks
I have tried the 5.0 ODBC Connector, but unfortunatly i had no joy. Still the same error.
MySQL
Hello,
When I try to connect to my MySQL server (on my webserver) via my ODBC
connector, I receive a "general network error". Does anyone know what this
is or what is causing this so I can get around it?
Thanks,
Evan M.
evan AT radiologyonesource DOT comEvan,
This is a Microsoft SQL Server group, you probably won't get a reply to
your MySQL question here. Try http://dev.mysql.com/support/
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Evan McCutchen wrote:
> Hello,
> When I try to connect to my MySQL server (on my webserver) via my ODBC
> connector, I receive a "general network error". Does anyone know what this
> is or what is causing this so I can get around it?
> Thanks,
> Evan M.
> evan AT radiologyonesource DOT com
>|||Mark,
Thanks for the direction! It helped alot!! :)
Evan McCutchen
Evan AT radiologyonesource. DOT com
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:u6FYV57UEHA.2320@.TK2MSFTNGP10.phx.gbl...
> Evan,
> This is a Microsoft SQL Server group, you probably won't get a reply to
> your MySQL question here. Try http://dev.mysql.com/support/
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Evan McCutchen wrote:
> > Hello,
> >
> > When I try to connect to my MySQL server (on my webserver) via my ODBC
> > connector, I receive a "general network error". Does anyone know what
this
> > is or what is causing this so I can get around it?
> >
> > Thanks,
> > Evan M.
> > evan AT radiologyonesource DOT com
> >
> >
When I try to connect to my MySQL server (on my webserver) via my ODBC
connector, I receive a "general network error". Does anyone know what this
is or what is causing this so I can get around it?
Thanks,
Evan M.
evan AT radiologyonesource DOT comEvan,
This is a Microsoft SQL Server group, you probably won't get a reply to
your MySQL question here. Try http://dev.mysql.com/support/
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Evan McCutchen wrote:
> Hello,
> When I try to connect to my MySQL server (on my webserver) via my ODBC
> connector, I receive a "general network error". Does anyone know what this
> is or what is causing this so I can get around it?
> Thanks,
> Evan M.
> evan AT radiologyonesource DOT com
>|||Mark,
Thanks for the direction! It helped alot!! :)
Evan McCutchen
Evan AT radiologyonesource. DOT com
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:u6FYV57UEHA.2320@.TK2MSFTNGP10.phx.gbl...
> Evan,
> This is a Microsoft SQL Server group, you probably won't get a reply to
> your MySQL question here. Try http://dev.mysql.com/support/
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Evan McCutchen wrote:
> > Hello,
> >
> > When I try to connect to my MySQL server (on my webserver) via my ODBC
> > connector, I receive a "general network error". Does anyone know what
this
> > is or what is causing this so I can get around it?
> >
> > Thanks,
> > Evan M.
> > evan AT radiologyonesource DOT com
> >
> >
MYODBC Drivers for sql server 2005
SO I installed the MyOdbc drivers 5.0 and 3.51 and then went into my Data Sources(ODBC) drivers in my Administrative Control Panel
I then proceeded to add the DSN Under System DSN and I also tried User DSN
When I try to use the import/export tool in my SQL Server 2005 Management studio I don't get presented with the MySql drivers at all for a source
why is this?
Trust me you don't need MySQL ODBC driver in SQL Server to move MySQL data to SQL Server, so tell me what you are trying to do and I will tell you how to do it. Hope this helps.|||
oh well that's pretty much it
The sites php with a mysql DB
I'm making it .NET with an MS SQL DB
So just copying the table data and structure to MS SQL
|||You can use OLE-DB driver to import MySQL data and table structure if it is not in the import/export wizard look for it in DTS/SSIS, another option is to use OPENROWSET or OPENQUERY in SQL Server to connect to MySQL run a search for all of the above in SQL Server BOL(books online). Hope this helps.
Subscribe to:
Posts (Atom)