Showing posts with label management. Show all posts
Showing posts with label management. Show all posts

Monday, March 19, 2012

bug: "autostat" of an index reported by SQL Server Management Studio for 2005

Do not know if any one has complained this to Microsoft.
SQL server management studio does not seem to display the "autostat" of
an index correctly. The value in SQL server management studio is
always the reverse of the value from "sp_autostats".
to reproduce, high light a table in object explorer -> right click to
select Modify -> click "manage indexes and keys" -> select the index ,
the value of "Re-compute Statistics" is always the reverse of the value
of the corresponding index from "sp_autostats".
Thanks.
Kong
(likong@.email.com) writes:
> Do not know if any one has complained this to Microsoft.
> SQL server management studio does not seem to display the "autostat" of
> an index correctly. The value in SQL server management studio is
> always the reverse of the value from "sp_autostats".
> to reproduce, high light a table in object explorer -> right click to
> select Modify -> click "manage indexes and keys" -> select the index ,
> the value of "Re-compute Statistics" is always the reverse of the value
> of the corresponding index from "sp_autostats".
Actually, I can't recall having seen this particular issue reported.
When playing around, it appears that someone has gotten confused over
the DLL, where the option is STATISTICS_NORECOMPUTE=ON/OFF. If you believe
what the dialog says, and change No to Yes, you will alter the setting.
The place to report bugs like this is
http://lab.msdn.microsoft.com/ProductFeedback/, and I encourage you to
go there.
By the way, if you right-click the index, select Properties, and go to
the Options page, you will see that on this screen they have it right.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Bug with SQL Server 2005 Management studio

Hi,

I'm having a really annoying problem with SQL Server 2005 Management studio. I've just imported a very large database with 1,175,966 records in org_details table. During the import primary didn't transfer, so I thought I'd use management studio to alter the table and reset a primary key. however I get the following error. I want to restart the identity at 2213364 but I get the following error, also if its only 1 by 1. I've read it can be related to log file however I've increase the size to 8 GB.

ERROR:

'org_details' table
- Unable to create index 'PK_org_details'.
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

This is really frustrating as I don't remember having issue like this with SQL Server 2000.

Thanks help or assistance.

Unfortunately, the error message doesn't let you know which timeout setting expired.

My guess is the table designer timeout. In Management Studio, go to

Tools|Options|Designers|Table and Database Designers

Uncheck "Override connection string time-out value for table designer updates." (The default is checked, with an override value of 30 seconds. That could be too short for you.)

Two other timeout settings that might be issues are mentioned in the answer to this similar question:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=291327&SiteID=1

Steve Kass

Drew University

http://www.stevekass.com

|||

The root cause of this problem is you have choosen Import/Export wizard to transfer data which will only transfer data not the exact schema like PK,FK,Check Constraints etc. So when you want exact schema in the target database , script the source database and run the script in target db and then use IMport/Export to transfer data to the newly created tables. I would suggest you to use Script to create PK when the table is huge.

Madhu

|||

Thank you, you make a very valid point. The problem is related to a client of mine who has an access database, yes I said access with over 1 million records. In my opinion SQL management studio should support the manipulation of large databases.Yes it’s a large database however database’s these-days are large, lets be realistic a 1 million plus database isn’t uncommon.

I'm looking for a solution to SQL Server 2005 management studio problem not a scripting alternative, although thank you anyway.

|||thankyou I changed the timeout to 240 seconds now the transaction works.

Bug or Feature

I noticed something when using Management Studio that I don't know if it's a bug or a feature. So if you have a login that's mapped to a user name in several databases, and you delete the login from the server using Management Studio, the user name is still left in the databases. This happens on a SQL 2000 or 2005 instance.

If I use Enterprise Manager and do the same function, the login is removed from the server as well as all databases where it was a valid user.

Any ideas?

Thanks,

Jason

It is by design as the user may own objects in some database, and some of the DBs may be offline or read-only. When you drop the login, the corresponding user in any DB will become an “orphan user”, and the behavior will be similar to restoring a database with user information without corresponding logins.

