Error installing SQL Server Developer 2005

I'm trying to install Microsoft SQL Server 2005 Developer Edition and each
time I attempt to I get the error message:
"Failed to install and configure assemblies C:\Program Files\Microsoft SQL
Server\90\NotificationServices\9.0.242\Bin\microsoft.sqlserver.notificationservices.dll
in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: MSDTC was unable to read its configuration information.
(Exception from HRESULT: 0x8004D027)"
Not only that, but in my Component Services->Distributed Transaction
Coordinator section, I get the following error message when trying to open
either the Transaction List or Transaction Statistics:
"Cannot open this folder because connection to the MSDTC service on 'My
Computer' failed."
Please help!
Thanks in advance,
Mervin WilliamsMervin Williams schrieb:
> I'm trying to install Microsoft SQL Server 2005 Developer Edition and each
> time I attempt to I get the error message:
> "Failed to install and configure assemblies C:\Program Files\Microsoft SQL
> Server\90\NotificationServices\9.0.242\Bin\microsoft.sqlserver.notificationservices.dll
> in the COM+ catalog. Error: -2146233087
> Error message: Unknown error 0x80131501
> Error description: MSDTC was unable to read its configuration information.
> (Exception from HRESULT: 0x8004D027)"
> Not only that, but in my Component Services->Distributed Transaction
> Coordinator section, I get the following error message when trying to open
> either the Transaction List or Transaction Statistics:
> "Cannot open this folder because connection to the MSDTC service on 'My
> Computer' failed."
>
Maybe MSDTC is not running. You can check this by going into cmd
and type "net start" <enter>. You should see a "distributed transaction
coordinator" service. If not maybe its starttype is "disabled" and you
should change it to "automatic".
hth
Gregor Stefka|||Actually, I have no "Distributed Transaction Coordinator" service in my
Services applet. Why is this and how do I install it?
Thanks in advance,
Mervin Williams
"Gregor Stefka" <stefka@.zuehlke-bieker.de> wrote in message
news:egCWZ7zkHHA.4876@.TK2MSFTNGP03.phx.gbl...
> Mervin Williams schrieb:
>> I'm trying to install Microsoft SQL Server 2005 Developer Edition and
>> each
>> time I attempt to I get the error message:
>> "Failed to install and configure assemblies C:\Program Files\Microsoft
>> SQL
>> Server\90\NotificationServices\9.0.242\Bin\microsoft.sqlserver.notificationservices.dll
>> in the COM+ catalog. Error: -2146233087
>> Error message: Unknown error 0x80131501
>> Error description: MSDTC was unable to read its configuration
>> information.
>> (Exception from HRESULT: 0x8004D027)"
>> Not only that, but in my Component Services->Distributed Transaction
>> Coordinator section, I get the following error message when trying to
>> open
>> either the Transaction List or Transaction Statistics:
>> "Cannot open this folder because connection to the MSDTC service on 'My
>> Computer' failed."
> Maybe MSDTC is not running. You can check this by going into cmd
> and type "net start" <enter>. You should see a "distributed transaction
> coordinator" service. If not maybe its starttype is "disabled" and you
> should change it to "automatic".
> hth
> Gregor Stefka|||Mervin Williams (mwilliams@.innovasolutions.net) writes:
> I'm trying to install Microsoft SQL Server 2005 Developer Edition and each
> time I attempt to I get the error message:
> "Failed to install and configure assemblies C:\Program Files\Microsoft SQL
>
Server\90\NotificationServices\9.0.242\Bin\microsoft.sqlserver.notifications
ervices.dll
> in the COM+ catalog. Error: -2146233087
Do you plan to work with Notification Services? Not that I want to
belittle it, but is not the most commonly used component of SQL Server.
So if you have no direct need of it, why not just skip installing it?
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

error installing sp2

