Showing posts with label wizard. Show all posts
Showing posts with label wizard. Show all posts

Monday, March 19, 2012

Bug with Renaming Connection

I used the wizard to create a package that loads data from Access into SQL Server 2005. I then saved the package to the File System and added to my project.

I had two connections, one for SQL and one for Access. When I rename either one, the source or destination tasks in the Data Flow task reset to the other connection and/or I get an error that the old connection ID cannot be found.

I solved by opening the dtsx in Notepad and doing a global find/replace for the connection ID's. This is a real hassle.

Are you right-clicking on the connection manager and selecting rename? Or how are you renaming them?|||

That was how I tried to rename, by right-clicking. Also tried within the Properties and in the Package Explorer. Same thing.

|||

Do you want to know another bug. In the Import Data wizard that creates the package, I checked the Source box in the upper left which selected all the tables. I then went into Edit Mappings and checked to Delete Rows in Destination Tables.

However, when I execute the package, it doesn't delete the rows and instead appends the data. It might be because I am importing a lot of tables, because when I tried one table only, it worked. I believe it calls sp_executesql to execute the SQL statement and maybe the sql statement string is too long. Unfortunately, it doesn't warn that anything is incorrect, so one doesn't discover this until after testing. Don't mind bugs, but a bug like this without any kind of warning message is kind of dangerous.

|||

When building a package from the designer, renaming connections is fine, because actually the task stores the connection ID not the name.

I did a quick test with a Wizard built package and it varies, for example a snippet of the Exec SQL Task <SQLTask:SqlTaskData SQLTask:Connection="{5545ACCD-6E14-45EF-9112-2AC292C30609}" shows the use of the ID, so renames should keep working just fine, except that other stuff is doing it wrong.

For example an OLE-DB destination shows <connection id="48" name="OleDbConnection" description="The OLE DB runtime connection used to access the database." connectionManagerID="DestinationConnectionOLEDB"/></connections> which uses the name.

If I then open the package, and open the UI and close it again for the OLE-DB component, the XMl is changed to this <connection id="48" name="OleDbConnection" description="The OLE DB runtime connection used to access the database." connectionManagerID="{5545ACCD-6E14-45EF-9112-2AC292C30609}"/></connections> which clearly will survive a rename.

So why not log it at http://connect.microsoft.com

By the way, stop using notepad if you have added the package to a project. Just right click the package in the Solution Explore and select View Code. You get a much nicer text editor with better find and replace, and it keeps it all nicely liked to the designer window for the package as well. Much easier for when you do want to hack package XML directly.

Thursday, March 8, 2012

BUG IN MANAGEMENT STUDIO