The sysadmin will have the opportunity to cleanup the “orphan users” by changing ownership of the objects in any given database and deleting the user or simply by mapping the orphan user to a different login using sp_change_Users_login.

I hope I was able to answer your question.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Okay, that explains it. Thanks for the info!

It would be nice if when the user owns an object, SQL Server changes the value in some flag for example, and then when the login is dropped from the server, SQL Server looks at that flag and say if it is set to 0, then drop the user from all databases, but if it is set to 1, drop the login but not the user from the database. This way it is less maintenance for the DBA to come through and clean up orphan users. Just my 2 cents.

Jason

Thursday, March 8, 2012

Bug in MS Management Studio for SQL-Server 2005 while creating a publication!

Hello,

I found a bug in Management Studio, which can be reproduced with following steps:

1. Create a new publication with the 'New Publication Wizard'
2. Select a database which contains at least 2 tables.
3. Select 'transactional publicatioon'
4. Select at least 2 tables as articles
5. Set article properties for all table articles
6. Change 'Statement Delivery' to 'Insert statement', 'Update statement' and 'Delete statement' and save the article properties.
7. If you now check the properties for a single article you find that the 'Statement Delivery' is set to 'Do not replicate...'. If you generate this publication and create a subscritpion you will see, that actual no replication take place.

It took me a while to find out why my replication doesn't work! :-((

Wolfgang Kunk

PS : Management Studio version is 9.00.1399.00

Unfortunately that part of the wizard is kind of broke, and it won't get fixed for SP2 either. A similar issue was raised in an earlier post as well - http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=984751&SiteID=1.

The workaround is to either use TSQL scripts to set everything up, or set everything up with UI and then immediately issue a sp_changearticle to set it.

As a side note, may I ask why you want to use "Insert/Update/Delete statement" instead of the default stored proc? This can have bad performance impact against a SQL subscriber.

|||Normally we use T-SQL scripts to set up replication. So it is not a real big problem.
I wanted to see if it is a known bug!

Can you please explain what the bad performance impact can be?
As far as I know the default stored procs execute nothing else then a simple insert, update or delete statement. So I cannot see a bad impact. The only thing is that the optimizer optimzes a stored proc once while it has to optimize insert, update ans delete-statements every time.

Wolfgang Kunk|||

When using stored procs, each proc is fired off as an individual RPC, and the proc itself generates a plan that can be reused over and over for optimal performance.

When using SQL, we fit as many commands as we can (I think up to 500) into a single parameterized sp_executesql and execute it all at once. Meaning one single sp_executesql call can have anywhere from one to 500 different ins/upd/del statements - this generates one single plan. The next sp_executesql call will most likely be different, and generate a totally different plan. So what happens is every call will most likely have to be compiled because you'll never get plan reuse. In an OLTP scenario where you're replicating thousands of commands a second, you'lll definitely see an impact in performance.

For proof, apply a mixed/random workload to the publisher and then trace the distribution agent calls at the subscriber using SQL and stored procs, you'll see what I mean.

SQL is used mostly with heterogeneous subscriber cases and the very rare case when customer has a purpose for SQL subscriber cases.

|||Thanks for the explanation.

At the moment we only use heterogenous subscriber, where we work with SQL. So I used SQL for my first MS-MS Replication as well. I will take your recommendation in account for my further tests!

Wolfgang Kunk

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
--

Friday, February 24, 2012

Browsing a cube in ssrs Matrix

When we browse the cube in management studio we are able to see the correct aggregates where as in the report from reporting services we are just getting the sums instead of running aggregates especially in the intersection cells of columns and rows. ( where ever the aggregrate function is difference/division. )

Is there a setting in reporting services which would make the report return the running aggregates like in the management studio.

thanks in advance

The brower is diferent in Reporting Services, but if you use the MATRIX in reporting Services, you all the cells for columns, rows and data!

Try it... if you never did that, use the wizard!

Helped?

Regards!

|||

--

|||

PedroCGD wrote:

The brower is diferent in Reporting Services, but if you use the MATRIX in reporting Services, you all the cells for columns, rows and data!

