Release Notes
IBM Database Add-Ins for Visual Studio 2005
Release Notes: Fix Pack 2
© Copyright International Business Machines Corporation 2006.
All rights reserved.
The IBM® Database Add-Ins for Visual Studio 2005 -
Fix Pack 2 includes support for DB2® Version 9.1
for z/OS, two new function designers, and support for application debugging.
IBM Database Add-Ins for Visual Studio 2005 - Fix Pack 2 supports the
IBM DB2 Data Provider for .NET Framework 2.0.
Prerequisites
Prerequisites for the IBM Database Add-Ins for Visual Studio 2005 - Fix Pack 2
include:
- Microsoft® Visual Studio 2005®
- IBM DB2 Data Provider for .NET Framework 2.0
- Windows XP, Service Pack 2, or later; or Windows Server 2003,
Service Pack 1
Key new features in IBM Database Add-Ins for Visual Studio 2005 -
Fix Pack 2
The new features in the IBM Database Add-Ins for Visual Studio 2005 - Fix
Pack 2 enable
developers to reduce development time and develop .NET applications for the
entire DB2 server family using Microsoft® Visual Studio as
their integrated development environment. The following list summarizes
the new features:
- Support for DB2 Version 9.1 for z/OS, including:
- Native SQL procedural language
- Binary deploy
- Package variation for SQL procedures
- New data types (DECFLOAT and VARBINARY)
- XML support: XML indexes for tables, sample XML generation,
annotated XML schemas, XML Schema Repository
- End-to-end debugging of Windows applications in C# and
Visual Basic that use DB2 servers, including SQL procedures that are
called from the applications
- The IBM Web Service Function Designer, in which you can develop DB2
functions that access the operations of Web services
- The IBM OLE DB Table Function Designer, in which you can develop OLE
DB table functions that create DB2 tables and views of the table
functions
The IBM Database Add-Ins for Visual Studio 2005 support the following DB2
database servers:
- DB2 Universal Database for Linux, UNIX, and Windows, Versions 8.1,
8.2, 9.1, and 9.1 Fix Pack 2
- DB2 Universal Database for z/OS or OS/390, Versions 6 and 7
- DB2 Universal Database for z/OS, Versions 8 and 9.1
- DB2 Universal Database for iSeries, Versions 5.1, 5.2, and 5.3
Issues and limitations
The IBM Database Add-Ins for Visual Studio 2005 - Fix Pack 2
includes issues and limitations in the following categories:
General
Accessibility
All designers
Triggers
IBM Procedure Designer
SQL procedure runs
CLR procedures
IBM XSR Designer
DB2 XML Designer
IBM XML Schema Mapping Designer
IBM Web Service Function Designer
Windows application development
Web application development
DB2 database projects
DB2 V9 for z/OS
Visual Studio Query Builder
Visual Studio 2003 to Visual Studio
2005 migration
- Data connection error
- Issue: If you install Visual Studio 2005 after installing DB2
Version 9.1 for Linux, UNIX, and Windows, the IBM DB2 Data Provider
for .NET Framework 2.0 is not registered in the Global Assembly Cache.
Errors occur in the Add Connection window when you try to add a data
connection with an IBM DB2 Data Provider for .NET Framework 2.0 data
source.
- Workaround: Run a command to register the IBM DB2 Data
Provider for .NET Framework 2.0 in the Global Assembly Cache.
- Open the DB2 Command Window. Click Start
> Programs > IBM DB2
> Command Line Tools > Command
Window.
- At the prompt in the DB2 Command Window, enter the following
command:
db2lswtch.exe -promote
If you have multiple copies of DB2 installed, run this
command from the default DB2 copy only.
- Connection performance on iSeries and zSeries servers
- Issue: The current timeout duration for data
connections to all database server types is 30 seconds.
This setting is too low for iSeries and zSeries servers.
- Workaround: To improve performance when connecting to
an iSeries or zSeries server, increase the timeout duration
to 300 seconds or more.
- On the Tools menu, select
Options.
- In the list in the Options window, click IBM
DB2 Tools.
- In the Database Access category on the
right, increase the value of the Timeout
option.
- Missing data connection information
- Issue: If you do not save your password when you
create a data connection, the connection information
might be missing when you modify a data connection in
another session of Visual Studio 2005.
- In the Server Explorer, right-click the Data
Connections node, and then select
Add Connection on the shortcut menu.
- In the Add Connections window, specify the connection
information, but do not select the Save my
password check box.
- After you quit and restart Visual Studio, with the data
connection collapsed in the Server Explorer, right-click
the data connection, and then select Modify
Connection on the shortcut menu.
In the Modify Connection window, the information that you
specified when you added the data connection might be missing.
- Workaround: Expand the data connection in the Server
Explorer before you open the Modify Connection window.
- Nonworking access keys
- Issue: The access keys for the following controls are
not functional.
Select XML Schema Source window:
Owner
XML schema name
Select source for XML pattern window:
Owner
XML schema name
- Workaround: Use the Tab and arrow keys to navigate through
the controls in the windows.
- Missing access keys in DB2 XML Designer
- Issue: The following controls in the DB2 XML Designer do
not have access keys:
Text View tab
Grid View tab
Sample XML tab
Advanced Options section
- Workaround: Use the Tab and arrow keys to navigate through
the controls in the window.
- Shortcut keys in the IBM XML Schema Mapping Designer
- Issue: The shortcut keys for the IBM XML Schema Mapping
Designer are not described in Help.
- Workaround: Use the following shortcut keys in the Mapping
Editor section of the Annotated XML Schema view of the designer:
Keyboard command |
What it does |
Ctrl+T |
Moves the focus to the root-level
node in the Source XML schema pane. Use the arrow
keys to navigate through the nodes in the XML schema. |
Ctrl+G |
- If the focus is in the Source XML schema
pane, moves the focus to and selects the first target table
in the mapping editor.
- If the focus is in the mapping editor, moves the focus to
and selects the next target table in the mapping editor.
|
Ctrl+J |
- If a table is selected in the mapping editor, selects the first
map link for the table.
- If a map link is selected in the mapping editor, selects the
next map link for the same table.
|
To add a map link by using the keyboard:
- If the focus is on a table, press Ctrl+T to move the focus
to the root-level node in the Source XML schema
pane.
- Use the arrow keys to move the focus to the node in the XML
schema that is the source node for the new map link.
- Press the Menu key to display the shortcut menu,
press the down arrow key to select the Add Map
Link command, and then press Enter.
- Press Ctrl+G to move the focus to the first table in the
mapping editor, and then press Ctrl+G repeatedly to move
the focus to the table that contains the target column.
- Display the shortcut menu, select Add Map Link,
and press the right arrow key to display the submenu.
Press the down arrow key repeatedly until the target column
is selected in the list, and then press Enter.
If you cannot see a full column name, press the left arrow
key to scroll the list item text to the right.
To specify a value for the Content Handling or
Normalization property of a map link by using
the keyboard:
- Select the map link in the Mapping Editor
section of the Annotated XML Schema view of the designer.
- Press the Tab key to move to the Properties
section of the view.
- Press the down arrow key repeatedly to navigate to the
Content Handling or Normalization
property.
- Press the Tab key to move to the value cell of the property.
- Press Alt+down arrow to display the list in the cell, press the
down arrow key to move to the property value that you want to select,
and then press Enter.
- Case-sensitive identifiers
- Issue: SQL identifiers containing special characters and
case-sensitive characters that must be enclosed in single quotes
are not supported.
- Workaround: Specify identifiers that do not contain special
characters and that are not case-sensitive.
- Multiple prompts for save on close
- Issue: When you add a database object or SQL
procedure in a designer and do not save the item
before you close the designer, if you respond Yes
to the save-on-close prompt, you are asked to confirm the
save in a second message box.
This issue occurs only once in each session of Visual Studio:
for the first database object that you do not save until you
close the designer.
- Workaround: There is no workaround; this issue is a
current limitation.
- Deleting tables and triggers (Linux, UNIX, and Windows
servers only)
- Issue: If you delete a table, the triggers that are associated
with the table are not deleted.
Even though you delete a table, you might want to use the
triggers that are associated with the table in SQL procedures.
You can see the triggers that are associated with deleted tables
in the DB2 Control Center (Tools > IBM DB2 Tools >
DB2 Control Center).
- Workaround: If you want to delete triggers that are
associated with a table that you are deleting, delete the triggers
before you delete the table.
- In the Server Explorer under your data connection,
right-click the table that you want to delete, and
then select Open Definition on the
shortcut menu.
- With the table definition open in the IBM Table Designer,
click Triggers on the IBM Table Designer
toolbar.
- In the Triggers view, for each trigger that you want to
delete, select the trigger in the Triggers
list, and then click Delete Trigger.
- Save the table and then close the IBM Table Designer.
- Trigger row variable properties
- Issue: If you define a new row variable property for
a trigger in the Triggers view of the IBM Table Designer, the
value that you specify for the row variable is not persistent
from instance to instance of the designer.
- Workaround: There is no workaround; this issue is a
current limitation.
- Setting debug mode to ALLOW
- Issue: This issue applies only if your database is on
a DB2 UDB server for Linux, UNIX and Windows, Version 8.
On the Procedure page, if you set the Debug mode option
to ALLOW while you are creating or modifying the definition of an SQL
procedure, the next time that you open the SQL procedure definition,
the value of the option reverts to DISALLOW.
- Workaround: Reset the Debug mode option to ALLOW any time that
you open and save a procedure definition.
- Missing parameters in overloaded procedures
- Issue: In an overloaded procedure with multiple procedure definitions,
some of the procedure parameters are not displayed in the tree under
one or more occurrences of the procedure in the Server Explorer.
This problem occurs on a DB2 for iSeries server, when each definition of
the overloaded procedure has a different specific name.
- Workaround: There is no workaround; this issue is a limitation.
- Duplicate scripts for overloaded procedures
- Issue: In an overloaded procedure with multiple procedure definitions,
the SQL code that is shown on the Show Script page for all the
definitions of the procedure is the same.
This problem occurs on a DB2 for iSeries server.
- Workaround: There is no workaround; this issue is a limitation.
- Refreshing result set columns
- Issue: If you refresh a column in a result set, an error occurs.
- In the Server Explorer under your data connection, expand the
Procedures folder.
- Expand a procedure node, expand its Result Sets node,
and then expand a result set.
- Right-click a column in the result set, and then select
Refresh on the shortcut menu.
The following error occurs:
Error occurred while getting objects for a resultset.
- Workarounds:
- Ignore the error when refreshing a column in the result
set.
- Refresh the result set instead of refreshing a column in
the result set.
- Cursor movement in debug sessions
- Issue: While you are debugging an SQL procedure, if
there is more than one variable declaration in the procedure,
in some cases you must click Step Into or
Step Over more than once to move to the next
line.
- Workaround: You must click the number of times that
are equal to the number of variable declarations on the line.
For example, you must click twice on the following line:
DECLARE v_dept, v_actdept
CHAR(3)
and click three times on this line:
DECLARE v_bonus, v_deptbonus,
v_newbonus DECIMAL(9,2)
- Running CLR procedures deployed from .NET Framework 2.0 in DB2 V8
servers
- Issue: When you build and deploy a CLR procedure from the Visual
Studio 2005 .NET Framework Version 2.0 to the DB2 Version 8
server and try to run it, the following error message is displayed in the
IBM Output Message Pane:
Loading assembly
'<full_path_to_project_configuration_dll_file>'
failed.
- Workaround: Perform the following steps on the DB2
Version 8 server:
- Install Microsoft
.NET Framework 2.0, if it is not already installed.
Click
this link
to go to the download page on the Microsoft Web site.
- In the Windows Explorer, navigate to the
\windows\assembly
directory.
For example, C:\WINDOWS\assembly
or C:\WINNT\assembly
.
- In the
\assembly
directory, locate the
IBM.Data.DB2 assembly and review the version
information for the assembly. If the 8.1.2.1
version of the assembly is not listed, perform the following
steps:
- Open a second instance of the Windows Explorer and browse
to
<install_dir>\SQLLIB\bin\netf11
,
where install_dir
is your DB2 Version 8 installation directory.
- In the
\netf11
directory,
drag the IBM.Data.DB2.dll file to the
\windows\assembly
directory in the first instance of Windows Explorer.
Note: You cannot copy the .dll file
and paste it in the \assembly directory.
- Start Visual Studio 2005, open the DB2 project that contains
a CLR assembly, and build the project.
- XML schema names that begin with tilde ( ~ )
- Issue: Cannot delete an XML schema from the XML Schema
Repository (XSR) if the XSR name begins with the tilde (~)
character and the XSR name is not enclosed in quotation marks.
When you use the IBM XSR Designer to register an XML schema,
you can accept the default XSR name or specify a new one.
If you specify an XSR name that begins with a tilde, you can
successfully register the XML schema. However, if you do not
enclose the XSR name in double quotation marks, you cannot
delete the registered XML schema from the XML Schema Repository.
An error condition occurs when you select the
Delete command on the shortcut menu of the
registered XML schema in the Server Explorer.
- Workaround: If you are registering an XML schema with an
XSR name that begins with the tilde (~) character, enclose the
XSR name in double quotation marks.
- Generate Sample command
- Issue: The Generate Sample command on
the shortcut menu of an XML schema in the Server Explorer is
not described in Help.
You can generate sample XML for an XML schema that is registered
in the XML Schema Repository. If you are developing a Windows or
Web application that processes data in a database table, sample
XML can provide information about the content of a column of XML
data in the table.
To generate sample XML for an XML schema:
- In the Server Explorer under your data connection,
right-click the XML schema in the XML Schema Repository,
and then select Generate Sample on the
shortcut menu.
The sample XML is generated and displayed in the XML
editor.
- Optional: Copy the sample XML and paste it in your
application.
- Command buttons not visible
- Issue: In some languages, the Open
File, OK, Cancel, and
Help command buttons might not be fully visible.
- In the Server Explorer under your data connection, right-click
a table that con tains one or more columns of XML data type and
that are populated with data, and then select Show
Data on the shortcut menu.
- In the Result Data section of the IBM Data
Designer, click a cell that contains XML data, and then select
XML Designer on the drop-down menu.
In the DB2 XML Designer, only the tops of the Open
File, OK, Cancel, and
Help buttons might be visible in some languages.
- Workaround: To see all of the Open
File, OK, Cancel, and
Help buttons, reduce the font size.
- Close the DB2 XML Designer.
- On the Tools menu, select Options.
- In the Options window, click IBM DB2 Tools in the
list, and then scroll down to the Font Size option.
- Change the font size to a smaller number; for example, 7.
- Command buttons not visible
- Issue: If you quit Visual Studio while the DB2 XML Designer
is open, when you start your next Visual Studio session, the DB2
XML Designer is open, and the Open File,
OK, Cancel, and Help
command buttons are not fully visible.
- Workaround: Close the DB2 XML Designer before quitting
Visual Studio.
- Deleted map links remain in XML schema source
- Issue: If you delete a map link or a target table that has
map links from the Annotated XML Schema view in the designer, the
map link or map links are not deleted from the XML schema source
document.
- In the Mapping Editor section of the Annotated
XML Schema view of the designer, add one or more target tables,
and then add one or more map links for each table.
- Right-click in the mapping editor, select View
Source on the shortcut menu, and then select
Using Text Editor on the submenu.
- Review the map links in the text editor, and then close the
text editor.
- Delete a map link or a table that has map links from the
mapping editor.
The map link or the table and its associated map links
are no longer displayed in the mapping editor.
- Close the IBM XML Schema Mapping Designer. Save and register
the annotated XML schema.
- In the Server Explorer, right-click the annotated XML schema,
and then select View on the shortcut menu.
- Right-click in the XML Designer, and then select View
Code on the shortcut menu.
- Review the map links, and note that the map link that you deleted,
or the map links that are associated with the table that you deleted,
are still in the XML source document.
- Workaround: If you want to delete a map link or a table that has
map links, close the IBM XML Schema Mapping Designer without saving the annotated
XML schema, and start over.
- Truncated column names
- Issue: When you use the keyboard to add a map link in
the designer, a column name and data type can be right-aligned
in the list on the Add Map Link submenu. The right-alignment
of the column name and data type make the column name appear to be
truncated on the left. This issue occurs on only some computers.
- Workaround: Use the left arrow key to scroll left and
move the column name text to the right.
- Pane header label is not localized
- Issue: The header label for the Source XML schema
pane in the Annotated XML Schema view of the designer is shown in
English for every language.
- Workaround: The localized string for the pane header label is
shown in a ToolTip. To display the ToolTip, pause the pointer in the
pane header area.
- Finding XML nodes, tables, and columns
- Issue: The process of finding XML nodes in the Annotated XML
Schema view of the designer and finding XML nodes, tables and columns
in the Discover Relationships window is not described in Help.
You can find an XML node in the Source XML
Schema pane of the designer or in the Source
list of the Discover Relationships window. You can also find a table
or a column in the Target list of the Discover Relationships
window.
To find an XML node:
- Right-click any node in the Source XML Schema
pane of the Annotated XML Schema view, or right-click any node
in the Source list of the Discover
Relationships window, and then click Find on
the shortcut menu.
- In the Find window, specify the name of the XML node that you
want to find, and then click Find Next.
To find a table or a column:
- In the Discover Relationships window, right-click any table or
column in the Target list, and then click
Find on the shortcut menu.
- In the Find window, specify the name of the table or column
that you want to find, and then click Find Next.
- Complex types
- Issue: Complex types are not supported in the IBM Web Service
Function Designer.
- Workaround: There is no workaround; this issue is a current
limitation.
- Changing the assigned specific name of an SQL procedure in
the IBM Procedure Designer
- Issue: When you define a new SQL procedure in the IBM
Procedure Designer, the designer automatically assigns the value
that you enter for the procedure name to the specific name.
If you change the specific name so that it is different than the
procedure name, you cannot create a data source by dragging the
SQL procedure to the Dataset Designer.
- Workaround: If you plan to use an SQL procedure to create
a data source in a Windows application, do not change the specific
name that is assigned in the designer. Alternatively, if you change
the specific name so that that is different than the procedure name,
use the Data Source Wizard to create the data source for the
procedure.
- Table columns with LONG VARCHAR data type
- Issue: If you create a Web application and try to reference a
database table column whose data type is LONG VARCHAR, the
following error occurs:
Unknown TYPENAME LONG VARCHAR
- Workaround: Change the data type for the column to VARCHAR,
or drop the column.
- Overloaded procedures
- Issue: Web project runs only the first procedure of an
overloaded procedure.
- Create two procedures with the same name; one procedure
with no parameters, and the other procedure with one
parameter.
- Create a Web project.
- Drag an SQL data source to the project and configure the
data source.
- In the Data Source Configuration Wizard, select one
version of the overloaded procedure in the list, and then
click Test Query.
- After the test runs, select the other version of the
overloaded procedure in the list, and then click
Test Query.
In both tests, only the first version of the procedure is run.
- Workaround: There is no workaround; this issue is a
limitation.
- Debugging SQL procedures
- Issue: If you are developing an ASP.NET application in C#
or Visual Basic that uses DB2 servers, you cannot debug the SQL
procedures that are called from the Web application while you
debug the application.
- Workaround: There is no workaround; this issue is a
limitation.
- Default scripts
- Issue: The default procedure script and default function script
that you can create for a DB2 database project in the Server Explorer
are functional for DB2 servers for Linux, UNIX and Windows.
- Workaround: For DB2 Universal Database for iSeries servers and
DB2 Universal Database for z/OS servers, edit the default scripts and
add the necessary code to make the scripts functional.
- XML schema objects
- Issue:
When an XML schema is registered in the XSR Repository, the
View Definition and Open Definition
shortcut menu commands are not supported for the XML schema object.
- Workaround: There is no workaround; this issue is a current
limitation.
- DECFLOAT data type
- Issue: The DECFLOAT data type is not supported in the following
areas:
- IBM Data Designer
- Visual Studio Query Builder
- Run Options window when you are running a stored procedure or
a function
- A Windows application or a Web application that you are creating
from a stored procedure that contains a parameter with a DECFLOAT
data type
- Workaround: There is no workaround; this issue is a current
limitation.
- VARBINARY data type
- Issue: You cannot use a table that contains one or more columns
of VARBINARY data as a data source in a Windows application or a Web
application.
Running the Windows application throws an error.
When you run the Web application, the VARBINARY columns are not
displayed.
- Workaround: There is no workaround; this issue is a current
limitation.
- XML data type
- Issue: You cannot create an SQL procedure or a CLR procedure
if the procedure contains a parameter with an XML data type.
- Workaround: There is no workaround; this issue is a current
limitation.
- Data sources for tables
- Issue: If a database table contains one or more columns of
XML data type, you cannot create a data source for the table in a
Windows application. You also cannot create an SQL data source for
the table in a Web application.
- Workaround: There is no workaround; this issue is a current
limitation.
- Native SQL procedures
- Issue: The following functionality is not supported for native
SQL procedures in the Server Explorer:
- Create a native SQL procedure in the IBM Script Designer or
show a native SQL procedure script in the designer
- Workaround: There is no workaround; this issue is a current
limitation.
- Adding parameters to existing native SQL procedures
- Issue: You cannot add parameters to an existing native SQL
procedure.
- In the Server Explorer under your data connection, right-click
Procedures, and then select Add New
SQL Procedure with Designer on the shortcut menu.
- In the IBM Procedure Designer, save the procedure with the
default values, including a procedure type of
NATIVE and no parameters, and close the
designer.
- In the Server Explorer, right-click the new procedure that
you added, and then select Open Definition
on the shortcut menu.
- In the designer, add one parameter with default values, and
then save the procedure.
The following message is displayed in the IBM Output Message Pane:
Error occurred: ERROR [42601] [IBM][DB2] SQL0104N An unexpected token ...
- Workaround: Define the parameters for a native procedure
when you create the procedure.
- Creating native SQL procedure scripts
- Issue: In a DB2 Database project, you cannot create a native
SQL procedure by using a script with a .db2 extension.
- In the Solution Explorer, right-click the Scripts
folder, select Add on the shortcut menu, and then
select New Item on the submenu.
- In the Add New Item window, with Scripts selected
in the Categories list and Script
selected in the Templates box, type the name of the
script in the Name field.
Note that the script has a .db2 extension.
- Click Add.
- In the Solution Explorer, right-click the script that you added,
and then select Properties on the shortcut menu.
- In the Property Pages window, note that there is no property by which
you can set the procedure type.
- Workaround: Create the native SQL procedure by using a script with a
.db2sp extension.
- In the Solution Explorer, right-click the Scripts
folder, select Add on the shortcut menu, and then
select New Item on the submenu.
- In the Add New Item window, select Procedures
in the Categories list, select SQL
Procedure Script in the Templates box,
and then type the name of the script in the Name
field.
Note that the script has a .db2sp extension.
- Click Add.
- In the Solution Explorer, right-click the script that you added,
and then select Properties on the shortcut menu.
- In the Property Pages window, scroll down to the Procedure
Type property, and change the value of the property to
NATIVE.
- Native SQL procedure versions
- Issue: You cannot add a new version of a native SQL
procedure.
- In the Server Explorer under your data connection, right-click
Procedures, and then select Add New
SQL Procedure with Designer on the shortcut menu.
- In the IBM Procedure Designer, save the procedure with the
default values, including a procedure type of
NATIVE, and close the designer.
- In the Server Explorer, right-click the new procedure that
you added, and then select Add New Version
on the shortcut menu.
- In the designer, save the new version of the procedure with
the default values.
The following message is displayed in the IBM Output Message Pane:
Error occurred: ERROR [42601] [IBM][DB2] SQL0104N An unexpected token ...
- Workaround: There is no workaround; this issue is a current
limitation.
- Running package variations of SQL procedures
- Issue: The "Running DB2 Procedures or Functions" and "Run
Options" Help topics describe a Collection ID
list in the Run Options window. The Help topics state that you can
select the collection ID to indicate the package variation for the
SQL procedure that you want to run.
The Run Options window does not show a Collection ID
list.
- Workaround: There is no workaround; this issue is a current
limitation. You cannot run a package variation of an SQL procedure.
- Advanced SQL generation options not available for configuring data
source in Web site application
- Issue: If you are configuring a data source for an ASP.NET Web
site and want to configure the SELECT statement from a table, the
advanced SQL generation options are not available.
- Add a data connection for your database.
- Create an ASP.NET Web site.
- Display the Designer view for the .aspx file.
- Add an SqlDataSource element to the
designer form.
- Select Configure Data Source on the
displayed menu.
- Proceed through the pages of the Configure Data Source wizard,
and then perform the following actions on the Configure the
Select Statement page:
- Select the Select columns from a table or view
option.
- Select a table in the Name list.
- In the Columns list, select the check boxes
for all the primary key columns.
- Click Advanced.
The check boxes in the Advanced SQL Generation Options window are not
available.
- Workaround: There is no workaround; this issue is a current
limitation.
- Adding multiple tables
- Issue: Adding more than one table to the Table pane in
the Query Builder causes an error message to be displayed.
- In the Server Explorer, right-click your data connection,
and then select New Query on the shortcut
menu.
- In the Add Table window of the Query Builder, use the Ctrl
or Shift key to select two or more tables, and then click
Add.
A message box displays the following error condition:
Error occurred while
getting objects from the database.
The error message is also displayed if you add one table, and
then reopen the Add Table window and add another table.
- Workaround: The error condition does not affect
adding the tables. Click OK to dismiss each
instance of the message box and continue working in the
Query Builder.
- Case-sensitive table names
- Issue: The Query Builder cannot run queries on tables
that have case-sensitive names.
- In the Server Explorer, right-click your data connection,
and then select New Query on the shortcut
menu.
- In the Add Table window of the Query Builder, select a
table whose name contains lower-case letters.
- In the Table pane of the Query Builder, select a column
in the table.
- Right-click in the Query Builder, and then select
Execute SQL on the shortcut menu.
A message box displays the following error:
SQL Execution Error.
Executed SQL statement: SELECT <COLUMN_NAME>
FROM <SCHEMA_NAME>.<table_name>
Error Source: IBM.Data.DB2
Error Message: Error [42704] [IBM][DB2/NT] SQL0204N
"<SCHEMA_NAME>.<TABLE_NAME>"
is an undefined name.
SQLSTATE=42704
Workaround: Do not use the Query Builder to build
queries on tables with case-sensitive names.
- Verify SQL Syntax command
- Issue: Verifying SQL syntax causes an error condition
to occur if your data connection is DB2.
- In the Server Explorer, right-click your data connection,
and then select New Query on the shortcut
menu.
- In the Add Table window of the Query Builder, select a
table.
- Right-click in the Query Builder, and then select
Verify SQL Syntax on the shortcut menu.
A message box displays the following error:
This command is not supported by
this provider.
- Workaround: There is no workaround; this issue is a
limitation. Microsoft has stated that the Verify SQL Syntax
"feature is not supported for non-SQL Server
providers."
- Data connection shortcut menu
- Issue: When the Query Builder is open, the shortcut menu
for a data connection in the Server Explorer displays an undefined
submenu command.
- In the Server Explorer, right-click your data connection,
and then select New Query on the shortcut
menu.
- In the Add Table window of the Query Builder, click
Cancel.
- In the Server Explorer, right-click your data connection,
and then select Change View on the
shortcut menu.
The Change View submenu
displays a command named Undefined.
This condition exists whenever the Query Builder is open, regardless
of how you open it.
- Workaround: Close the Query Builder. The data connection
shortcut menu no longer displays the Change View
command.
- Incorrect SQL generated for data source configuration in
Web site application
- Issue: If you are configuring a data source for an
ASP.NET Web site and want to generate an SQL statement, the
Query Builder generates an incorrect DB2 SQL statement.
- Add a data connection for your database.
- Create an ASP.NET Web site.
- Display the Designer view for the .aspx file.
- Add an SqlDataSource element to the
designer form.
- Select Configure Data Source on the
displayed menu.
- Proceed through the pages of the Configure Data Source
wizard. On the Configure the Select Statement page, select
the Specify a custom SQL statement or stored
procedure option, and then click Next.
- On the Define Custom Statements or Stored Procedures page,
click Query Builder.
- In the Query Builder, add a table from your data connection,
and then select the check box for a column.
The generated SQL statement is:
SELECT <column_name>
FROM <schema_name>."<schema_name>.<table_name>"
when the correct SQL statement should be:
SELECT <column_name>
FROM <schema_name>.<table_name>
For example, the generated SQL statement is:
SELECT NAME
FROM BAKER."BAKER.CUSTOMER"
when the correct SQL statement should be:
SELECT NAME
FROM BAKER.CUSTOMER
- Workaround: Generate the SQL statement in the Query
Builder before you open the Configure Data Source wizard.
Make the following changes to the steps described above:
- Add an SqlDataSource element to the
designer form, and then perform the following steps:
- In the Server Explorer, right-click your data connection,
and then select New Query on the shortcut
menu.
- In the Query Builder, create the SQL statement, and then
copy the statement to the Clipboard.
- On the Define Custom Statements or Stored Procedures page,
paste the copied SQL statement in the SQL Statement
box, and then click Next.
- Skip this step; it is no longer necessary.
- Advanced SQL generation options not available for configuring data
source in Web site application
(iSeries server only)
- Issue: This issue applies only if your database is on an iSeries
server.
If you are configuring a data source for an ASP.NET Web site and
want to configure the SELECT statement from a table that does not have
an index, the advanced SQL generation options are not available.
- Add a data connection for your database.
- Create an ASP.NET Web site.
- Display the Designer view for the .aspx file.
- Add an SqlDataSource element to the
designer form.
- Select Configure Data Source on the
displayed menu.
- Proceed through the pages of the Configure Data Source wizard,
and then perform the following actions on the Configure the
Select Statement page:
- Select the Select columns from a table or view
option.
- In the Name list, select a table that does
not have an index.
- In the Columns list, select the check boxes
for all the primary key columns.
- Click Advanced.
The check boxes in the Advanced SQL Generation Options window are not
available.
- Workaround: Before you configure the data source, define an
index for the table that you want to use in the SELECT statement of
the data source configuration.
- Data Adapter Configuration Wizard license
- Issue: After you migrate a Windows application
that was developed in Visual Studio 2003 to Visual Studio
2005, you might see a window that states a license is
required.
- In a Windows application that you have migrated from
Visual Studio 2003 to Visual Studio 2005, open a form
that contains a data adapter in the Windows Forms
Designer.
- In the component tray in the designer, right-click
the data adapter, and then select Configure
Data Adapter on the shortcut menu.
An About Wizard window opens. The text in the window states
that each developer requires a license for the component.
- Workaround: Click OK to close the
About Wizard window and then proceed to use the Data Adapter
Configuration Wizard. A license is not required for the
wizard.
Support
Support for the IBM Database Add-Ins for Visual Studio 2005 -
Fix Pack 2 will be provided in the newsgroup forum developerWorks®
.NET forum. This forum will be monitored by the developers of
the IBM Database Add-Ins for Visual Studio 2005 and the IBM DB2
Data Provider for .NET Framework 2.0.
This team of IBM developers is looking to interact with you and is
extremely interested in any and all feedback or suggestions for
inclusion into upcoming drops and releases of the IBM data provider
and Add-In tools for Visual Studio and .NET.
Help make this a successful form of communication and feedback
to the IBM developers by actively engaging in the developerWorks
.NET forum.