Hello
Im trying to install sp2 on a win2k machine and i get:
Error running script: sp_vupgrade_replication(1)
all the time when its trying to finish the installation... sigh
how to fix that?
/LasseHave you got any read only databases or databases involved in log shipping ?
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Lasse Edsvik" <lasse@.nospam.com> wrote in message
news:uyudRJQAEHA.212@.TK2MSFTNGP12.phx.gbl...
> Hello
> Im trying to install sp2 on a win2k machine and i get:
> Error running script: sp_vupgrade_replication(1)
> all the time when its trying to finish the installation... sigh
> how to fix that?
> /Lasse
>sql

error installing sp2

Hello
Im trying to install sp2 on a win2k machine and i get:
Error running script: sp_vupgrade_replication(1)
all the time when its trying to finish the installation... sigh
how to fix that?
/LasseHave you got any read only databases or databases involved in log shipping ?
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Lasse Edsvik" <lasse@.nospam.com> wrote in message
news:uyudRJQAEHA.212@.TK2MSFTNGP12.phx.gbl...
> Hello
> Im trying to install sp2 on a win2k machine and i get:
> Error running script: sp_vupgrade_replication(1)
> all the time when its trying to finish the installation... sigh
> how to fix that?
> /Lasse
>

Error in the Stored Procedure

I am trying to swap two rows in a table .. I am stuck with this error since a long time.. can anyone guess where the problem is ? create procedure was working fine in query analyzer but when used it in the stored procedure. I am getting these .. can anyone help me out please ... Your help will be greatly appreciated.. UpdateRowsReorderUp is my storedprocedure ... and i am using MS Sql 2000 .. am I doing something really wrong which i'm not supposed to ???

Thanks friends..

Procedure 'UpdateRowsReorderUp' expects parameter '@.nextlowestsortID', which was not supplied.

CREATE PROCEDURE [dbo].[UpdateRowsReorderUp]

(

@.intsortID int,

@.nextlowestsortID int,

@.MemberID int

)

AS

Select @.nextlowestsortID=(Select Top 1 SortID from SelectedCredits where SortID<@.intsortID order by SortID DESC)

UPDATE SelectedCredits SET SortID= CASE

WHEN SortID = @.nextlowestsortID then @.intsortID

WHEN SortID = @.intsortID then @.nextlowestsortID ELSE SortID End

WHERE MemberID = @.MemberID

SELECT * FROM SelectedCredits WHERE MemberID= @.MemberID ORDER BY SortID

GO

**************

// this is my script on the page

void moveup(Object s, DataListCommandEventArgs e) {

objcmd= new SqlCommand("UpdateRowsReorderUp",objConn);

objcmd.CommandType = CommandType.StoredProcedure;

objcmd.Parameters.Add("@.intsortID",intsortID);

objcmd.Parameters.Add("@.MemberID",Session["MemberID"]);

objRdr= objcmd.ExecuteReader();

dlSelCredits.DataSource = objRdr;

dlSelCredits.DataBind();

objRdr.Close();

objConn.Close();

BindData();

}

You are missing the @.nextlowestsortid parameter in your code. Add it between the other two.
|||

Thanks for your reply . I'm storing a value in the @.nextlowestsortid using a SELECT statement.I am not assigning any value outside so that i can pass it into the parameter. for example @.intsortid i'm assiging intsortid through the code but what can i assign to this? Sorry to ask like this i am a newbie in this field..

Can i write the SELECT statement in different way so that there is no need add any parameter through the code ??

|||If the @.nextlowestsortid parameter is an internal parameter, remove itfrom the parameter list and declare it after the AS, like this:
DECLARE @.nextlowestsortid int
Then you stored procedure will only have two parameters that you supply, and the error will go away.
Sam
|||

Thank you very much Sam .. I am really grateful to you ..

You solved my problem .. that was the perfect solution ..

cheers mate

Error in MSSQL Manager