Try it... if you never did that, use the wizard!

Helped?

Regards!

Can you eloborate please.

Even when I use the matrix and the wizard still it dosent give me the running aggegates it is just giving me the sum in the intersections cells.

Any thots ?

Browse mssqlsystemresource.mdf (SQL Server's Resource Database)

Is there a way to have the Resource Database (mssqlsystemresource.mdf) appear
in the list of Databases in SQL Server Management Studio for easy browsing of
it's contents, or is the only browse option to open the MDF file with a text
editor such as notepad?
Thanks.
Chris Jones
Application Development Consultant
Giving credit where credit is due, I found the following info I am about to
post at the following location:
http://www.aspfaq.com/sql2005/show.asp?id=28
Since the engine has hooks that hide the mssqlsystemresource database from
users, you don't have direct access to it through the GUI.
However, there is a way around this:
1.)Determine where the system databse files live, and keep this path handy:
USE master
GO
SELECT REPLACE(filename, 'master.mdf', '')
FROM sys.sysfiles
WHERE fileid = 1
2.)Stop the SQL Server service;
3.)Copy the files mssqlsystemresource.*df -> resource_copy.*df.
NOTE: do *not* rename or remove the mssqlsystemresource files!
4.)Start the SQL Server service;
5.)Run the following code in a new query window:
EXEC sp_attach_db
'Resource_Copy',
'<path from above>resource_copy.mdf',
'<path from above>resource_copy.ldf'
6.)Now, the system will no longer identify this database as a "special"
database
7.)You can easily scan through the names of system objects that might
otherwise be unknown (and browse any code associated with these objects) from
a GUI (like SQL Server Management Studio).
Thanks.
Chris Jones
Application Development Consultant
"Chris" wrote:

> Is there a way to have the Resource Database (mssqlsystemresource.mdf) appear
> in the list of Databases in SQL Server Management Studio for easy browsing of
> it's contents, or is the only browse option to open the MDF file with a text
> editor such as notepad?
> --
> Thanks.
> Chris Jones
> Application Development Consultant
|||Yes, if you start your SQL Server is single user mode.
Why do you need to see the contents? It just contains definitions of stored
procedures and views, and you can get to all those using the
OBJECT_DEFINITION function.
HTH
Kalen Delaney, SQL Server MVP
http://sqlblog.com
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:83427BEB-8A5E-4A21-B8CC-EF65E1BEF9DD@.microsoft.com...
> Is there a way to have the Resource Database (mssqlsystemresource.mdf)
> appear
> in the list of Databases in SQL Server Management Studio for easy browsing
> of
> it's contents, or is the only browse option to open the MDF file with a
> text
> editor such as notepad?
> --
> Thanks.
> Chris Jones
> Application Development Consultant

Browse mssqlsystemresource.mdf (SQL Server's Resource Database)

Is there a way to have the Resource Database (mssqlsystemresource.mdf) appea
r
in the list of Databases in SQL Server Management Studio for easy browsing o
f
it's contents, or is the only browse option to open the MDF file with a text
editor such as notepad?
Thanks.
Chris Jones
Application Development ConsultantGiving credit where credit is due, I found the following info I am about to
post at the following location:
http://www.aspfaq.com/sql2005/show.asp?id=28
Since the engine has hooks that hide the mssqlsystemresource database from
users, you don't have direct access to it through the GUI.
However, there is a way around this:
1.)Determine where the system databse files live, and keep this path handy:
USE master
GO
SELECT REPLACE(filename, 'master.mdf', '')
FROM sys.sysfiles
WHERE fileid = 1
2.)Stop the SQL Server service;
3.)Copy the files mssqlsystemresource.*df -> resource_copy.*df.
NOTE: do *not* rename or remove the mssqlsystemresource files!
4.)Start the SQL Server service;
5.)Run the following code in a new query window:
EXEC sp_attach_db
'Resource_Copy',
'<path from above>resource_copy.mdf',
'<path from above>resource_copy.ldf'
6.)Now, the system will no longer identify this database as a "special"
database
7.)You can easily scan through the names of system objects that might
otherwise be unknown (and browse any code associated with these objects) fro
m
a GUI (like SQL Server Management Studio).
--
Thanks.
Chris Jones
Application Development Consultant
"Chris" wrote:

