I have named SQL Server 200 instance installed.
I am trying to connect to connect this named instance using
java application which using JDBC driver ?
anybody knows how can I connect named instance using JDBC driver ?
thank you for timely help
jagdishYou have to use the port number for the named sql server instance:
e.g.
jdbc:microsoft:sqlserver://servername:portnumber;user=XXX;password=YYY
Showing posts with label driver. Show all posts
Showing posts with label driver. Show all posts
Friday, March 23, 2012
Wednesday, March 21, 2012
N' prefix required or not?
Need to provide international support for the product. Use
SqlServer 2000 for repository; DataDirect JDBC driver and
Java code for the application.
Using nvarchar datatypes for columns. Data entry/retrieval
will be through Java code. When send SQL commands through
Java/JDBC; do we need to prefix the constants with the N'
prefix example - INSERT INTO abc VALUES (N'xyz') or will
INSERT INTO abc VALUES ('xyz') store the data in unicode.
If the datatype supports unicode chars do we still need to
use the N'prefix? Also assuming data is stored in unicode;
when using in where clause while selecting will we have to
use SELECT * from abc where f1 =N'xyx' for it to be
retrieved? FYI, All database access is through Java/JDBC
which both claim to provide full international/unicode
support.
Thanks,If you are sending in hard-coded strings, then you will need to prefix them
with N to indicate that the string is Unicode. Otherwise, unicode strings
will be stored as a series of junk characters in SQL Server.
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"AB" <anonymous@.discussions.microsoft.com> wrote in message
news:900901c3e9f5$a1fc1f20$a501280a@.phx.gbl...
> Need to provide international support for the product. Use
> SqlServer 2000 for repository; DataDirect JDBC driver and
> Java code for the application.
> Using nvarchar datatypes for columns. Data entry/retrieval
> will be through Java code. When send SQL commands through
> Java/JDBC; do we need to prefix the constants with the N'
> prefix example - INSERT INTO abc VALUES (N'xyz') or will
> INSERT INTO abc VALUES ('xyz') store the data in unicode.
> If the datatype supports unicode chars do we still need to
> use the N'prefix? Also assuming data is stored in unicode;
> when using in where clause while selecting will we have to
> use SELECT * from abc where f1 =N'xyx' for it to be
> retrieved? FYI, All database access is through Java/JDBC
> which both claim to provide full international/unicode
> support.
> Thanks,
SqlServer 2000 for repository; DataDirect JDBC driver and
Java code for the application.
Using nvarchar datatypes for columns. Data entry/retrieval
will be through Java code. When send SQL commands through
Java/JDBC; do we need to prefix the constants with the N'
prefix example - INSERT INTO abc VALUES (N'xyz') or will
INSERT INTO abc VALUES ('xyz') store the data in unicode.
If the datatype supports unicode chars do we still need to
use the N'prefix? Also assuming data is stored in unicode;
when using in where clause while selecting will we have to
use SELECT * from abc where f1 =N'xyx' for it to be
retrieved? FYI, All database access is through Java/JDBC
which both claim to provide full international/unicode
support.
Thanks,If you are sending in hard-coded strings, then you will need to prefix them
with N to indicate that the string is Unicode. Otherwise, unicode strings
will be stored as a series of junk characters in SQL Server.
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"AB" <anonymous@.discussions.microsoft.com> wrote in message
news:900901c3e9f5$a1fc1f20$a501280a@.phx.gbl...
> Need to provide international support for the product. Use
> SqlServer 2000 for repository; DataDirect JDBC driver and
> Java code for the application.
> Using nvarchar datatypes for columns. Data entry/retrieval
> will be through Java code. When send SQL commands through
> Java/JDBC; do we need to prefix the constants with the N'
> prefix example - INSERT INTO abc VALUES (N'xyz') or will
> INSERT INTO abc VALUES ('xyz') store the data in unicode.
> If the datatype supports unicode chars do we still need to
> use the N'prefix? Also assuming data is stored in unicode;
> when using in where clause while selecting will we have to
> use SELECT * from abc where f1 =N'xyx' for it to be
> retrieved? FYI, All database access is through Java/JDBC
> which both claim to provide full international/unicode
> support.
> Thanks,
N' prefix required or not?
Need to provide international support for the product. Use
SqlServer 2000 for repository; DataDirect JDBC driver and
Java code for the application.
Using nvarchar datatypes for columns. Data entry/retrieval
will be through Java code. When send SQL commands through
Java/JDBC; do we need to prefix the constants with the N'
prefix example - INSERT INTO abc VALUES (N'xyz') or will
INSERT INTO abc VALUES ('xyz') store the data in unicode.
If the datatype supports unicode chars do we still need to
use the N'prefix? Also assuming data is stored in unicode;
when using in where clause while selecting will we have to
use SELECT * from abc where f1 =N'xyx' for it to be
retrieved? FYI, All database access is through Java/JDBC
which both claim to provide full international/unicode
support.
Thanks,If you are sending in hard-coded strings, then you will need to prefix them
with N to indicate that the string is Unicode. Otherwise, unicode strings
will be stored as a series of junk characters in SQL Server.
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"AB" <anonymous@.discussions.microsoft.com> wrote in message
news:900901c3e9f5$a1fc1f20$a501280a@.phx.gbl...
SqlServer 2000 for repository; DataDirect JDBC driver and
Java code for the application.
Using nvarchar datatypes for columns. Data entry/retrieval
will be through Java code. When send SQL commands through
Java/JDBC; do we need to prefix the constants with the N'
prefix example - INSERT INTO abc VALUES (N'xyz') or will
INSERT INTO abc VALUES ('xyz') store the data in unicode.
If the datatype supports unicode chars do we still need to
use the N'prefix? Also assuming data is stored in unicode;
when using in where clause while selecting will we have to
use SELECT * from abc where f1 =N'xyx' for it to be
retrieved? FYI, All database access is through Java/JDBC
which both claim to provide full international/unicode
support.
Thanks,If you are sending in hard-coded strings, then you will need to prefix them
with N to indicate that the string is Unicode. Otherwise, unicode strings
will be stored as a series of junk characters in SQL Server.
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"AB" <anonymous@.discussions.microsoft.com> wrote in message
news:900901c3e9f5$a1fc1f20$a501280a@.phx.gbl...
quote:sql
> Need to provide international support for the product. Use
> SqlServer 2000 for repository; DataDirect JDBC driver and
> Java code for the application.
> Using nvarchar datatypes for columns. Data entry/retrieval
> will be through Java code. When send SQL commands through
> Java/JDBC; do we need to prefix the constants with the N'
> prefix example - INSERT INTO abc VALUES (N'xyz') or will
> INSERT INTO abc VALUES ('xyz') store the data in unicode.
> If the datatype supports unicode chars do we still need to
> use the N'prefix? Also assuming data is stored in unicode;
> when using in where clause while selecting will we have to
> use SELECT * from abc where f1 =N'xyx' for it to be
> retrieved? FYI, All database access is through Java/JDBC
> which both claim to provide full international/unicode
> support.
> Thanks,
Monday, March 12, 2012
MySQL OLEDB Driver
Hi!
I have a small question, there are OLEDB drivers availible for .NET on the MYSQL download site. But when I install them I'm not able to see them inside SQLIS, I've tried them inside Visual Studio and they work fine.
Is there a way to get them "registred" or add them as a reference inside SQLIS so that I may choose them when setting up an OLEDB Source / Destination?For performance reasons, the Integration Services Service caches (as DTS used to do) the list of available components and, among other things, OLE DB Providers, so that the designer doesn't need to waste time gathering those lists from the registry and the file system. I'm just speculating here, but I'm guessing that you might need to do something to refresh that cached list, such as stop and re-start the Service (or reboot). A little-known dialog box in DTS times has a "Refresh Cache" button, but I haven't seen an equivalent button in SSIS.
-Doug
|||Don't think that's the problem, I think the problem is that the driver doesn't get registered in the windows registery. Is there a way to add some keys to the windows registery to manually register the .dll files as OLEDB drivers?|||Hi, have you figured out that one?|||You say OLEDB drivers for .NET but that doesn't make sense to me. OLEDB is not a .NET provider instead it would be ADO.NET. Are the drivers OLEDB or are they .NET. If they are .NET then they wouldn't be available from our OLEDB source but from our DataReaderSource, which uses .NET connections. If they are indeed OLEDB then if they are not showing up then they are not registering themselves correctly. You could try regsvr32 to reregister them but you might have to contact MySQL support and ask them for help.
Thanks,
Matt
MySQL OLEDB Driver
Hi!
I have a small question, there are OLEDB drivers availible for .NET on the MYSQL download site. But when I install them I'm not able to see them inside SQLIS, I've tried them inside Visual Studio and they work fine.
Is there a way to get them "registred" or add them as a reference inside SQLIS so that I may choose them when setting up an OLEDB Source / Destination?For performance reasons, the Integration Services Service caches (as DTS used to do) the list of available components and, among other things, OLE DB Providers, so that the designer doesn't need to waste time gathering those lists from the registry and the file system. I'm just speculating here, but I'm guessing that you might need to do something to refresh that cached list, such as stop and re-start the Service (or reboot). A little-known dialog box in DTS times has a "Refresh Cache" button, but I haven't seen an equivalent button in SSIS.
-Doug
|||Don't think that's the problem, I think the problem is that the driver doesn't get registered in the windows registery. Is there a way to add some keys to the windows registery to manually register the .dll files as OLEDB drivers?|||Hi, have you figured out that one?|||You say OLEDB drivers for .NET but that doesn't make sense to me. OLEDB is not a .NET provider instead it would be ADO.NET. Are the drivers OLEDB or are they .NET. If they are .NET then they wouldn't be available from our OLEDB source but from our DataReaderSource, which uses .NET connections. If they are indeed OLEDB then if they are not showing up then they are not registering themselves correctly. You could try regsvr32 to reregister them but you might have to contact MySQL support and ask them for help.
Thanks,
Matt
MySQL Linked Server
I am trying to linka mysql database to SQL 2005, but I am not sure what I
need to do.
I have set up a DSN using the mysql driver. I get lost when I try and create
the linked server in SQL 2005. Can someone please outline the steps to creat
e
the linked server. Should the mysql driver show up as a provider in SQL 2005
?Select the Microsoft OLE DB Provider for ODBC Drivers. Form
there, enter the DSN name for the Data source.
-Sue
On Thu, 16 Mar 2006 17:07:27 -0800, Curtis
<Curtis@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I am trying to linka mysql database to SQL 2005, but I am not sure what I
>need to do.
>I have set up a DSN using the mysql driver. I get lost when I try and creat
e
>the linked server in SQL 2005. Can someone please outline the steps to crea
te
>the linked server. Should the mysql driver show up as a provider in SQL 2005?[/vbco
l]
need to do.
I have set up a DSN using the mysql driver. I get lost when I try and create
the linked server in SQL 2005. Can someone please outline the steps to creat
e
the linked server. Should the mysql driver show up as a provider in SQL 2005
?Select the Microsoft OLE DB Provider for ODBC Drivers. Form
there, enter the DSN name for the Data source.
-Sue
On Thu, 16 Mar 2006 17:07:27 -0800, Curtis
<Curtis@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I am trying to linka mysql database to SQL 2005, but I am not sure what I
>need to do.
>I have set up a DSN using the mysql driver. I get lost when I try and creat
e
>the linked server in SQL 2005. Can someone please outline the steps to crea
te
>the linked server. Should the mysql driver show up as a provider in SQL 2005?[/vbco
l]
MySQL Linked Server
I am trying to linka MySQL database to SQL 2005, but I am not sure what I
need to do.
I have set up a DSN using the MySQL driver. I get lost when I try and create
the linked server in SQL 2005. Can someone please outline the steps to create
the linked server. Should the MySQL driver show up as a provider in SQL 2005?
Select the Microsoft OLE DB Provider for ODBC Drivers. Form
there, enter the DSN name for the Data source.
-Sue
On Thu, 16 Mar 2006 17:07:27 -0800, Curtis
<Curtis@.discussions.microsoft.com> wrote:
>I am trying to linka MySQL database to SQL 2005, but I am not sure what I
>need to do.
>I have set up a DSN using the MySQL driver. I get lost when I try and create
>the linked server in SQL 2005. Can someone please outline the steps to create
>the linked server. Should the MySQL driver show up as a provider in SQL 2005?
need to do.
I have set up a DSN using the MySQL driver. I get lost when I try and create
the linked server in SQL 2005. Can someone please outline the steps to create
the linked server. Should the MySQL driver show up as a provider in SQL 2005?
Select the Microsoft OLE DB Provider for ODBC Drivers. Form
there, enter the DSN name for the Data source.
-Sue
On Thu, 16 Mar 2006 17:07:27 -0800, Curtis
<Curtis@.discussions.microsoft.com> wrote:
>I am trying to linka MySQL database to SQL 2005, but I am not sure what I
>need to do.
>I have set up a DSN using the MySQL driver. I get lost when I try and create
>the linked server in SQL 2005. Can someone please outline the steps to create
>the linked server. Should the MySQL driver show up as a provider in SQL 2005?
Friday, March 9, 2012
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
Subscribe to:
Posts (Atom)