I get this blow up and can reproduce it at will.
I am not going to pay to report a bug.
I also have another problem with replication. The wizard fails with a
message saying" invalid column name "options"", but I don't gave any column
named options in any table or view.
philip_38@.hotmail.com.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: InvalidArgument=Value of '52' is not
valid for 'index'.
Parameter name: index
at System.Windows.Forms.ListView.ListViewItemCollecti on.get_Item(Int32
index)
at System.Windows.Forms.ListView.set_VirtualListSize( Int32 value)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ap pIDPackage.RightPaneListViewer.set_VirtualListSize (Int32 value)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ap pIDPackage.RightPaneListViewer.RemoveItems(IList`1 items)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ap pIDPackage.RightPaneControl.RemoveItemsFromReport( INodeInformation[] nodes)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ap pIDPackage.RightPaneToolWindow.OnNodesRemoved(Obje ct sender, NodesChangedEventArgs args)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
AppIDPackage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/AppIDPackage.DLL
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
Microsoft.SqlServer.SqlTools.VSIntegration
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.SqlTools.VSIntegration.DLL
Microsoft.VisualStudio.Shell.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.dll
Microsoft.VisualStudio.OLE.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.OLE.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.OLE.Interop.dll
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
Microsoft.SqlServer.SqlTDiagM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SqlTDiagM/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.SqlTDiagM.dll
Microsoft.DataWarehouse.SQM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.DataWarehouse.SQM.DLL
Microsoft.SqlServer.Instapi
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Instapi/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.Instapi.dll
ObjectExplorer
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/ObjectExplorer.DLL
ConnectionDlg
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/ConnectionDlg.DLL
Microsoft.SqlServer.CustomControls
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.CustomControls/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.CustomControls.dll
SqlWorkbench.Interfaces
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SqlWorkbench.Interfaces.DLL
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
Microsoft.SqlServer.RegSvrEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.RegSvrEnum/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.RegSvrEnum.dll
SqlMgmt
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SqlMgmt.DLL
EnvDTE
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC/EnvDTE/8.0.0.0__b03f5f7f11d50a3a/EnvDTE.dll
Microsoft.NetEnterpriseServers.ExceptionMessageBox
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.NetEnterpriseServers.ExceptionMessageBox /9.0.242.0__89845dcd8080cc91/Microsoft.NetEnterpriseServers.ExceptionMessageBox .dll
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
Microsoft.SqlServer.ConnectionInfo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.ConnectionInfo/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.ConnectionInfo.dll
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
Microsoft.SqlServer.SmoEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SmoEnum/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.SmoEnum.dll
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
Microsoft.SqlServer.Smo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Smo/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.Smo.dll
Microsoft.SqlServer.SqlEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SqlEnum/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.SqlEnum.dll
Microsoft.SqlServer.BatchParser
Assembly Version: 9.0.242.0
Win32 Version: 2005.090.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/Microsoft.SqlServer.BatchParser/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.BatchParser.dll
msvcm80
Assembly Version: 8.0.50608.0
Win32 Version: 8.00.50727.42
CodeBase:
file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727. 42_x-ww_0DE06ACD/msvcm80.dll
ObjectExplorerReplication
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/ObjectExplorerReplication.DLL
Microsoft.ReportViewer.WinForms
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.ReportViewer.WinForms/8.0.0.0__b03f5f7f11d50a3a/Microsoft.ReportViewer.WinForms.dll
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
SQLEditors
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SQLEditors.DLL
Microsoft.VisualStudio.TextManager.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.TextManager.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.TextManager.Interop.dll
Microsoft.SqlServer.GridControl
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.GridControl/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.GridControl.dll
Microsoft.SqlServerCe.Client
Assembly Version: 9.0.242.0
Win32 Version: 3.0.5207.0
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServerCe.Client.DLL
SqlManagerUI
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SqlManagerUI.DLL
Microsoft.AnalysisServices
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.AnalysisServices/9.0.242.0__89845dcd8080cc91/Microsoft.AnalysisServices.dll
Microsoft.SqlServer.DlgGrid
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DlgGrid/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.DlgGrid.dll
Microsoft.SqlServer.DataStorage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DataStorage/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.DataStorage.dll
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Philip Orleans wrote:

> I get this blow up and can reproduce it at will.
> I am not going to pay to report a bug.
> I also have another problem with replication. The wizard fails with a
> message saying" invalid column name "options"", but I don't gave any column
> named options in any table or view.
> philip_38@.hotmail.com.
>
The support policy says that MS doesn't charge for bug reports (they
refund your advance charges). You can also file bugs online at the
Product Feedback Centre:
http://lab.msdn.microsoft.com/productfeedback/
David Portas
SQL Server MVP

BUG IN MANAGEMENT STUDIO

I get this blow up and can reproduce it at will.
I am not going to pay to report a bug.
I also have another problem with replication. The wizard fails with a
message saying" invalid column name "options"", but I don't gave any column
named options in any table or view.
philip_38@.hotmail.com.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: InvalidArgument=Value of '52' is not
valid for 'index'.
Parameter name: index
at System.Windows.Forms.ListView.ListViewItemCollection.get_Item(Int32
index)
at System.Windows.Forms.ListView.set_VirtualListSize(Int32 value)
at
Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneListViewer.set_VirtualListSize(Int32 value)
at
Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneListViewer.RemoveItems(IList`1 items)
at
Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneControl.RemoveItemsFromReport(INodeInformation[] nodes)
at
Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneToolWindow.OnNodesRemoved(Object sender, NodesChangedEventArgs args)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
---
AppIDPackage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/AppIDPackage.DLL
---
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
---
Microsoft.SqlServer.SqlTools.VSIntegration
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.SqlTools.VSIntegration.DLL
---
Microsoft.VisualStudio.Shell.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.dll
---
Microsoft.VisualStudio.OLE.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.OLE.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.OLE.Interop.dll
---
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
---
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
---
Microsoft.SqlServer.SqlTDiagM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SqlTDiagM/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.SqlTDiagM.dll
---
Microsoft.DataWarehouse.SQM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.DataWarehouse.SQM.DLL
---
Microsoft.SqlServer.Instapi
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Instapi/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.Instapi.dll
---
ObjectExplorer
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/ObjectExplorer.DLL
---
ConnectionDlg
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/ConnectionDlg.DLL
---
Microsoft.SqlServer.CustomControls
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.CustomControls/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.CustomControls.dll
---
SqlWorkbench.Interfaces
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SqlWorkbench.Interfaces.DLL
---
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
---
Microsoft.SqlServer.RegSvrEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.RegSvrEnum/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.RegSvrEnum.dll
---
SqlMgmt
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SqlMgmt.DLL
---
EnvDTE
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC/EnvDTE/8.0.0.0__b03f5f7f11d50a3a/EnvDTE.dll
---
Microsoft.NetEnterpriseServers.ExceptionMessageBox
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.NetEnterpriseServers.ExceptionMessageBox/9.0.242.0__89845dcd8080cc91/Microsoft.NetEnterpriseServers.ExceptionMessageBox.dll
---
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
---
Microsoft.SqlServer.ConnectionInfo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.ConnectionInfo/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.ConnectionInfo.dll
---
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
---
Microsoft.SqlServer.SmoEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SmoEnum/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.SmoEnum.dll
---
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
---
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
---
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
---
Microsoft.SqlServer.Smo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Smo/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.Smo.dll
---
Microsoft.SqlServer.SqlEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SqlEnum/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.SqlEnum.dll
---
Microsoft.SqlServer.BatchParser
Assembly Version: 9.0.242.0
Win32 Version: 2005.090.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/Microsoft.SqlServer.BatchParser/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.BatchParser.dll
---
msvcm80
Assembly Version: 8.0.50608.0
Win32 Version: 8.00.50727.42
CodeBase:
file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0DE06ACD/msvcm80.dll
---
ObjectExplorerReplication
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/ObjectExplorerReplication.DLL
---
Microsoft.ReportViewer.WinForms
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.ReportViewer.WinForms/8.0.0.0__b03f5f7f11d50a3a/Microsoft.ReportViewer.WinForms.dll
---
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
---
SQLEditors
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SQLEditors.DLL
---
Microsoft.VisualStudio.TextManager.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.TextManager.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.TextManager.Interop.dll
---
Microsoft.SqlServer.GridControl
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.GridControl/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.GridControl.dll
---
Microsoft.SqlServerCe.Client
Assembly Version: 9.0.242.0
Win32 Version: 3.0.5207.0
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServerCe.Client.DLL
---
SqlManagerUI
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SqlManagerUI.DLL
---
Microsoft.AnalysisServices
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.AnalysisServices/9.0.242.0__89845dcd8080cc91/Microsoft.AnalysisServices.dll
---
Microsoft.SqlServer.DlgGrid
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DlgGrid/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.DlgGrid.dll
---
Microsoft.SqlServer.DataStorage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DataStorage/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.DataStorage.dll
---
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.Philip Orleans wrote:
> I get this blow up and can reproduce it at will.
> I am not going to pay to report a bug.
> I also have another problem with replication. The wizard fails with a
> message saying" invalid column name "options"", but I don't gave any column
> named options in any table or view.
> philip_38@.hotmail.com.
>
The support policy says that MS doesn't charge for bug reports (they
refund your advance charges). You can also file bugs online at the
Product Feedback Centre:
http://lab.msdn.microsoft.com/productfeedback/
--
David Portas
SQL Server MVP
--