> Is there a way to have the Resource Database (mssqlsystemresource.mdf) app
ear
> in the list of Databases in SQL Server Management Studio for easy browsing
of
> it's contents, or is the only browse option to open the MDF file with a te
xt
> editor such as notepad?
> --
> Thanks.
> Chris Jones
> Application Development Consultant|||Yes, if you start your SQL Server is single user mode.
Why do you need to see the contents? It just contains definitions of stored
procedures and views, and you can get to all those using the
OBJECT_DEFINITION function.
HTH
Kalen Delaney, SQL Server MVP
http://sqlblog.com
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:83427BEB-8A5E-4A21-B8CC-EF65E1BEF9DD@.microsoft.com...
> Is there a way to have the Resource Database (mssqlsystemresource.mdf)
> appear
> in the list of Databases in SQL Server Management Studio for easy browsing
> of
> it's contents, or is the only browse option to open the MDF file with a
> text
> editor such as notepad?
> --
> Thanks.
> Chris Jones
> Application Development Consultant

Thursday, February 16, 2012

Bring back Query Analyser

Hi,
I am using 2005 SQL Management to edit my T-SQL stuff but it reformats all
of my SQL statements (just like Enterprise Manager) making complex
statements impossible to read.
Can anyone tell me if there any options to turn this off and/or an
alternative?
Thanks for any help,
Steve.I am using 2K5 SQL Management, your problem doesn't occur at my site.
Do you use query builder?
Steve Lloyd wrote:
> Hi,
> I am using 2005 SQL Management to edit my T-SQL stuff but it reformats all
> of my SQL statements (just like Enterprise Manager) making complex
> statements impossible to read.
> Can anyone tell me if there any options to turn this off and/or an
> alternative?
> Thanks for any help,
> Steve.|||Hi, thanks for the reply,
Ok, find out a few more things... Stored procedures open using query builder
and I can retain the formatting but Views open Enterpise Manager style and I
can't work out how to stop it...
Thanks again
Steve
<navyzhu@.gmail.com> wrote in message
news:1149757541.865478.194360@.h76g2000cwa.googlegroups.com...
>I am using 2K5 SQL Management, your problem doesn't occur at my site.
> Do you use query builder?
> Steve Lloyd wrote:
>|||Steve Lloyd (steve.remove@.livenowpaylater.this.co.uk) writes:
> Ok, find out a few more things... Stored procedures open using query
> builder and I can retain the formatting but Views open Enterpise Manager
> style and I can't work out how to stop it...
Stop using the Query Designer.
After all, since the subject line says bring back "Query Analyzer", you
should be used to be without the Query Designer as it is not present in
Query Analyzer.
As long as you stick to the regular query editor in Mgmt Studio, there
should be no reformatting.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||In addition to Erland's post:
Keep your DDL scripts somewhere safe, and only use them to create/alter/drop
SQL objects.
ML
http://milambda.blogspot.com/|||OK, it think I'm not making myself clear.. I want to be able to edit my
Views, Query Analyzer style, but when I open them in SQL Management they
default to the Query Builder and I can't work out how to open them without.
Sorry for the confusion...
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns97DC7DAD2FAEBYazorman@.127.0.0.1...
> Steve Lloyd (steve.remove@.livenowpaylater.this.co.uk) writes:
> Stop using the Query Designer.
> After all, since the subject line says bring back "Query Analyzer", you
> should be used to be without the Query Designer as it is not present in
> Query Analyzer.
> As long as you stick to the regular query editor in Mgmt Studio, there
> should be no reformatting.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||Right click on the view
DO NOT select modify view
Instead choose Script View as -->ALTER To--> New Query window
Denis the SQL Menace
http://sqlservercode.blogspot.com/
Steve Lloyd wrote:
> OK, it think I'm not making myself clear.. I want to be able to edit my
> Views, Query Analyzer style, but when I open them in SQL Management they
> default to the Query Builder and I can't work out how to open them without
.
> Sorry for the confusion...
> "Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
> news:Xns97DC7DAD2FAEBYazorman@.127.0.0.1...|||> Right click on the view
> DO NOT select modify view
> Instead choose Script View as -->ALTER To--> New Query window
This is easily in my top ten of pet peeves in Management Studio. Not just
because Modify does this weird thing with a useless Access-style view
designer that drives me bonkers, but combined with the slowness and the
frequency that I click the wrong menu item, it is maddening.
I was told off the cuff that they're going to add some options to the
immediate right-click menu for views, but I don't know when they'll be
implemented...