Using MSSQL 9.0.1399. And one time in hour get the error (see screenshot)
After that the summare tab dont't worked.
(http://eyfel.info/news/local/detail.htm?id=10209227@.eflArticle)
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 '6' 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.PopulateView()
at Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneListViewer.OnNavigateToSummaryView(ISummaryView view)
at Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneListViewer.InvokeItemDefaultAction(ISummaryItem item)
at Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.RightPaneListViewer.OnListViewMouseDoubleClick(Object sender, MouseEventArgs e)
at System.Windows.Forms.Control.OnMouseDoubleClick(MouseEventArgs e)
at System.Windows.Forms.ListView.WndProc(Message& m)
at Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.SummaryListView.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** 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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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.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.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
-
System.Web
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.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
-
Microsoft.VisualStudio
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 built by: RTM
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.dll
-
Microsoft.VisualStudio.Shell
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio.Shell/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.dll
-
Microsoft.VisualStudio.Shell.Interop.8.0
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop.8.0/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.8.0.dll
-
System.Drawing.Design
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing.Design/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.Design.dll
-
Microsoft.VisualStudio.Designer.Interfaces
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Designer.Interfaces/1.0.5000.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Designer.Interfaces.dll
-
System.Design
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Design/2.0.0.0__b03f5f7f11d50a3a/System.Design.dll
-
Microsoft.VisualStudio.DataTools.Interop
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.VisualStudio.DataTools.Interop.DLL
-
Microsoft.VisualStudio.Data.Interop
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.VisualStudio.Data.Interop.DLL
-
Microsoft.VisualStudio.Data
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.VisualStudio.Data.DLL
-
Microsoft.VisualStudio.DataTools
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.VisualStudio.DataTools.DLL
-
Microsoft.Data.ConnectionUI.Dialog
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.Data.ConnectionUI.Dialog.DLL
-
Microsoft.Data.ConnectionUI
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.Data.ConnectionUI.DLL
-
System.Data.OracleClient
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data.OracleClient/2.0.0.0__b77a5c561934e089/System.Data.OracleClient.dll
-
System.Security
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Security/2.0.0.0__b03f5f7f11d50a3a/System.Security.dll
-
Microsoft.VisualStudio.Debugger.Interop
Assembly Version: 8.0.1.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Debugger.Interop/8.0.1.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Debugger.Interop.dll
-
Microsoft.VisualStudio.vspSmoEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1314.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.VisualStudio.vspSmoEnum.DLL
-
Microsoft.VisualStudio.vspConnectionInfo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1314.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.VisualStudio.vspConnectionInfo.DLL
-
Microsoft.VisualStudio.vspSqlEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1314.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.VisualStudio.vspSqlEnum.DLL
-
Microsoft.VisualStudio.vspBatchParser
Assembly Version: 9.0.242.0
Win32 Version: 2005.090.1314.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.VisualStudio.vspBatchParser.DLL
-
Microsoft.VisualStudio.Design
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio.Design/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Design.dll
-
Microsoft.VisualStudio.Shell.Design
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio.Shell.Design/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Design.dll
-
Microsoft.VisualStudio.vspGridControl
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1314.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.VisualStudio.vspGridControl.DLL
-
CustomMarshalers
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/CustomMarshalers/2.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.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.

I am having the same isssue. The summary page stops working after this. You have to close Management Studio down and reopen it to get the summary page to work again.

|||

See this post

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

Error in Management Studio

Have installed SQL 2008 db engine and client tools. Each time I attempt to return a resultset, I receive the following error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

This error occurs on any data access, such as:

select * from sys.columns

Does anyone know what might be going on?

And if you switch results to text instead of the grid, does everything work?|||

No, I receive the same error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

|||Nope. Do you have more than one machine to do this on, or could you re-install SSMS?|||

Had same exact error message. Tried uninstalling and reinstalling just the client tools with no affect. Then completely uninstalled SQL 2008 (had both June and July instances) and reinstalled all of July. This "fixed" the problem. This is a frustrating one, I'd already submitted it as a bug earlier today. Perhaps it is related to partial uninstalls of just the client tools, since I had to uninstall the June tools to install the July ones the first time around. But doing a total remove of all of SQL 2008 seemed to do the trick.

Have Fun!

Ron

Error in Management Studio

Have installed SQL 2008 db engine and client tools. Each time I attempt to return a resultset, I receive the following error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

This error occurs on any data access, such as:

select * from sys.columns

Does anyone know what might be going on?

And if you switch results to text instead of the grid, does everything work?|||

No, I receive the same error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

|||Nope. Do you have more than one machine to do this on, or could you re-install SSMS?|||

Had same exact error message. Tried uninstalling and reinstalling just the client tools with no affect. Then completely uninstalled SQL 2008 (had both June and July instances) and reinstalled all of July. This "fixed" the problem. This is a frustrating one, I'd already submitted it as a bug earlier today. Perhaps it is related to partial uninstalls of just the client tools, since I had to uninstall the June tools to install the July ones the first time around. But doing a total remove of all of SQL 2008 seemed to do the trick.

Have Fun!

Ron

Error in Management Studio

Have installed SQL 2008 db engine and client tools. Each time I attempt to return a resultset, I receive the following error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

This error occurs on any data access, such as:

select * from sys.columns

Does anyone know what might be going on?

And if you switch results to text instead of the grid, does everything work?

|||

No, I receive the same error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

|||Nope. Do you have more than one machine to do this on, or could you re-install SSMS?

|||

Had same exact error message. Tried uninstalling and reinstalling just the client tools with no affect. Then completely uninstalled SQL 2008 (had both June and July instances) and reinstalled all of July. This "fixed" the problem. This is a frustrating one, I'd already submitted it as a bug earlier today. Perhaps it is related to partial uninstalls of just the client tools, since I had to uninstall the June tools to install the July ones the first time around. But doing a total remove of all of SQL 2008 seemed to do the trick.

Have Fun!

Ron

Error in Management Studio

Have installed SQL 2008 db engine and client tools. Each time I attempt to return a resultset, I receive the following error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

This error occurs on any data access, such as:

select * from sys.columns

Does anyone know what might be going on?

And if you switch results to text instead of the grid, does everything work?|||

No, I receive the same error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

|||Nope. Do you have more than one machine to do this on, or could you re-install SSMS?|||

Had same exact error message. Tried uninstalling and reinstalling just the client tools with no affect. Then completely uninstalled SQL 2008 (had both June and July instances) and reinstalled all of July. This "fixed" the problem. This is a frustrating one, I'd already submitted it as a bug earlier today. Perhaps it is related to partial uninstalls of just the client tools, since I had to uninstall the June tools to install the July ones the first time around. But doing a total remove of all of SQL 2008 seemed to do the trick.

Have Fun!

Ron

Error in Management Studio

Have installed SQL 2008 db engine and client tools. Each time I attempt to return a resultset, I receive the following error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

This error occurs on any data access, such as:

select * from sys.columns

Does anyone know what might be going on?

And if you switch results to text instead of the grid, does everything work?|||

No, I receive the same error:

An error occurred while executing batch. Error message is: Method not found: 'Void Microsoft.SqlServer.Management.UI.Grid.ColumnInfo.set_ServerVersion(Int32)'.

|||Nope. Do you have more than one machine to do this on, or could you re-install SSMS?|||

Had same exact error message. Tried uninstalling and reinstalling just the client tools with no affect. Then completely uninstalled SQL 2008 (had both June and July instances) and reinstalled all of July. This "fixed" the problem. This is a frustrating one, I'd already submitted it as a bug earlier today. Perhaps it is related to partial uninstalls of just the client tools, since I had to uninstall the June tools to install the July ones the first time around. But doing a total remove of all of SQL 2008 seemed to do the trick.

Have Fun!

Ron

Error in installation SQL 2005 SP2 on 64 Bit Cluster.

I receive the below mentioned error message each time I try to install SP2 on SQL 2005 64 Bit Cluster:

Using PrevRegRootPath: Software\Microsoft\Microsoft SQL Server\MSSQL.2

GetServiceUserGroup failed for PLMCWSM01, 5

Error Code: 0x800706fd (1789)

Windows Error Text: The trust relationship between this workstation and the primary domain failed.

Source File Name: sqlca\sqlcax.cpp

Compiler Timestamp: Fri Feb 9 22:35:02 2007

Function Name: SetInstanceProperty

Source Line Number: 1223

MSI (s) (78!08) [01:05:21:864]: Transforming table Error.

MSI (s) (78!08) [01:05:21:989]: Transforming table Error.

MSI (s) (78!08) [01:05:21:989]: Note: 1: 2262 2: Error 3: -2147287038

MSI (s) (78!08) [01:05:21:989]: Product: Microsoft SQL Server 2005 (64-bit) -- Error 29528. The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.

Error 29528. The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.

Any Help on this would be highly appreciated.

Thanks

Anurag

Hi Anurag,

did you check this workarount: http://support.microsoft.com/kb/925976/en-us?

CU

tosc

error in execution time

hi all

i am working in sql reporting 2000.

In my report i have included field to display the execution time.

That time is not changing if i am running the report again & again.

Its only showing the time at which report was run first time in current Internet Explorer window.

how can i get current time in report?

plz help me.

In your text box, put this:

="Report Created On: " & Globals.ExecutionTime

|||

Thanks for reply.

I am already using Globals.ExecutionTime to display execution time in my report .

But if i am rexecuting the report then also time is not getting updated.

If i am running other report & after that report if i am running this report then also its showing the last time at which the report was executed.

So what is the solutin for this?

Plz help me

|||The reports might have been cached on the server if you specifically have set it to keep the last run report. So it may not be running the report, but instead getting the last cached report. I haven't tinkered with the settings, but it's an idea. You might want to check the report properties and then the execution tab..

Error in calculating Twelve Months to date using Time Intelligence

Hi,

I have used Time intelligence of AS2005 to calculate YTD and Twelve Months to date. YTD works pretty well, but there is an error in parsing the code that AS2005 generated when it created time intelligence for calculating Twelve Months to date.

The time dimension contains 2 hierarchies, Full Year (QTR- Month) and YTD hierarchy(Year - Qtr - Month) . Here is the code it generated for 12 months to date.

Scope( { [Measures].[Quote Count] } )

( [Total Year FY].[YTD Hierarchy Total Year FY Calculations 2].[Twelve Months to Date],

[Total Year FY].[YTD Hierarchy].[YTD Hierarchy].Members) =

Aggregate(

{ [Total Year FY].[YTD Hierarchy Total Year FY Calculations 2].DefaultMember } *

{ ParallelPeriod(

[Total Year FY].[YTD Hierarchy].[?MonthLevelUniqueName], 11,

[Total Year FY].[YTD Hierarchy].CurrentMember

) : [Total Year FY].[YTD Hierarchy].CurrentMember } )

End Scope

This is the error message

MdxScript(ApplicantHORT) (130, 8) The level '[YTD Hierarchy]' object was not found in the cube when the string, [Total Year FY].[YTD Hierarchy].[YTD Hierarchy], was parsed.

Any ideas how to fix this problem?

Thanks

Srinivas

Hi Srinivas,

If you refer to this SQL Server Magazine article, the MDX Script generated for Time Intelligence conforms to certain patterns; so I suspect that your [YTD Hierarchy] doesn't quite fit:

http://www.sqlmag.com/Articles/Print.cfm?ArticleID=46157

>>
Analysis Services 2005 Brings You Automated Time Intelligence
The Business Intelligence Wizard makes time analysis a snap
Mosha Pasumansky,
Robert Zare
InstantDoc #46157
June 2005

...

As Listing 3 shows, best practice uses attribute hierarchies on the left side of the assignment. In Analysis Services 2005, the cube space is defined entirely by attributes, so the space to which calculations apply is best described by the attribute hierarchies contained therein. Conversely, specifying the scope for user-defined hierarchies can result in inadvertently over-restricting the calculation scope. The Year to Date calculation illustrates this best practice through the use of the Fiscal Year attribute hierarchy, which excludes the All member (where the calculation doesn't apply). This approach includes all other attributes in the hierarchy, regardless of whether or not they are All members, which is precisely what we want.

Next, note that the right side of the assignment uses multilevel user hierarchies (rather than attribute hierarchies), which lets you use hierarchy-friendly MDX functions such as ParallelPeriod and PeriodsToDate.

...

( [Date].[Fiscal Date Calculations].[Twelve Month Moving Average],
[Date].[Month Name].[Month Name].Members ) =
Avg(
{
ParallelPeriod(
[Date].[Fiscal].[Month],
11,
[Date].[Fiscal].CurrentMember
) : [Date].[Fiscal].CurrentMember
},
[Date].[Fiscal Date Calculations].DefaultMember
) ;
>>

If you compare the above listing with your MDX Script, then [Total Year FY].[YTD Hierarchy].[YTD Hierarchy].Members should be members of the Month level of a Month attribute hierarchy, which should be incorporated in your user-defined [YTD Hierarchy]. Similarly, [Total Year FY].[YTD Hierarchy].[?MonthLevelUniqueName] should be the Month level of [YTD Hierarchy].

|||

Thanks Deepak,

It worked when i changed

[Total Year FY].[YTD Hierarchy].[YTD Hierarchy].Members to

[Total Year FY].[Months].[Months].Members and

[Total Year FY].[YTD Hierarchy].[?MonthLevelUniqueName] to

[Total Year FY].[YTD Hierarchy].[Months]

your post was really helpful.

Error Importing SSIS Package

I can't import a package from the SSIS to the file system of my SQL Server Management Studio. Every time i've tried the following message appears. What should i do to correct this problem? Any ideas?

===================================

Invalid access to memory location. (Exception from HRESULT: 0x800703E6) (Microsoft.SqlServer.ManagedDTS)

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToDtsServer(Package pPackage, IDTSEvents pEvents, String sPackagePath, String sServerName)
at Microsoft.SqlServer.Dts.ObjectExplorerUI.ImportPackageAsAction.ImportPackage(ImportPackageAsForm dlg)

Similar problem here:

I cannot store DTSX-Packages from local filesystem on the ISS-MSDB, if I try I get the same errormessage as you.

Regards,

Jan

|||

I had the same problem and the fix was to run

Regsvr32 msxml3.dll
Regsvr32 msxml6.dll

//Niclas

|||Thanks Niclas. This worked for me too.

Error Importing SSIS Package

I can't import a package from the SSIS to the file system of my SQL Server Management Studio. Every time i've tried the following message appears. What should i do to correct this problem? Any ideas?

===================================

Invalid access to memory location. (Exception from HRESULT: 0x800703E6) (Microsoft.SqlServer.ManagedDTS)

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToDtsServer(Package pPackage, IDTSEvents pEvents, String sPackagePath, String sServerName)
at Microsoft.SqlServer.Dts.ObjectExplorerUI.ImportPackageAsAction.ImportPackage(ImportPackageAsForm dlg)

Similar problem here:

I cannot store DTSX-Packages from local filesystem on the ISS-MSDB, if I try I get the same errormessage as you.

Regards,

Jan

|||

I had the same problem and the fix was to run

Regsvr32 msxml3.dll
Regsvr32 msxml6.dll

//Niclas

|||Thanks Niclas. This worked for me too.

Error Importing SSIS Package

I can't import a package from the SSIS to the file system of my SQL Server Management Studio. Every time i've tried the following message appears. What should i do to correct this problem? Any ideas?

===================================

Invalid access to memory location. (Exception from HRESULT: 0x800703E6) (Microsoft.SqlServer.ManagedDTS)

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToDtsServer(Package pPackage, IDTSEvents pEvents, String sPackagePath, String sServerName)
at Microsoft.SqlServer.Dts.ObjectExplorerUI.ImportPackageAsAction.ImportPackage(ImportPackageAsForm dlg)

Similar problem here:

I cannot store DTSX-Packages from local filesystem on the ISS-MSDB, if I try I get the same errormessage as you.

Regards,

Jan

|||

I had the same problem and the fix was to run

Regsvr32 msxml3.dll
Regsvr32 msxml6.dll

//Niclas

|||Thanks Niclas. This worked for me too.

Error Importing SSIS Package

I can't import a package from the SSIS to the file system of my SQL Server Management Studio. Every time i've tried the following message appears. What should i do to correct this problem? Any ideas?

===================================

Invalid access to memory location. (Exception from HRESULT: 0x800703E6) (Microsoft.SqlServer.ManagedDTS)

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToDtsServer(Package pPackage, IDTSEvents pEvents, String sPackagePath, String sServerName)
at Microsoft.SqlServer.Dts.ObjectExplorerUI.ImportPackageAsAction.ImportPackage(ImportPackageAsForm dlg)

Similar problem here:

I cannot store DTSX-Packages from local filesystem on the ISS-MSDB, if I try I get the same errormessage as you.

Regards,

Jan

|||

I had the same problem and the fix was to run

Regsvr32 msxml3.dll
Regsvr32 msxml6.dll

//Niclas

|||Thanks Niclas. This worked for me too.

Error if table has not created yet at the first time

Hello,

I have created a package that check if a table exist otherwise it drop it, then it creates a new one (both with SSIS execute SQL task).

Then a Flow task run some transformation SSIS to load the table just created.

The problem is that when I run the package an error occur telling me that the table does not exist (if runs for the first time and in this case the table has not created yet).

How can I run a package that create a table and then Load it.

Thank

You need to set the DelayValidation property to True on the Data Flow and the Execute SQL tasks.

error handling and transactions - speed question

I've been very carefully studying
http://www.sommarskog.se/error-handling-II.html recently. I went through it
some time ago before I was very familiar with working in SQL and it was all
sort of mysterious to me. Now I'm finding it to be very helpful.
Here's my issue right now: I have a former coworker who has been wroking in
sql 2k for several years now (we tend to disagree often on programming
techniques). When I asked him today how extensively he implements the sorts
of strategies detailed in Erland's articles he said that he rarely does any
of this. I was surprised. He said that occasionally and with great restraint
he'll use a begin/commit structure. He says that if you have a system with
many users then you have to worry about the system getting bogged down in
transactions. I mentioned the classic example of transferring money from a
savings account to a checking acount and what if something fails between the
2 update statements and he said that if you have a banking system where
thousands of people are hammering away at the system all day long then using
transactiosn in such a situation would be detrimental to performance. He
thinks that in theory using begin/commmit and @.@.error is very good but in
it's not very practical in the real world. I'm thinking that would be true
if you didn't design your error handling carefully as Erland outlines. I
would very much appreciate some feedback from the experts on this topic
because in my opinion, not handling errors at all is a bad idea. Is my
friend way off, somewhere in the middle or right on target?
Thanks,
KeithLet me guess, he's the type of guy who takes a chance when bicycling into a
crossing, and don't
break in order to not loose speed; hoping that no car will intersect?
Sure, if your customer (MD, president, or whatever) agrees that some crap in
the database is OK, you
don't have to worry (as much) about transaction handling. But make sure it i
s a conscious decision,
taken higher up in the organization and make sure you have this in writing (
or it will be your ass).
Another way of looking at a DBMS is as a state machine. Each modification ta
kes you from one state
to another state. With transactions, you can protect yourself from disallowe
d states.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Keith G Hicks" <krh@.comcast.net> wrote in message news:ugsl8asTGHA.1576@.tk2msftngp13.phx.g
bl...
> I've been very carefully studying
> http://www.sommarskog.se/error-handling-II.html recently. I went through i
t
> some time ago before I was very familiar with working in SQL and it was al
l
> sort of mysterious to me. Now I'm finding it to be very helpful.
> Here's my issue right now: I have a former coworker who has been wroking i
n
> sql 2k for several years now (we tend to disagree often on programming
> techniques). When I asked him today how extensively he implements the sort
s
> of strategies detailed in Erland's articles he said that he rarely does an
y
> of this. I was surprised. He said that occasionally and with great restrai
nt
> he'll use a begin/commit structure. He says that if you have a system with
> many users then you have to worry about the system getting bogged down in
> transactions. I mentioned the classic example of transferring money from a
> savings account to a checking acount and what if something fails between t
he
> 2 update statements and he said that if you have a banking system where
> thousands of people are hammering away at the system all day long then usi
ng
> transactiosn in such a situation would be detrimental to performance. He
> thinks that in theory using begin/commmit and @.@.error is very good but in
> it's not very practical in the real world. I'm thinking that would be true
> if you didn't design your error handling carefully as Erland outlines. I
> would very much appreciate some feedback from the experts on this topic
> because in my opinion, not handling errors at all is a bad idea. Is my
> friend way off, somewhere in the middle or right on target?
> Thanks,
> Keith
>|||geee. and he's a db programmer?
if he doesn't use begin/commit statments in multi statement stored procs he
eventually ends up with much bigger number of transactions than with these
statements. each statement is auto committed by default, unless he uses
"implicit transactions on" setting..
http://msdn2.microsoft.com/en-us/library/ms175523.aspx
Peter|||I completely agree with Tibor... and have NEVER written any serious
application without doing proper error handling... If the data is not
important - that's one thing... but if it is used to run your business, then
you have an obligation to make sure things are good...Yes, depending on the
work you are doing, transactions might cause some locking - that is the
INTENDED way they work... They prevent one persons work from overwriting and
interfering with another..
To presumptively say that trans cause to many problems is disappointing and
lazy.
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"unknown" wrote:

>|||"Slow and right" beats "fast and wrong" two out of three times...
because there's always someone who doesn't care about the right answer, just
give me any answer fast.
I, for one, strongly agree with the other comments here, that good logical
transactional control and error handling is far more important than shaving
off a few milliseconds at the risk of a wrong answer.
btw, when I've dealt with folks who didn't see much value in certain SQL
technologies it was because they didn't really understand the technology -
like the data modeler who said that query path to the data didn't matter in
a database design, and sure enough, he couldn't write a basic query.
-Paul Nielsen
SQL Server MVP
"Keith G Hicks" <krh@.comcast.net> wrote in message
news:ugsl8asTGHA.1576@.tk2msftngp13.phx.gbl...
> I've been very carefully studying
> http://www.sommarskog.se/error-handling-II.html recently. I went through
> it
> some time ago before I was very familiar with working in SQL and it was
> all
> sort of mysterious to me. Now I'm finding it to be very helpful.
> Here's my issue right now: I have a former coworker who has been wroking
> in
> sql 2k for several years now (we tend to disagree often on programming
> techniques). When I asked him today how extensively he implements the
> sorts
> of strategies detailed in Erland's articles he said that he rarely does
> any
> of this. I was surprised. He said that occasionally and with great
> restraint
> he'll use a begin/commit structure. He says that if you have a system with
> many users then you have to worry about the system getting bogged down in
> transactions. I mentioned the classic example of transferring money from a
> savings account to a checking acount and what if something fails between
> the
> 2 update statements and he said that if you have a banking system where
> thousands of people are hammering away at the system all day long then
> using
> transactiosn in such a situation would be detrimental to performance. He
> thinks that in theory using begin/commmit and @.@.error is very good but in
> it's not very practical in the real world. I'm thinking that would be true
> if you didn't design your error handling carefully as Erland outlines. I
> would very much appreciate some feedback from the experts on this topic
> because in my opinion, not handling errors at all is a bad idea. Is my
> friend way off, somewhere in the middle or right on target?
> Thanks,
> Keith
>