question

mbarfiel avatar image
mbarfiel asked Spirent_Admin edited

SQL Server 2005 Database Client Support

Currently, I'm using iTest 4.0.2 and I'm trying to connect to a SQL Server 2005 DB. I haven't been able to get the built in SQL Server option to work. I looked at the message board and this feature works with SQL Server 2003.

 

Has anyone tried using the iTest DB client against SQL Server 2005? Do I need to configure the JDBC option to connect to a 2005 server or should the built-in options work?

 

I may need to play around with this a little more. On a positive note, the DB Client works great with MySQL.

 

Thanks.

iTestsession profile
10 |950
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

·
PaulD avatar image
PaulD answered PaulD posted

I'm pretty sure that this has been tested against SQL Server 2005.  We integrate the 2.0 JDBC driver from Microsoft, which indicates that it supports 2000, 2005 and 2008.  There is a new 3.0 driver but I don't think it should be needed.

 

If you select SQL Server, we set up the JDBC connection string to:

 

jdbc:sqlserver://<server>:<port>;database=<dbname>

 

where port defaults to 1433.

 

That should all be appropriate for connecting to SQL Server 2005.  If I had to guess, perhaps your SQL Server has a firewall turned on, or some other setup issue.  Have you tried using other tools (like the Microsoft tools) to access the database  from the same machine where iTest is running?

4 comments
10 |950
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

mbarfiel avatar image mbarfiel commented ·

I'm able to query the database with SQL Query Analyzer so I know I can connect to the DB remotely. However, I'm missing something with iTest because I keep getting an error.

 

I'm going to attach some screen shots. You may see something obvious with the connection parameters that I'm missing.

 

I appreciate the help with this is.

 

 

0 Likes 0 ·
SQL_Server_Error_Message.jpg (17.2 KiB)
SQL_Server_Session_Information.jpg (36.8 KiB)
PaulD avatar image PaulD mbarfiel commented ·

The entry in the address field, "PQ_Generate_Data/PQ_CN_GENERAL", looks strange to me.  This doesn't look like a hostname -- because of the / in the middle of it.  Can you explain what I'm looking at there?  

 

It sounds like you've already tried using just a dotted IP address, so this might not be it, but I'm curious.

0 Likes 0 ·
mbarfiel avatar image mbarfiel PaulD commented ·

I'm connecting to SQL Server Cluster. The full path to the server is CORP-SQL1\PQ_CN_GENERAL. iTest may be having an issue with extended server path. I'm attaching some screenshots of the ODBC connection to the server. This may provide some useful information.

 

 

0 Likes 0 ·
DataSource_Information.JPG (61.7 KiB)
ODBC_Configuration_SQL_2005.JPG (43.9 KiB)
PaulD avatar image PaulD mbarfiel commented ·

I suspect that the problem is related to clustering.  I found several articles on the internet about JDBC with SQL Server Clustering.  Here's one:

 

http://msdn.microsoft.com/en-us/library/aa342332.aspx

 

One thing you might consider is using "custom" and then you'll be free to specify your own connection string.  You should use:

 

com.microsoft.sqlserver.jdbc.SQLServerDriver

 

as the driver class for using SQL Server.

 

 

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.