Sunday, February 12, 2012

Bought and installed VS2005 professional - There is no Management studio got installed in

Hi Friends,

I have a question. At my home computer i downloaded and
installed VWD. As usual it also installed Sqlexpress as part of the
installation(i checked the option). Later on i downloaded Management
studio separately so i am fine with my home computer as every thing is free.

But at work we decided to develop application using VS 2005 and Sqlserver 2005. So we bought and installed VS2005 professional edition at work and it also installed Sqlexpress during the installation as a defualt desktop engine. I am fine with that too. But i am not
understing where do i get the Management studio? Is it some thing i
could get it off the web for free or what? I am not sure we would have an option while installing the VS 2005 professional that also does install management studio and we need to check that option. I am not sure if we could get the management studion off the web for free and and evelop applications.


Please advise.
Thanks
-L

Off the SQL Server 2005 CD. I believe there is a Management Studio Express as well available for download from MS. Kind of a braindead way to do things, as I expect that a lot of VS 2005 Professionals will be in the same situation as me that I develop on SQL Express, and then push to SQL Server 2005 (I also need to manage SQL Server 2000 and 2005 machines as well). It would have been nice if they just put Management Studio in VS 2005 from the start. Management Studio can work with SQL Express, 2005, and most of 2000 (Optional DTS download needed).|||

Yes we can download the Management Studio Express for free from MS website. I did the same thing on my personal laptop. But can we develop applications using free downloaded Management Studio and deploy later on with the free stuff at work?

Or else like you have mentioned may be i want to get it off Sql server 2005.

May be you can help me figuring out where i can get it off

Its kind of confusing what to install of all the CDs we got when we bought the software.

Please bear with me the list of CDs we have is:

1).Microsoft Visual Studio 2005 Professional Edition (Disc1 & Disc 2)

2)Microsoft Visual Studio 2005 Professional Edition (SQL Server 2005 Developer Edition 32-bit Cd1 & CD2)

3).Microsoft SQL Server 2005 Developer Edition (32 bit) (Disc1 & Disc 2)

4).Microsoft Visual Studio 2005 Professional Edition (SQL Server 2005 Developer Edition IA 64-bit CD1 and CD2)

5).Microsoft Sql server 2005 Developer Edition for Itanium-based Systems (Disc 1 & Disc 2)

6).Microsoft Sql server 2005 Developer Edition (X64) (Disc 1 & Disc 2)

7).Microsoft Visual Studio 2005 Professional Edition (Sql server 2005 Developer Edition 64-bit CD1 & CD2)

My work machine runs on Windows XP Prof . Of all the above CDs I installed Visual Studio 2005 Professional alone. So i have VS 2005 installed and also SQL Express.

Like you said can use #2 set of CDs to get Management Studio or #3 set of CDs(i have windows XP professional installed on my work machine)?

We have already ordered another development box from Dell and we are going to have Windows 2003 server on that. Correct me if i am wrong, #4,5, and 6 set of CDs are designed for 64-bit Windows 2003 server.

what is IA in #4 set of CDs and Itanium-based system in #5 respectively?

Am i getting you confusing with lot of stupid questions here :)?

I have lot of questions with the new stuff.

Thanks

-L

|||Wish I could help you. Unfortunately, I don't have a set of retail disks. My home machine has .ISO's I downloaded from MSDN (I have a personal MSDN Subscription), and at work, they install whatever I tell them to, but they lock up the disks and licenses.