﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Discuss Content Posted by Amit Jethva / Article Discussions / Article Discussions by Author </title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Thu, 24 May 2012 11:52:24 GMT</lastBuildDate><ttl>20</ttl><item><title>DATABASE / TABLE SIZE ESTIMATER</title><link>http://www.sqlservercentral.com/Forums/Topic405317-171-1.aspx</link><description>Comments posted to this topic are about the item [B]&lt;A HREF="/scripts/Miscellaneous/31062/"&gt;DATABASE / TABLE SIZE ESTIMATER&lt;/A&gt;[/B]</description><pubDate>Mon, 01 Oct 2007 17:33:02 GMT</pubDate><dc:creator>Amit Jethva</dc:creator></item><item><title>Monthly SQL Server Agent Jobs report</title><link>http://www.sqlservercentral.com/Forums/Topic410729-171-1.aspx</link><description>Comments posted to this topic are about the item [B]&lt;A HREF="/scripts/Miscellaneous/31014/"&gt;Monthly SQL Server Agent Jobs report&lt;/A&gt;[/B]</description><pubDate>Mon, 15 Oct 2007 02:47:48 GMT</pubDate><dc:creator>Amit Jethva</dc:creator></item><item><title>Capturing The Error Description In A Stored Procedure</title><link>http://www.sqlservercentral.com/Forums/Topic112659-171-1.aspx</link><description>Comments posted to this topic are about the content posted at &lt;A HREF=http://www.sqlservercentral.com/columnists/ajethva/capturingtheerrordescriptioninastoredprocedure.asp&gt;http://www.sqlservercentral.</description><pubDate>Thu, 22 Apr 2004 14:48:00 GMT</pubDate><dc:creator>Amit Jethva</dc:creator></item><item><title>Question Regarding SQL Update Assistant 2005</title><link>http://www.sqlservercentral.com/Forums/Topic582129-171-1.aspx</link><description>Goal: To upgrage the SQL 2000 DB to 2005 DB.Tools Used: SQL Server Upgrade Assistance 2005&amp;gt; I was trying to run the SQL Server Upgrade Assistance to convert the SQL Server 7.0 database to SQL Server 2005. Soon as I run the SSUA on the Server 7.0 machine, it prompts following ERROR:================================================================================================================================================See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************System.IO.FileLoadException: Could not load file or assembly 'Microsoft.SqlServer.SString, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)File name: 'Microsoft.SqlServer.SString, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' ---&amp;gt; System.Security.SecurityException: Strong name validation failed. (Exception from HRESULT: 0x8013141A)The Zone of the assembly that failed was:MyComputer   at a.d()   at a.e(Object A_0, EventArgs A_1)   at System.Windows.Forms.Control.OnClick(EventArgs e)   at System.Windows.Forms.Button.OnClick(EventArgs e)   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)   at System.Windows.Forms.Control.WmMouseUp(Message&amp; m, MouseButtons button, Int32 clicks)   at System.Windows.Forms.Control.WndProc(Message&amp; m)   at System.Windows.Forms.ButtonBase.WndProc(Message&amp; m)   at System.Windows.Forms.Button.WndProc(Message&amp; m)   at System.Windows.Forms.Control.ControlNative&amp;#119;indow.OnMessage(Message&amp; m)   at System.Windows.Forms.Control.ControlNative&amp;#119;indow.WndProc(Message&amp; m)   at System.Windows.Forms.Native&amp;#119;indow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)************** Loaded Assemblies **************mscorlib    Assembly Version: 2.0.0.0    Win32 Version: 2.0.50727.832 (QFE.050727-8300)    CodeBase: file:///C:/WINNT/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll----------------------------------------SSUA    Assembly Version: 1.0.0.1    Win32 Version: 1.0.0.1    CodeBase: file:///C:/Program%20Files/Scalability%20Experts/SSUA/SSUA.exe----------------------------------------System.Windows.Forms    Assembly Version: 2.0.0.0    Win32 Version: 2.0.50727.832 (QFE.050727-8300)    CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll----------------------------------------System    Assembly Version: 2.0.0.0    Win32 Version: 2.0.50727.832 (QFE.050727-8300)    CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll----------------------------------------System.Drawing    Assembly Version: 2.0.0.0    Win32 Version: 2.0.50727.832 (QFE.050727-8300)    CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll----------------------------------------System.Xml    Assembly Version: 2.0.0.0    Win32 Version: 2.0.50727.832 (QFE.050727-8300)    CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll----------------------------------------Accessibility    Assembly Version: 2.0.0.0    Win32 Version: 2.0.50727.42 (RTM.050727-4200)    CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll----------------------------------------************** JIT Debugging **************To enable just-in-time (JIT) debugging, the .config file for thisapplication or computer (machine.config) must have thejitDebugging value set in the system.windows.forms section.The application must also be compiled with debuggingenabled.For example:       When JIT debugging is enabled, any unhandled exceptionwill be sent to the JIT debugger registered on the computerrather than be handled by this dialog box.=========================================================================</description><pubDate>Tue, 07 Oct 2008 13:17:53 GMT</pubDate><dc:creator>vaishu_arch</dc:creator></item><item><title>RE:</title><link>http://www.sqlservercentral.com/Forums/Topic240436-171-1.aspx</link><description>&lt;P&gt;getting the error description in your sp is very easy: you know the errorcode and the errmessage is in the master.dbo.sysmessages. just wrote myself an UDF to get the errmessage for my log.&lt;/P&gt;&lt;P&gt;problem: you have to manage the security (access to master...) but as most of our really heavy batches are running with highlevel permissions..&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;cheers&lt;/P&gt;&lt;P&gt;moritz&lt;/P&gt;</description><pubDate>Tue, 29 Nov 2005 10:57:00 GMT</pubDate><dc:creator>Moritz Braun</dc:creator></item></channel></rss>