BUG IN MANAGEMENT STUDIO

I get this blow up and can reproduce it at will.
I am not going to pay to report a bug.
I also have another problem with replication. The wizard fails with a
message saying" invalid column name "options"", but I don't gave any column
named options in any table or view.
philip_38@.hotmail.com.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: InvalidArgument=Value of '52' is not
valid for 'index'.
Parameter name: index
at System.Windows.Forms.ListView.ListViewItemCollection.get_Item(Int32
index)
at System.Windows.Forms.ListView.set_VirtualListSize(Int32 value)
at
Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneListVi
ewer.set_VirtualListSize(Int32 value)
at
Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneListVi
ewer.RemoveItems(IList`1 items)
at
Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneContro
l.RemoveItemsFromReport(INodeInformation[] nodes)
at
Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneToolWi
ndow.OnNodesRemoved(Object sender, NodesChangedEventArgs args)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
---
AppIDPackage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/AppIDPackage.DLL
---
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System
.dll
---
Microsoft.SqlServer.SqlTools.VSIntegration
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/Microsoft.SqlServer.SqlTools.VSIntegration.DLL
---
Microsoft.VisualStudio.Shell.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop/7.1.403
04.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.dll
---
Microsoft.VisualStudio.OLE.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.OLE.Interop/7.1.40304
.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.OLE.Interop.dll
---
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561
934e089/System.Windows.Forms.dll
---
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3
a/System.Drawing.dll
---
Microsoft.SqlServer.SqlTDiagM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SqlTDiagM/9.0.242.0
__89845dcd8080cc91/Microsoft.SqlServer.SqlTDiagM.dll
---
Microsoft.DataWarehouse.SQM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/Microsoft.DataWarehouse.SQM.DLL
---
Microsoft.SqlServer.Instapi
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Instapi/9.0.242.0__
89845dcd8080cc91/Microsoft.SqlServer.Instapi.dll
---
ObjectExplorer
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/ObjectExplorer.DLL
---
ConnectionDlg
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/ConnectionDlg.DLL
---
Microsoft.SqlServer.CustomControls
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.CustomControls/9.0.
242.0__89845dcd8080cc91/Microsoft.SqlServer.CustomControls.dll
---
SqlWorkbench.Interfaces
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/SqlWorkbench.Interfaces.DLL
---
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a
/Accessibility.dll
---
Microsoft.SqlServer.RegSvrEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.RegSvrEnum/9.0.242.
0__89845dcd8080cc91/Microsoft.SqlServer.RegSvrEnum.dll
---
SqlMgmt
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/SqlMgmt.DLL
---
EnvDTE
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC/EnvDTE/8.0.0.0__b03f5f7f11d50a3a/EnvDTE.dll
---
Microsoft.NetEnterpriseServers.ExceptionMessageBox
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.NetEnterpriseServers.Exceptio
nMessageBox/9.0.242.0__89845dcd8080cc91/Microsoft.NetEnterpriseServers.Excep
tionMessageBox.dll
---
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/Sys
tem.Data.dll
---
Microsoft.SqlServer.ConnectionInfo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.ConnectionInfo/9.0.
242.0__89845dcd8080cc91/Microsoft.SqlServer.ConnectionInfo.dll
---
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/Sy
stem.Xml.dll
---
Microsoft.SqlServer.SmoEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SmoEnum/9.0.242.0__
89845dcd8080cc91/Microsoft.SqlServer.SmoEnum.dll
---
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f1
1d50a3a/System.Configuration.dll
---
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934
e089/System.Transactions.dll
---
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f
7f11d50a3a/System.EnterpriseServices.dll
---
Microsoft.SqlServer.Smo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Smo/9.0.242.0__8984
5dcd8080cc91/Microsoft.SqlServer.Smo.dll
---
Microsoft.SqlServer.SqlEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SqlEnum/9.0.242.0__
89845dcd8080cc91/Microsoft.SqlServer.SqlEnum.dll
---
Microsoft.SqlServer.BatchParser
Assembly Version: 9.0.242.0
Win32 Version: 2005.090.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/Microsoft.SqlServer.BatchParser/9.0.242.0
__89845dcd8080cc91/Microsoft.SqlServer.BatchParser.dll
---
msvcm80
Assembly Version: 8.0.50608.0
Win32 Version: 8.00.50727.42
CodeBase:
file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.
42_x-ww_0DE06ACD/msvcm80.dll
---
ObjectExplorerReplication
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/ObjectExplorerReplication.DLL
---
Microsoft.ReportViewer.WinForms
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.ReportViewer.WinForms/8.0.0.0
__b03f5f7f11d50a3a/Microsoft.ReportViewer.WinForms.dll
---
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d5
0a3a/System.Management.dll
---
SQLEditors
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/SQLEditors.DLL
---
Microsoft.VisualStudio.TextManager.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase:
file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.TextManager.Interop/7
.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.TextManager.Interop.dll
---
Microsoft.SqlServer.GridControl
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.GridControl/9.0.242
.0__89845dcd8080cc91/Microsoft.SqlServer.GridControl.dll
---
Microsoft.SqlServerCe.Client
Assembly Version: 9.0.242.0
Win32 Version: 3.0.5207.0
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/Microsoft.SqlServerCe.Client.DLL
---
SqlManagerUI
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Co
mmon7/IDE/SqlManagerUI.DLL
---
Microsoft.AnalysisServices
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.AnalysisServices/9.0.242.0__8
9845dcd8080cc91/Microsoft.AnalysisServices.dll
---
Microsoft.SqlServer.DlgGrid
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DlgGrid/9.0.242.0__
89845dcd8080cc91/Microsoft.SqlServer.DlgGrid.dll
---
Microsoft.SqlServer.DataStorage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.DataStorage/9.0.242
.0__89845dcd8080cc91/Microsoft.SqlServer.DataStorage.dll
---
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.Philip Orleans wrote:

> I get this blow up and can reproduce it at will.
> I am not going to pay to report a bug.
> I also have another problem with replication. The wizard fails with a
> message saying" invalid column name "options"", but I don't gave any colum
n
> named options in any table or view.
> philip_38@.hotmail.com.
>
The support policy says that MS doesn't charge for bug reports (they
refund your advance charges). You can also file bugs online at the
Product Feedback Centre:
http://lab.msdn.microsoft.com/productfeedback/
David Portas
SQL Server MVP
--

Bug in Ent Mgr Maintenance Plan Wizard if MSDE vs SQL

I have seen this "bug" many times personally, but cannot seem to find any posting on the Internet about it. I have many customers using MSDE
The bug is with the Database Maintenance Plans of Microsoft SQL Enterprise Manager when connecting to MSDE.
Yes, yes, I realize that MSDE (Microsoft SQL Desktop Edition) does NOT include licence for Enterprize Manager (EM)... but any technician who does have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access Licence) does have Enterprize Manag
er and can connect and manage MSDE and SQL engines/servers equally well.
Consider http://support.microsoft.com/default...22&Product=sql Here we see substantiation that one "can" use EM and Maintenance Plans on MSDE, albeit that you had better be the latest Service Pack since the sqlmaint feature was over
looked in the original release to market.
The bug I am reporting is with the "Remove after X Weeks/Days" option for Database Backup, Transaction Backup (and Log text files). This is important because unless you can also choose to do so, one will end up filling the hard disk with far too many SQL
dumps.
If connected to an SQL server... the option works fine. If connected to an MSDE, the option fails to provie the drop-down for days/weeks and the resulting job created has bugs in the command line options of the job step which one must then go and manuall
y tweak to be correct (never report a bug without a workaround eh? ;-P)
John,
As far as im aware this happens because the maintenance wizard
(sqlmaint.exe) is looking for a backupdirectory string valuein the MSDE
instance registry location.
(I would maybe do this on a test machine first if possible or make sure you
have backups)
So firstly make sure the following backup folder path exists , if not create
it :
c:\program files\microsoft sql server\<MSDE instance>\Backup.
Then in regedit:
HKLM\Software\Microsoft\Microsoft SQL Server\<MSDE instance>\MSSQLserver
there should be a BackupDirectory string value , the value data should be
the physical path to the backup folder in our case c:\program
files\microsoft sql server\<MSDE instance>\Backup.
HTH
Dylan
"John D. Sullivan" <John D. Sullivan@.discussions.microsoft.com> wrote in
message news:835E25B5-6EE5-4533-A1D5-43D3873BC0B1@.microsoft.com...
> I have seen this "bug" many times personally, but cannot seem to find any
posting on the Internet about it. I have many customers using MSDE
> The bug is with the Database Maintenance Plans of Microsoft SQL Enterprise
Manager when connecting to MSDE.
> Yes, yes, I realize that MSDE (Microsoft SQL Desktop Edition) does NOT
include licence for Enterprize Manager (EM)... but any technician who does
have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access
Licence) does have Enterprize Manager and can connect and manage MSDE and
SQL engines/servers equally well.
> Consider
http://support.microsoft.com/default...22&Product=sql
Here we see substantiation that one "can" use EM and Maintenance Plans on
MSDE, albeit that you had better be the latest Service Pack since the
sqlmaint feature was overlooked in the original release to market.
> The bug I am reporting is with the "Remove after X Weeks/Days" option for
Database Backup, Transaction Backup (and Log text files). This is important
because unless you can also choose to do so, one will end up filling the
hard disk with far too many SQL dumps.
> If connected to an SQL server... the option works fine. If connected to
an MSDE, the option fails to provie the drop-down for days/weeks and the
resulting job created has bugs in the command line options of the job step
which one must then go and manually tweak to be correct (never report a bug
without a workaround eh? ;-P)
|||Thanks for the thought. No that's not what I mean (see my additional post
in next thread). About the backup folder here is what I did discover the
hard way..
When creating the Maintenance Plan...if one chooses "use the default backup
directory" then it seems to work, and the (first) backup will create the
folder path even if it did not yet exist. However if you specify a "use
this directory" to backup to... then I have found that folder you specify
had better exist already because the backup job will fail rather than create
it. So there's a little idiosyncracy for ya. (I have not experienced the
issue you mention, but perhaps that is an issue if the SQL is installed as a
"named" instance of SQL instead of the default/single instance of SQL? in
which case thank you for the additional tweaks)
John D. Sullivan
ABELSoft Corporation
"Dylan Kruger" <carmellobear1@.hotmail.com> wrote in message
news:OQXmdsjaEHA.3596@.tk2msftngp13.phx.gbl...
> John,
> As far as im aware this happens because the maintenance wizard
> (sqlmaint.exe) is looking for a backupdirectory string valuein the MSDE
> instance registry location.
> (I would maybe do this on a test machine first if possible or make sure
you
> have backups)
> So firstly make sure the following backup folder path exists , if not
create[vbcol=seagreen]
> it :
> c:\program files\microsoft sql server\<MSDE instance>\Backup.
> Then in regedit:
> HKLM\Software\Microsoft\Microsoft SQL Server\<MSDE instance>\MSSQLserver
> there should be a BackupDirectory string value , the value data should be
> the physical path to the backup folder in our case c:\program
> files\microsoft sql server\<MSDE instance>\Backup.
> HTH
> Dylan
>
>
> "John D. Sullivan" <John D. Sullivan@.discussions.microsoft.com> wrote in
> message news:835E25B5-6EE5-4533-A1D5-43D3873BC0B1@.microsoft.com...
any[vbcol=seagreen]
> posting on the Internet about it. I have many customers using MSDE
Enterprise[vbcol=seagreen]
> Manager when connecting to MSDE.
> include licence for Enterprize Manager (EM)... but any technician who does
> have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access
> Licence) does have Enterprize Manager and can connect and manage MSDE and
> SQL engines/servers equally well.
> http://support.microsoft.com/default...22&Product=sql
> Here we see substantiation that one "can" use EM and Maintenance Plans on
> MSDE, albeit that you had better be the latest Service Pack since the
> sqlmaint feature was overlooked in the original release to market.
for
> Database Backup, Transaction Backup (and Log text files). This is
important
> because unless you can also choose to do so, one will end up filling the
> hard disk with far too many SQL dumps.
> an MSDE, the option fails to provie the drop-down for days/weeks and the
> resulting job created has bugs in the command line options of the job step
> which one must then go and manually tweak to be correct (never report a
bug
> without a workaround eh? ;-P)
>

Bug in Ent Mgr Maintenance Plan Wizard if MSDE vs SQL

I have seen this "bug" many times personally, but cannot seem to find any posting on the Internet about it. I have many customers using MSDE
The bug is with the Database Maintenance Plans of Microsoft SQL Enterprise Manager when connecting to MSDE.
Yes, yes, I realize that MSDE (Microsoft SQL Desktop Edition) does NOT include licence for Enterprize Manager (EM)... but any technician who does have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access Licence) does have Enterprize Manag
er and can connect and manage MSDE and SQL engines/servers equally well.
Consider http://support.microsoft.com/default...22&Product=sql Here we see substantiation that one "can" use EM and Maintenance Plans on MSDE, albeit that you had better be the latest Service Pack since the sqlmaint feature was over
looked in the original release to market.
The bug I am reporting is with the "Remove after X Weeks/Days" option for Database Backup, Transaction Backup (and Log text files). This is important because unless you can also choose to do so, one will end up filling the hard disk with far too many SQL
dumps.
If connected to an SQL server... the option works fine. If connected to an MSDE, the option fails to provie the drop-down for days/weeks and the resulting job created has bugs in the command line options of the job step which one must then go and manuall
y tweak to be correct (never report a bug without a workaround eh? ;-P)
John,
As far as im aware this happens because the maintenance wizard
(sqlmaint.exe) is looking for a backupdirectory string valuein the MSDE
instance registry location.
(I would maybe do this on a test machine first if possible or make sure you
have backups)
So firstly make sure the following backup folder path exists , if not create
it :
c:\program files\microsoft sql server\<MSDE instance>\Backup.
Then in regedit:
HKLM\Software\Microsoft\Microsoft SQL Server\<MSDE instance>\MSSQLserver
there should be a BackupDirectory string value , the value data should be
the physical path to the backup folder in our case c:\program
files\microsoft sql server\<MSDE instance>\Backup.
HTH
Dylan
"John D. Sullivan" <John D. Sullivan@.discussions.microsoft.com> wrote in
message news:835E25B5-6EE5-4533-A1D5-43D3873BC0B1@.microsoft.com...
> I have seen this "bug" many times personally, but cannot seem to find any
posting on the Internet about it. I have many customers using MSDE
> The bug is with the Database Maintenance Plans of Microsoft SQL Enterprise
Manager when connecting to MSDE.
> Yes, yes, I realize that MSDE (Microsoft SQL Desktop Edition) does NOT
include licence for Enterprize Manager (EM)... but any technician who does
have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access
Licence) does have Enterprize Manager and can connect and manage MSDE and
SQL engines/servers equally well.
> Consider
http://support.microsoft.com/default...22&Product=sql
Here we see substantiation that one "can" use EM and Maintenance Plans on
MSDE, albeit that you had better be the latest Service Pack since the
sqlmaint feature was overlooked in the original release to market.
> The bug I am reporting is with the "Remove after X Weeks/Days" option for
Database Backup, Transaction Backup (and Log text files). This is important
because unless you can also choose to do so, one will end up filling the
hard disk with far too many SQL dumps.
> If connected to an SQL server... the option works fine. If connected to
an MSDE, the option fails to provie the drop-down for days/weeks and the
resulting job created has bugs in the command line options of the job step
which one must then go and manually tweak to be correct (never report a bug
without a workaround eh? ;-P)
|||Thanks for the thought. No that's not what I mean (see my additional post
in next thread). About the backup folder here is what I did discover the
hard way..
When creating the Maintenance Plan...if one chooses "use the default backup
directory" then it seems to work, and the (first) backup will create the
folder path even if it did not yet exist. However if you specify a "use
this directory" to backup to... then I have found that folder you specify
had better exist already because the backup job will fail rather than create
it. So there's a little idiosyncracy for ya. (I have not experienced the
issue you mention, but perhaps that is an issue if the SQL is installed as a
"named" instance of SQL instead of the default/single instance of SQL? in
which case thank you for the additional tweaks)
John D. Sullivan
ABELSoft Corporation
"Dylan Kruger" <carmellobear1@.hotmail.com> wrote in message
news:OQXmdsjaEHA.3596@.tk2msftngp13.phx.gbl...
> John,
> As far as im aware this happens because the maintenance wizard
> (sqlmaint.exe) is looking for a backupdirectory string valuein the MSDE
> instance registry location.
> (I would maybe do this on a test machine first if possible or make sure
you
> have backups)
> So firstly make sure the following backup folder path exists , if not
create[vbcol=seagreen]
> it :
> c:\program files\microsoft sql server\<MSDE instance>\Backup.
> Then in regedit:
> HKLM\Software\Microsoft\Microsoft SQL Server\<MSDE instance>\MSSQLserver
> there should be a BackupDirectory string value , the value data should be
> the physical path to the backup folder in our case c:\program
> files\microsoft sql server\<MSDE instance>\Backup.
> HTH
> Dylan
>
>
> "John D. Sullivan" <John D. Sullivan@.discussions.microsoft.com> wrote in
> message news:835E25B5-6EE5-4533-A1D5-43D3873BC0B1@.microsoft.com...
any[vbcol=seagreen]
> posting on the Internet about it. I have many customers using MSDE
Enterprise[vbcol=seagreen]
> Manager when connecting to MSDE.
> include licence for Enterprize Manager (EM)... but any technician who does
> have a licenced copy of SQL (Standard, Enterprize etc) CAL (Client Access
> Licence) does have Enterprize Manager and can connect and manage MSDE and
> SQL engines/servers equally well.
> http://support.microsoft.com/default...22&Product=sql
> Here we see substantiation that one "can" use EM and Maintenance Plans on
> MSDE, albeit that you had better be the latest Service Pack since the
> sqlmaint feature was overlooked in the original release to market.
for
> Database Backup, Transaction Backup (and Log text files). This is
important
> because unless you can also choose to do so, one will end up filling the
> hard disk with far too many SQL dumps.
> an MSDE, the option fails to provie the drop-down for days/weeks and the
> resulting job created has bugs in the command line options of the job step
> which one must then go and manually tweak to be correct (never report a
bug
> without a workaround eh? ;-P)
>

Wednesday, March 7, 2012

BUG in BIDS when developing SSIS packages

There seems to be a BUG in BIDS when developing SSIS packages using the Import/Export Data wizard.

If you use the wizard to import a large number of tables, and then select all the tables, and then choose to delete exisiting data in each table, the PrologueSQL file does NOT get built correctly. Instead of having a

TRUNCATE tablename Go

for each table, it just has a bunch of "Go"s with nothing between them. In the step immediately prior, where you confirm what the wizard will do, it tells you, after each table, that it will delete any existing data...but it doesn't do this.

If, during the wizard, I select each individual table one at a time and tell it to delete existing data, then it will get built correctly, but not if I select them all at once...YET, if I do select the whole block, choose delete existing data, and then select any single table, it shows that table as being set up to delete existing rows.

This is very frustrating when trying to import large numbers of tables.

Am I missing something? or is this really a bug?

Thanks, Jeff

Jeff,

We've noticed the same behavior here. If we edit the mappings for each of the tables individually we see that the 'Delete rows in destination table' is selected (after selecting that option for the group). If we click OK for the mappings dialog the TRUNCATE options is then correctly added to the package.

I vote for bug.

Ray

|||Post it at:

http://connect.microsoft.com/sqlserver/feedback|||

Yes, this is a known bug.

The best workaround I can offer is to unselect the "Optimize for Many Tables" checkbox. The transfer will probably succeed if the number of tables is resonable (say less than 100) for your hardware (transfers will go in parallel). If it fails, try to go in multiple batches with smaller number of tables.

Thanks.

BUG in BIDS when developing SSIS packages

There seems to be a BUG in BIDS when developing SSIS packages using the Import/Export Data wizard.

If you use the wizard to import a large number of tables, and then select all the tables, and then choose to delete exisiting data in each table, the PrologueSQL file does NOT get built correctly. Instead of having a

TRUNCATE tablename Go

for each table, it just has a bunch of "Go"s with nothing between them. In the step immediately prior, where you confirm what the wizard will do, it tells you, after each table, that it will delete any existing data...but it doesn't do this.

If, during the wizard, I select each individual table one at a time and tell it to delete existing data, then it will get built correctly, but not if I select them all at once...YET, if I do select the whole block, choose delete existing data, and then select any single table, it shows that table as being set up to delete existing rows.

This is very frustrating when trying to import large numbers of tables.

Am I missing something? or is this really a bug?

Thanks, Jeff

Jeff,

We've noticed the same behavior here. If we edit the mappings for each of the tables individually we see that the 'Delete rows in destination table' is selected (after selecting that option for the group). If we click OK for the mappings dialog the TRUNCATE options is then correctly added to the package.

I vote for bug.

Ray

|||Post it at:

http://connect.microsoft.com/sqlserver/feedback|||

Yes, this is a known bug.

The best workaround I can offer is to unselect the "Optimize for Many Tables" checkbox. The transfer will probably succeed if the number of tables is resonable (say less than 100) for your hardware (transfers will go in parallel). If it fails, try to go in multiple batches with smaller number of tables.

Thanks.

BUG : Data source not appearing

Hello,

I am trying make some imports and I am using the wizard.

I have created a new project and added 2 new datasources. One for a DB2 database and one for a SQL Server database

I select Project | SS Import and Export Wizard and the wizard launches.

When I look under datasource I can't find my 2 created datasources. I can create new ones but this is not something I want.

Any help ?

Constantijn Enders

Are you trying to create data sources, via the 'Data Sources' in the BI Project? if so, the data sources created in there will not be shared/visible in import/export wizard or the package.

Import/Export wizard has no access to project level artifacts, but is simply a way to auto-generate packages. Please try creating a package for your solution.

|||

It would be handy if the import/export wizard could access the project items. Perhaps for a next version.

I am importing from a DB2 system and setting up the oledb connection requires at least 3 screens.

You can only import multiple tables and/or views OR a single query. (not multiple queries)

If you have 10 queries, you have to setup that connection 10 times

Just my 2 cents

CE