CFquery crashes SQL server

We have just run into an instance where any query to a
SQL2000 db locks up the SQL server (by consuming all the
resources), which eventually causes the server to crash.
Our web host (intermedia.net) told us that the problem is
selecting a field designated as nvarchar(1) is the cause of the
problem.
Since we use this same select on identical databases at the
more than 100+ sites we host at intermedia.net, and have no
problems with those sites, we think there is a problem at
intermedia.net. Of course, they say no, it is a program problem.
But I wrote a 3 line test program that simply tries to open
the database with a select *, and it still crashes the server.
Any suggestions about what settings in CF or SQL2000 that
would cause all DB queries to lock up SQL?
Thanks for any help

> wrote a 3 line test program that simply tries to open
the database
> with a select *, and it still crashes the server.
Have you tried running this simple query in Query Analyzer
looked at the results?
Is it possible for you to write a simple test script that
does not bring down the
sql server?
Perhaps this may simply be a driver issue?
Good luck!

Similar Messages

SQL Server Compact 3.5 Merge Replication With SQL Server 2012 - Causing IIS App Pool to Crash

Hi, I may be the only person in the world doing this but I wanted to give this information to anyone else who may follow this path in the future, and hopefully avoid a headache, or at least a paid support call to Microsoft.
My original scenario was we had a SQL Server 2008 Server using Merge Replication through and IIS (web server) to several Windows Mobile 6 devices. This has worked fairly well for a few years.
Recently we upgraded our SQL server to version 2012 SP 1. After moving the database over to the new server, and re-setting the merge replication stuff, we couldn't get merge replication to work on the Windows Mobile 6 handheld devices. The replication
would appear to start, and then we would get a message saying that the device could not get to the web site. The message on the handheld device was this:
"The IIS service is not available."
After doing some more research, we found that the start of the replication process was causing the Thread Pool that was running the SQLCESA35.dll to crash.
The SQLCESALOG.txt file had this information:
Date Time == SQLCESA Version ==> 3.5.8088.0
Date Time Hr=80004005 ERR:Couldn't find existing RSCB 1
After 2 days of trying to figure out the issue on our own, we gave in and called for paid Microsoft support. They eventually found a known issue where a cumulative update was able to fix the problem.
We installed the update on the IIS server and everything ran smoothly again.
FIX: Merge replication fails when you use SQL Server Compact to perform a merge replication that synchronizes changes with a publisher in SQL Server 2012
http://support.microsoft.com/kb/2845550
Seth O'Neal

Hi sonealtx,
Glad to hear that the issue is resolved. Thanks for your sharing, other community members could benefit from your solution.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

ODBC function SQLDriverConnect() crashes with SQL Server 2008 R2

When calling the SQLDriverConnect() function from a 64-bit process and selecting a system DSN with a SQL Server Native Client 10.0 ODBC driver with SQL Server 2008 R2 SP3, then this call crashes here:
    sqlncli10.dll!SNIMemRegion::Pop() + 0x77 bytes
    sqlncli10.dll!SNIPacketAllocateEx2() + 0xa8 bytes
    sqlncli10.dll!Np::ReadSync() + 0x7e bytes
    sqlncli10.dll!Ssl::HandshakeReadToken() - 0x1b bytes
    user32.dll!InternalDialogBox() + 0x132 bytes
    user32.dll!DialogBoxIndirectParamAorW() + 0x56 bytes
    user32.dll!DialogBoxParamW() + 0x85 bytes
    sqlncli10.dll!SQLDriverConnectW() + 0x34f23 bytes
    odbc32.dll!SQLInternalDriverConnectW() + 0x17c bytes
    odbc32.dll!SQLDriverConnectW() + 0xa15b bytes
Am I calling SQLDriverConnect() correctly (see below)? Or is this a bug in the 64-bit version of the ODBC driver?
In the 32-bit version, everything works fine.
Here is a test program:
int _tmain(int argc, _TCHAR* argv[])
SQLHENV hEnv = NULL;
SQLHDBC hDbc = NULL;
SQLRETURN ret = SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, &hEnv);
assert(ret == SQL_SUCCESS || ret == SQL_SUCCESS_WITH_INFO);
ret = SQLSetEnvAttr(hEnv, SQL_ATTR_ODBC_VERSION, (SQLPOINTER) SQL_OV_ODBC3, 0);
if (ret != SQL_SUCCESS && ret != SQL_SUCCESS_WITH_INFO)
fprintf(stderr, "SQLSetEnvAttr failed\r\n");
return EXIT_FAILURE;
ret = SQLAllocHandle(SQL_HANDLE_DBC, hEnv, &hDbc);
assert(ret == SQL_SUCCESS || ret == SQL_SUCCESS_WITH_INFO);
SQLTCHAR szConnection[2048];
SQLSMALLINT cbChars;
ret = SQLDriverConnect(hDbc, ::GetDesktopWindow(), (SQLTCHAR*) _T(""), SQL_NTS,
szConnection, _countof(szConnection)-1, &cbChars, SQL_DRIVER_PROMPT);
if (ret != SQL_SUCCESS && ret != SQL_SUCCESS_WITH_INFO && ret != SQL_NO_DATA)
fprintf(stderr, "SQLDriverConnect failed\r\n");
return EXIT_FAILURE;
else
fprintf(stdout, "Success\r\n");
return 0;
The stdafx.h contains the following includes:
#include "targetver.h"
#include <stdio.h>
#include <tchar.h>
#include <Windows.h>
#include <sql.h>
#include <sqlext.h>
#include <assert.h>
Steps to reproduce the crash: compile program with Visual Studio 2010 as 64-bit console application; run it and select a 64-bit SQL Server DSN.
If the crash does not occur, try using the "AllocationPreference" registry entry set to 0x100000 (see https://msdn.microsoft.com/en-us/library/windows/hardware/Dn613975%28v=vs.85%29.aspx for details); don't forget to reboot Windows. This registry
helps to find 64-bit portability issues.

Hi T.holt,
Personally, I don’t believe SQL 2008 R2 with ADMT 3.2 is supported. From the guidelines of install the Active Directory Migration Tool (ADMT), ADMT v3.2 requires a preconfigured instance of SQL Server for its underlying data store. We
should use SQL Server Express and install ADMT v3.2 on a member server. ADMT installation enforces the following service pack requirements:
• SQL Server 2005 Express must be installed with Service Pack 3 (SP3) or later.
• SQL Server 2008 Express must be installed with Service Pack 1 (SP1) or later.
If you use full versions of SQL Server 2005 or SQL Server 2008. In this case, you need to install and run the ADMT console on a remote computer, and you can run multiple ADMT consoles on different remote computers. If
you use a full version of SQL Server, ADMT installation does not enforce any service pack requirements.
For more information about installing ADMT in the target domain, you can review the following article.http://technet.microsoft.com/en-us/library/cc974370(v=ws.10).aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Windows 8 and IE 10 crashed after printing from Report Manager SQL server 2008 / 2008 R2

We have a problem with Windows 8 in combination with IE 10 and printing reports.
When we print a report from the Report Manager 'http://<servername>/reports' the browser crashed after a print.
Sometimes before printing and somthimes after printing or when you close the browser.
Al other operating systems like XP, Vista, Windows 7 with different IE versions have no problem.
I tried the report manager from SQL Server 2008 and SQL Server 2008 R2.
The same error occured when printing from our Internet application and the reportviewer.
(ASP application written in Visual Studio 2010 and reportviewer version 10.)
The event log shows two different messages.
Faulting application name: IEXPLORE.EXE, version: 10.0.9200.16453, time stamp: 0x509b0dfb
Faulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505aaa82
Exception code: 0xc0000005
Fault offset: 0x00061252
Faulting process id: 0x780
Faulting application start time: 0x01ce03a294f7d1d5
Faulting application path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: d4a72486-6f96-11e2-be6e-10604b6a74ed
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: IEXPLORE.EXE, version: 10.0.9200.16384, time stamp: 0x50107ee0
Faulting module name: rsclientprint.dll, version: 2009.100.1600.1, time stamp: 0x4bb67a74
Exception code: 0xc0000005
Fault offset: 0x00017e7a
Faulting process id: 0x9c8
Faulting application start time: 0x01ce02f35c70ab85
Faulting application path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
Faulting module path: C:\Windows\Downloaded Program Files\rsclientprint.dll
Report Id: a13fccc6-6ee6-11e2-be67-10604b6a74ed
Faulting package full name:
Faulting package-relative application ID:
Is there a fix for this problem?

Dear Mike Yin,
Thank you for your response. Your answer was the
reason for finding the real problem.
In december 2010 a SQL Server 2008 fix was the cause. I don't remember exactly the problem, but we changed the RSCLIENTPrint-x86.cab file. But instead to use the version of SQL Server 2008 we used the version of SQL Server 2008
R2 (10.50.1600.1). This worked until
Windows 8 (Internet Explorer crashed when printing).
We fixed this problem by using the RSClientPrint-x86.cab file from SQL server 2008 (10.0.5500.0).
But we now get the known problem that the
activeX always must be installed again.
The reason for this is that the version of
the SQL Server (10.0.5512.0)
and the rsclientprint.dll (10.0.5500.0) is different. SQL Server is newer (caused
by a security patch (KB2716436)).
Do you know when this problem will be resolved
by Microsoft?
Work arrounds
I've also tried to install the RSClientprint.dll
every time automatically (without user interaction).
But this will be delayed the printing for more
than 4 seconds. This
is very annoying.
Another workaround is to generate a PDF and print the PDF. But this is also
a lot slower.
Uninstall the security patch. but I don't know the security risk.

SQL Server 2014 Express Management Studion crash

Hello!
After clean install new management stuidio 2014 I tried to import setting about registered sql servers from 2012.
He-he! I did not read docs and did not know that it is not working. But exception, wtf?
Summary my IDE crash every time when I try to expand Registered Servers. Reinstall, repair SQL Server 2014 is not healing problem.
Faulting application name: Ssms.exe, version: 2014.120.2000.8, time stamp: 0x5306c06d
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54504ade
Exception code: 0xc000041d
Fault offset: 0x00014598
Faulting process id: 0x494
Faulting application start time: 0x01d0099222d89631
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio\Ssms.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: 68e6a650-7585-11e4-8257-f46d0493d13a
Faulting package full name:
Help please. If somebody tell me "Reinstall windows", I ### him!

Application: Ssms.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Security.Cryptography.CryptographicException
Stack:
at Microsoft.SqlServer.Management.RegisteredServers.RegisteredServer.ProtectData(System.String, Boolean)
at Microsoft.SqlServer.Management.RegisteredServers.RegisteredServer.get_SecureConnectionString()
at Microsoft.SqlServer.Management.RegisteredServers.RegisteredServer.get_ConnectionString()
at Microsoft.SqlServer.Management.RegisteredServers.RegisteredServer.get_ServerName()
at Microsoft.SqlServer.Management.RegisteredServers.RegisteredServerTree.AddRegisteredServerNode(Microsoft.SqlServer.Management.RegisteredServers.RegisteredServer, System.Windows.Forms.TreeNodeCollection)
at Microsoft.SqlServer.Management.RegisteredServers.RegisteredServerTree.AddServerGroupToNodeCollection(Microsoft.SqlServer.Management.RegisteredServers.ServerGroup, System.Windows.Forms.TreeNodeCollection, Boolean)
at Microsoft.SqlServer.Management.RegisteredServers.RegisteredServerTree.AddServerGroupToNodeCollection(Microsoft.SqlServer.Management.RegisteredServers.ServerGroup, System.Windows.Forms.TreeNodeCollection, Boolean)
at Microsoft.SqlServer.Management.RegisteredServers.RegisteredServerTree.Initialize(Microsoft.SqlServer.Management.RegisteredServers.ServerGroup, Microsoft.SqlServer.Management.Common.ServerType, Microsoft.SqlServer.Management.UI.ConnectionDlg.IServerType,
Microsoft.SqlServer.Management.RegisteredServers.AddCentralManagementServerDelegate, Microsoft.SqlServer.Management.RegisteredServers.AddNewCentralManagementServerDelegate, Microsoft.SqlServer.Management.RegisteredServers.DeleteCentralManagementServerDelegate,
Microsoft.SqlServer.Management.RegisteredServers.GetServiceProviderDelegate)
at Microsoft.SqlServer.Management.RegisteredServers.RegisteredServerControl.RegisteredServerControl_Load(System.Object, System.EventArgs)
at System.Windows.Forms.UserControl.OnLoad(System.EventArgs)
at System.Windows.Forms.UserControl.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ScrollableControl.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ContainerControl.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.UserControl.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.IntCreateWindowEx(Int32, System.String, System.String, Int32, Int32, Int32, Int32, Int32, System.Runtime.InteropServices.HandleRef, System.Runtime.InteropServices.HandleRef, System.Runtime.InteropServices.HandleRef,
System.Object)
at System.Windows.Forms.UnsafeNativeMethods.CreateWindowEx(Int32, System.String, System.String, Int32, Int32, Int32, Int32, Int32, System.Runtime.InteropServices.HandleRef, System.Runtime.InteropServices.HandleRef, System.Runtime.InteropServices.HandleRef,
System.Object)
at System.Windows.Forms.NativeWindow.CreateHandle(System.Windows.Forms.CreateParams)
at System.Windows.Forms.Control.CreateHandle()
at System.Windows.Forms.Control.get_Handle()
at Microsoft.VisualStudio.Shell.UIWin32ElementWrapper.Create(IntPtr, IntPtr ByRef)
at Microsoft.VisualStudio.Platform.WindowManagement.UIElementDocumentObject.Init(Boolean)
at Microsoft.VisualStudio.Platform.WindowManagement.DocumentObjectSite.InitializeDocumentObject(System.Object)
at Microsoft.VisualStudio.Platform.WindowManagement.WindowManagerService.CreateContentPane(System.String, Int32, Int32, System.String, UInt32, UInt32, System.Object, System.Object, Microsoft.VisualStudio.OLE.Interop.IServiceProvider, Microsoft.VisualStudio.Shell.Interop.IVsUIHierarchy,
UInt32, Int32 ByRef, System.Guid ByRef, Microsoft.VisualStudio.Shell.Interop.IVsWindowFrame ByRef)
at Microsoft.VisualStudio.Shell.Interop.IVsUIShell.CreateToolWindow(UInt32, UInt32, System.Object, System.Guid ByRef, System.Guid ByRef, System.Guid ByRef, Microsoft.VisualStudio.OLE.Interop.IServiceProvider, System.String, Int32[], Microsoft.VisualStudio.Shell.Interop.IVsWindowFrame
ByRef)
at Microsoft.VisualStudio.Shell.Package.CreateToolWindow(System.Type, Int32, Microsoft.VisualStudio.Shell.ProvideToolWindowAttribute)
at Microsoft.VisualStudio.Shell.Package.CreateToolWindow(System.Type, Int32)
at Microsoft.VisualStudio.Shell.Package.FindToolWindow(System.Type, Int32, Boolean, Microsoft.VisualStudio.Shell.ProvideToolWindowAttribute)
at Microsoft.SqlServer.Management.RegisteredServers.RegisteredServers.ShowToolWindow(System.Object, System.EventArgs)
at System.ComponentModel.Design.MenuCommand.Invoke()
at System.ComponentModel.Design.MenuCommand.Invoke(System.Object)
at Microsoft.VisualStudio.Shell.OleMenuCommandService.Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.Exec(System.Guid ByRef, UInt32, UInt32, IntPtr, IntPtr)
at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.Exec(System.Guid ByRef, UInt32, UInt32, IntPtr, IntPtr)
at Microsoft.VisualStudio.Shell.Interop.IVsUIDataSource.Invoke(System.String, System.Object, System.Object ByRef)
at Microsoft.Internal.VisualStudio.PlatformUI.DataSource.Invoke(System.String, System.Object, System.Object ByRef)
at Microsoft.VisualStudio.PlatformUI.VsCommand.Execute(System.Object)
at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(System.Windows.Input.ICommandSource, Boolean)
at System.Windows.Controls.MenuItem.InvokeClickAfterRender(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

SQL Server 2008 R2 Sp2 crashed on query

On some my query I got:
Msg 0, Level 11, State 0, Line 0
A severe error occurred Msg 0, Level 20, State 0, Line 0
A severe error occurred In ERRORLOG:
2014-07-09 17:01:30.50 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 * 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.59 spid71 2014-07-09 17:01:30.66 spid71 2014-07-09 17:01:30.66 spid71 2014-07-09 17:01:30.66 spid71 2014-07-09 17:01:30.66 spid71 2014-07-09 17:01:30.66 spid71 2014-07-09 17:01:30.66 spid71 2014-07-09 17:01:30.67 spid71 2014-07-09 17:01:30.67 spid71 2014-07-09 17:01:30.67 spid71 2014-07-09 17:01:30.67 spid71 2014-07-09 17:01:30.67 spid71 2014-07-09 17:01:30.67 spid71 2014-07-09 17:01:30.67 spid71 2014-07-09 17:01:30.67 spid71 2014-07-09 17:01:30.67 spid71 2014-07-09 17:01:30.67 spid71 2014-07-09 17:01:30.68 spid71 2014-07-09 17:01:30.68 spid71 2014-07-09 17:01:30.68 spid71 2014-07-09 17:01:30.68 spid71 2014-07-09 17:01:30.68 spid71 2014-07-09 17:01:30.69 spid71 2014-07-09 17:01:30.69 spid71 2014-07-09 17:01:30.70 spid71 2014-07-09 17:01:30.71 spid71 2014-07-09 17:01:30.71 spid71 2014-07-09 17:01:30.71 spid71 2014-07-09 17:01:34.02 spid71 External dump process I have tried on another How and where I should report it? on the current command. The results, if any, should be discarded.
on the current command. The results, if any, should be discarded.
Using 'dbghelp.dll' version '4.0.5'
***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0010.txt
SqlDumpExceptionHandler: Process 71 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 07/09/14 17:01:30 spid 71
*
*
* Exception Address = 00000000008AEEF0 Module(sqlservr+000000000031EEF0)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 0000000000000000
* Input Buffer 510 bytes -
update dbo.CONTRACT_CONNECTION set DATE_TO=coalesce(( SELECT
* MAX(F) FROM ( VALUES ((select max(ccdailypla1_.DATE_FOR) from dbo.CC_DAI
* LY_PLAN ccdailypla1_ where dbo.CONTRACT_CONNECTION.CC_ID=ccdailypla1_.CC
* _ID)),((select max(contrarcex2_.CORR_TIME) from dbo.CONTR_ARC_EXPS_D con
* trarcex2_ where dbo.CONTRACT_CONNECTION.CC_ID=contrarcex2_.CC_ID)),((sel
* ect max(contrarcex3_.CORR_TIME) from dbo.CONTR_ARC_EXPS_H contrarcex3_ w
* here dbo.CONTRACT_CONNECTION.CC_ID=contrarcex3_.CC_ID and contrarcex3_.C
* C_ID=CC_ID)) ) T(F) ), DATE_TO), DVIS=case when ( SELECT MAX(F) FROM ( V
* ALUES ((select max(ccdailypla4_.DATE_FOR) from dbo.CC_DAILY_PLAN ccdaily
* pla4_ where dbo.CONTRACT_CONNECTION.CC_ID=ccdailypla4_.CC_ID)),((select
* max(contrarcex5_.CORR_TIME) from dbo.CONTR_ARC_EXPS_D contrarcex5_ where
* dbo.CONTRACT_CONNECTION.CC_ID=contrarcex5_.CC_ID)),((select max(contrar
* cex6_.CORR_TIME) from dbo.CONTR_ARC_EXPS_H contrarcex6_ where dbo.CONTRA
* CT_CONNECTION.CC_ID=contrarcex6_.CC_ID and contrarcex6_.CC_ID=CC_ID)) )
* T(F) ) is null then 1 else 0 end, MODIFICATION_DATE=getdate() where (DAT
* E_TO is null or DATE_TO<>( SELECT MAX(F) FROM ( VALUES ((select max(ccda
* ilypla7_.DATE_FOR) from dbo.CC_DAILY_PLAN ccdailypla7_ where dbo.CONTRAC
* T_CONNECTION.CC_ID=ccdailypla7_.CC_ID)),((select max(contrarcex8_.CORR_T
* IME) from dbo.CONTR_ARC_EXPS_D contrarcex8_ where dbo.CONTRACT_CONNECTIO
* N.CC_ID=contrarcex8_.CC_ID)),((select max(contrarcex9_.CORR_TIME) from d
* bo.CONTR_ARC_EXPS_H contrarcex9_ where dbo.CONTRACT_CONNECTION.CC_ID=con
* trarcex9_.CC_ID and contrarcex9_.CC_ID=CC_ID)) ) T(F) )) and (( SELECT M
* AX(F) FROM ( VALUES ((select max(ccdailypla10_.DATE_FOR) from dbo.CC_DAI
* LY_PLAN ccdailypla10_ where dbo.CONTRACT_CONNECTION.CC_ID=ccdailypla10_.
* CC_ID)),((select max(contrarcex11_.CORR_TIME) from dbo.CONTR_ARC_EXPS_D
* contrarcex11_ where dbo.CONTRACT_CONNECTION.CC_ID=contrarcex11_.CC_ID)),
* ((select max(contrarcex12_.CORR_TIME) from dbo.CONTR_ARC_EXPS_H contrarc
* ex12_ where dbo.CONTRACT_CONNECTION.CC_ID=contrarcex12_.CC_ID and contra
* rcex12_.CC_ID=CC_ID)) ) T(F)
*
*
* MODULE BASE END SIZE
* sqlservr 0000000000590000 00000000041A1FFF 03c12000
* ntdll 0000000076F90000 0000000077138FFF 001a9000
* kernel32 0000000076E70000 0000000076F8EFFF 0011f000
* KERNELBASE 000007FEFD240000 000007FEFD2AAFFF 0006b000
* ADVAPI32 000007FEFD490000 000007FEFD56AFFF 000db000
* msvcrt 000007FEFDE10000 000007FEFDEAEFFF 0009f000
* sechost 000007FEFEC40000 000007FEFEC5EFFF 0001f000
* RPCRT4 000007FEFDB20000 000007FEFDC4CFFF 0012d000
* MSVCR80 00000000739C0000 0000000073A88FFF 000c9000
* MSVCP80 00000000738A0000 00000000739A8FFF 00109000
* sqlos 0000000073860000 0000000073866FFF 00007000
* Secur32 000007FEFCA20000 000007FEFCA2AFFF 0000b000
* SSPICLI 000007FEFCD40000 000007FEFCD64FFF 00025000
* pdh 000007FEF9BD0000 000007FEF9C1DFFF 0004e000
* SHLWAPI 000007FEFDCA0000 000007FEFDD10FFF 00071000
* GDI32 000007FEFF0E0000 000007FEFF146FFF 00067000
* USER32 0000000076D70000 0000000076E69FFF 000fa000
* LPK 000007FEFF1B0000 000007FEFF1BDFFF 0000e000
* USP10 000007FEFDD40000 000007FEFDE08FFF 000c9000
* USERENV 000007FEFC220000 000007FEFC23DFFF 0001e000
* profapi 000007FEFCEA0000 000007FEFCEAEFFF 0000f000
* WINMM 000007FEF9DD0000 000007FEF9E0AFFF 0003b000
* IPHLPAPI 000007FEFA650000 000007FEFA676FFF 00027000
* NSI 000007FEFDA70000 000007FEFDA77FFF 00008000
* WINNSI 000007FEFA520000 000007FEFA52AFFF 0000b000
* opends60 0000000073830000 0000000073837FFF 00008000
* NETAPI32 000007FEFA2F0000 000007FEFA305FFF 00016000
* netutils 000007FEFA610000 000007FEFA61BFFF 0000c000
* srvcli 000007FEFC980000 000007FEFC9A2FFF 00023000
* wkscli 000007FEFA2D0000 000007FEFA2E4FFF 00015000
* LOGONCLI 000007FEFC7D0000 000007FEFC7FFFFF 00030000
* SAMCLI 000007FEF9E30000 000007FEF9E43FFF 00014000
* BatchParser 00000000737E0000 000000007380CFFF 0002d000
* IMM32 000007FEFED90000 000007FEFEDBDFFF 0002e000
* MSCTF 000007FEFEFD0000 000007FEFF0D8FFF 00109000
* psapi 0000000077150000 0000000077156FFF 00007000
* instapi10 00000000737A0000 00000000737ACFFF 0000d000
* cscapi 000007FEF9C50000 000007FEF9C5EFFF 0000f000
* sqlevn70 0000000073590000 0000000073793FFF 00204000
* CRYPTSP 000007FEFC950000 000007FEFC966FFF 00017000
* rsaenh 000007FEFC4A0000 000007FEFC4E6FFF 00047000
* CRYPTBASE 000007FEFCDD0000 000007FEFCDDEFFF 0000f000
* BROWCLI 000007FEF9AA0000 000007FEF9AB1FFF 00012000
* AUTHZ 000007FEFC920000 000007FEFC94EFFF 0002f000
* MSCOREE 000007FEF9A30000 000007FEF9A9EFFF 0006f000
* ole32 000007FEFEDC0000 000007FEFEFC2FFF 00203000
* credssp 000007FEFC350000 000007FEFC359FFF 0000a000
* msv1_0 000007FEFC600000 000007FEFC650FFF 00051000
* cryptdll 000007FEFCAA0000 000007FEFCAB3FFF 00014000
* kerberos 000007FEFC6C0000 000007FEFC773FFF 000b4000
* MSASN1 000007FEFCF80000 000007FEFCF8EFFF 0000f000
* schannel 000007FEFC660000 000007FEFC6B6FFF 00057000
* CRYPT32 000007FEFD030000 000007FEFD196FFF 00167000
* security 0000000073470000 0000000073472FFF 00003000
* WS2_32 000007FEFDC50000 000007FEFDC9CFFF 0004d000
* SHELL32 000007FEFDEB0000 000007FEFEC37FFF 00d88000
* OLEAUT32 000007FEFF1C0000 000007FEFF296FFF 000d7000
* ftimport 0000000060000000 0000000060024FFF 00025000
* MSFTE 0000000049980000 0000000049D2DFFF 003ae000
* VERSION 000007FEFC030000 000007FEFC03BFFF 0000c000
* dbghelp 0000000073270000 00000000733CDFFF 0015e000
* WINTRUST 000007FEFCFD0000 000007FEFD009FFF 0003a000
* ncrypt 000007FEFC8D0000 000007FEFC91DFFF 0004e000
* bcrypt 000007FEFC8A0000 000007FEFC8C1FFF 00022000
* ntmarta 000007FEFC000000 000007FEFC02CFFF 0002d000
* WLDAP32 000007FEFF150000 000007FEFF1A1FFF 00052000
* mswsock 000007FEFC810000 000007FEFC864FFF 00055000
* wship6 000007FEFC800000 000007FEFC806FFF 00007000
* wshtcpip 000007FEFC100000 000007FEFC106FFF 00007000
* ntdsapi 000007FEF9890000 000007FEF98B6FFF 00027000
* bcryptprimitives 000007FEFC3E0000 000007FEFC42BFFF 0004c000
* CLBCatQ 000007FEFD850000 000007FEFD8E8FFF 00099000
* sqlncli10 0000000064780000 0000000064A3CFFF 002bd000
* COMCTL32 000007FEF42C0000 000007FEF435FFFF 000a0000
* COMDLG32 000007FEFDA80000 000007FEFDB16FFF 00097000
* SQLNCLIR10 0000000064740000 0000000064776FFF 00037000
* netbios 000007FEF7C10000 000007FEF7C19FFF 0000a000
* xpstar 00000000646B0000 0000000064737FFF 00088000
* SQLSCM 00000000646A0000 00000000646ADFFF 0000e000
* ODBC32 000007FEF9210000 000007FEF92C0FFF 000b1000
* ATL80 0000000074900000 000000007491FFFF 00020000
* odbcint 00000000749E0000 0000000074A17FFF 00038000
* clusapi 000007FEF8F70000 000007FEF8FBFFFF 00050000
* resutils 000007FEF8F50000 000007FEF8F68FFF 00019000
* xpstar 0000000064670000 0000000064694FFF 00025000
* dbghelp 0000000064510000 000000006466DFFF 0015e000
*
* P1Home: 0000000016EB3E50: 00000000C0000005 0000000000000000 00000000008AEEF0 0000000000000002 0000000000000000 0000000000000000
* P2Home: 0000000016EB3960: 0000000016EB3E50 0000000016EB3960 FFFFFFFF00000000 0000000000000000 0000000094AB1AD0 0000000000000000
* P3Home: FFFFFFFF00000000:
* P4Home: 0000000000000000:
* P5Home: 0000000094AB1AD0: 000000000069ED90 0000000000000001 0000000094AB1B80 0000000000000001 0000000094AB1AF8 0000000000000000
* P6Home: 0000000000000000:
* ContextFlags: 000000000010001F:
* MxCsr: 0000000000001FA0:
* SegCs: 0000000000000033:
* SegDs: 000000000000002B:
* SegEs: 000000000000002B:
* SegFs: 0000000000000053:
* SegGs: 000000000000002B:
* SegSs: 000000000000002B:
* EFlags: 0000000000010246: 0000000000000000 0000000101580000 0000000102680000 0000000102780000 0000000000000000 0000001000000000
Rax: 0000000000000000:
Rcx: 0000000094AB47B0: 00000000006687C0 0000000000000001 0000000094A7E060 0000000000000001 0000000000000000 0000000094B0A560
Rdx: 0000000094A7E060: 0000000000596C60 0000000000002000 0000000000000082 0000000094A00080 0000000100000008 0000000080080B08
Rbx: 0000000094AB4700: 000000000069ED90 0000003800000001 0000000094AB47B0 0000000000000002 0000000094AB4728 0000000094AB4530
Rsp: 0000000016EB3F20: 0000000094AB4700 0000000094A7E060 0000000094AAA300 0000000000000001 0000000000000000 0000000000000000
Rbp: 0000000000000000:
Rsi: 0000000094AAA1C0: 000000000069ED90 0000000000000001 0000000000000000 0000000000000002 0000000094AAA1E8 0000000094AAA270
Rdi: 0000000000000000:
R8: 0000000000000000:
R9: 00000000000002F3:
R10: 0000000000596C60: 0000000002ADC674 000000000059EA18 000000000059E9B8 0000000002A89A04 0000000002A88BD8 0000000002A899F8
R11: 0000000094A7E060: 0000000000596C60 0000000000002000 0000000000000082 0000000094A00080 0000000100000008 0000000080080B08
R12: 0000000094AB1BC0: 000000000069ED90 0000000000000001 0000000094AB1C70 0000000000000002 0000000094AB1BE8 0000000000000000
R13: 0000000000000001:
R14: 0000000094AB1AB0: 0000000094AB1AC0 0000000094AB1970 0000000000000000 0000000094A7F7F0 000000000069ED90 0000000000000001
R15: 0000000094AB1AD0: 000000000069ED90 0000000000000001 0000000094AB1B80 0000000000000001 0000000094AB1AF8 0000000000000000
Rip: 00000000008AEEF0: 8B48D68B48008B4C 000002B890FF41C8 4B8B481574FF8548 3D5852FF118B4810 EB56840F000000C2 9C8B48C68B48FFF1
* *******************************************************************************
* -------------------------------------------------------------------------------
* Short Stack Dump
00000000008AEEF0 Module(sqlservr+000000000031EEF0)
00000000008BEAFE Module(sqlservr+000000000032EAFE)
00000000008BEAFE Module(sqlservr+000000000032EAFE)
00000000008BEAFE Module(sqlservr+000000000032EAFE)
00000000008BEAFE Module(sqlservr+000000000032EAFE)
00000000008BEAFE Module(sqlservr+000000000032EAFE)
00000000018D2533 Module(sqlservr+0000000001342533)
00000000006CBB8D Module(sqlservr+000000000013BB8D)
00000000007375D7 Module(sqlservr+00000000001A75D7)
000000000077203D Module(sqlservr+00000000001E203D)
0000000000771E3F Module(sqlservr+00000000001E1E3F)
0000000000771D58 Module(sqlservr+00000000001E1D58)
0000000000B1AB83 Module(sqlservr+000000000058AB83)
0000000000B1C800 Module(sqlservr+000000000058C800)
0000000000AC3DC6 Module(sqlservr+0000000000533DC6)
000000000059AB94 Module(sqlservr+000000000000AB94)
000000000059B05E Module(sqlservr+000000000000B05E)
000000000059AD57 Module(sqlservr+000000000000AD57)
0000000000A751DE Module(sqlservr+00000000004E51DE)
0000000000A75395 Module(sqlservr+00000000004E5395)
0000000000A78925 Module(sqlservr+00000000004E8925)
0000000000A759D6 Module(sqlservr+00000000004E59D6)
00000000739C37D7 Module(MSVCR80+00000000000037D7)
00000000739C3894 Module(MSVCR80+0000000000003894)
0000000076E8652D Module(kernel32+000000000001652D)
0000000076FBC521 Module(ntdll+000000000002C521)
Stack Signature for the dump is 0x000000015B49D68C
External dump process return code 0x20000001.
returned no errors.
server (not sure about SP) and also have crash.

Your best bet is to open a support case with Microsoft. They will analyze the dump files and will provide you with resolution.
http://support.microsoft.com/contactus/?ln=en-nz
YOu can also check for known issues search for "c0000005 EXCEPTION_ACCESS_VIOLATION" adn your sql server version.
To know more about access violations and how to troubleshoot this check these links
http://mssqlwiki.com/2012/10/16/sql-server-exception_access_violation-and-sql-server-assertion/
http://troubleshootingsql.com/2011/03/09/wiki-demystifying-sql-server-exception-dumps/
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Sql server 2008 R2 sp2 keeps crashing with ntdll.dll

Our sql server 2008 r2 on windows 2008 r2 crashes once a day with this error
Faulting application name: sqlservr.exe, version: 2009.100.4290.0, time stamp: 0x52007306
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x11b8
Faulting application start time: 0x01cf59e47c2e9f9a
Faulting application path: C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 93d8ef8b-c70c-11e3-b572-002564fcc042
Here is the dump
Version=1
EventType=APPCRASH
EventTime=130423078596029680
ReportType=2
Consent=1
ReportIdentifier=93d8ef8c-c70c-11e3-b572-002564fcc042
IntegratorReportIdentifier=93d8ef8b-c70c-11e3-b572-002564fcc042
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=sqlservr.exe
Sig[1].Name=Application Version
Sig[1].Value=2009.100.4290.0
Sig[2].Name=Application Timestamp
Sig[2].Value=52007306
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_259d
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7601.17725
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4ec4aa8e
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
Sig[7].Value=00000000000c40f2
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.274.10
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=259d
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=259dc7d033214d7478a8b078fa9c6fc4
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=a970
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=a9707a254613322c29b1185c564c54e6
UI[2]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
UI[5]=Check online for a solution (recommended)
UI[6]=Check for a solution later (recommended)
UI[7]=Close
UI[8]=SQL Server Windows NT - 64 Bit stopped working and was closed
UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
UI[10]=&Close
LoadedModule[0]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[5]=C:\Windows\system32\msvcrt.dll
LoadedModule[6]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[7]=C:\Windows\system32\RPCRT4.dll
LoadedModule[8]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_88df89932faf0bf6\MSVCR80.dll
LoadedModule[9]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_88df89932faf0bf6\MSVCP80.dll
LoadedModule[10]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlos.dll
LoadedModule[11]=C:\Windows\system32\Secur32.dll
LoadedModule[12]=C:\Windows\system32\SSPICLI.DLL
LoadedModule[13]=C:\Windows\system32\pdh.dll
LoadedModule[14]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[15]=C:\Windows\system32\GDI32.dll
LoadedModule[16]=C:\Windows\system32\USER32.dll
LoadedModule[17]=C:\Windows\system32\LPK.dll
LoadedModule[18]=C:\Windows\system32\USP10.dll
LoadedModule[19]=C:\Windows\system32\USERENV.dll
LoadedModule[20]=C:\Windows\system32\profapi.dll
LoadedModule[21]=C:\Windows\system32\WINMM.dll
LoadedModule[22]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[23]=C:\Windows\system32\NSI.dll
LoadedModule[24]=C:\Windows\system32\WINNSI.DLL
LoadedModule[25]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\opends60.dll
LoadedModule[26]=C:\Windows\system32\NETAPI32.dll
LoadedModule[27]=C:\Windows\system32\netutils.dll
LoadedModule[28]=C:\Windows\system32\srvcli.dll
LoadedModule[29]=C:\Windows\system32\wkscli.dll
LoadedModule[30]=C:\Windows\system32\LOGONCLI.DLL
LoadedModule[31]=C:\Windows\system32\SAMCLI.DLL
LoadedModule[32]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\BatchParser.dll
LoadedModule[33]=C:\Windows\system32\IMM32.DLL
LoadedModule[34]=C:\Windows\system32\MSCTF.dll
LoadedModule[35]=C:\Windows\system32\psapi.dll
LoadedModule[36]=C:\Program Files\Microsoft SQL Server\100\Shared\instapi10.dll
LoadedModule[37]=C:\Windows\system32\cscapi.dll
LoadedModule[38]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\sqlevn70.rll
LoadedModule[39]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[40]=C:\Windows\system32\rsaenh.dll
LoadedModule[41]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[42]=C:\Windows\system32\BROWCLI.DLL
LoadedModule[43]=C:\Windows\system32\AUTHZ.DLL
LoadedModule[44]=C:\Windows\system32\MSCOREE.DLL
LoadedModule[45]=C:\Windows\system32\ole32.dll
LoadedModule[46]=C:\Windows\system32\credssp.dll
LoadedModule[47]=C:\Windows\system32\msv1_0.DLL
LoadedModule[48]=C:\Windows\system32\cryptdll.dll
LoadedModule[49]=C:\Windows\system32\kerberos.DLL
LoadedModule[50]=C:\Windows\system32\MSASN1.dll
LoadedModule[51]=C:\Windows\system32\schannel.DLL
LoadedModule[52]=C:\Windows\system32\CRYPT32.dll
LoadedModule[53]=C:\Windows\system32\security.dll
LoadedModule[54]=C:\Windows\system32\WS2_32.dll
LoadedModule[55]=C:\Windows\system32\SHELL32.dll
LoadedModule[56]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[57]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\ftimport.dll
LoadedModule[58]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\MSFTE.DLL
LoadedModule[59]=C:\Windows\system32\VERSION.dll
LoadedModule[60]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\dbghelp.dll
LoadedModule[61]=C:\Windows\system32\WINTRUST.dll
LoadedModule[62]=C:\Windows\system32\ntmarta.dll
LoadedModule[63]=C:\Windows\system32\WLDAP32.dll
LoadedModule[64]=C:\Windows\system32\ncrypt.dll
LoadedModule[65]=C:\Windows\system32\bcrypt.dll
LoadedModule[66]=C:\Windows\system32\mswsock.dll
LoadedModule[67]=C:\Windows\System32\wship6.dll
LoadedModule[68]=C:\Windows\System32\wshtcpip.dll
LoadedModule[69]=C:\Windows\system32\ntdsapi.dll
LoadedModule[70]=C:\Windows\system32\DNSAPI.dll
LoadedModule[71]=C:\Windows\system32\rasadhlp.dll
LoadedModule[72]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[73]=C:\Windows\system32\bcryptprimitives.dll
LoadedModule[74]=C:\Windows\system32\SAMLIB.dll
LoadedModule[75]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[76]=C:\Windows\system32\sqlncli10.dll
LoadedModule[77]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_a4d6a923711520a9\COMCTL32.dll
LoadedModule[78]=C:\Windows\system32\COMDLG32.dll
LoadedModule[79]=C:\Windows\system32\1033\SQLNCLIR10.RLL
LoadedModule[80]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
LoadedModule[81]=C:\Windows\assembly\NativeImages_v2.0.50727_64\mscorlib\51a23687fdafc32b697f5a719e364651\mscorlib.ni.dll
LoadedModule[82]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorsec.dll
LoadedModule[83]=C:\Windows\system32\imagehlp.dll
LoadedModule[84]=C:\Windows\system32\GPAPI.dll
LoadedModule[85]=C:\Windows\system32\cryptnet.dll
LoadedModule[86]=C:\Windows\system32\SensApi.dll
LoadedModule[87]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\SqlAccess.dll
LoadedModule[88]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll
LoadedModule[89]=C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll
LoadedModule[90]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System\6be6efa1e2ffc9d46e99839edac5c5a8\System.ni.dll
LoadedModule[91]=C:\Windows\assembly\GAC_64\System.Transactions\2.0.0.0__b77a5c561934e089\System.Transactions.dll
LoadedModule[92]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Security\15270ef5168ba4d4185515789a08655d\System.Security.ni.dll
LoadedModule[93]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\xpstar.dll
LoadedModule[94]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\SQLSCM.dll
LoadedModule[95]=C:\Windows\system32\ODBC32.dll
LoadedModule[96]=C:\Windows\WinSxS\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_none_8a1a02152edb659b\ATL80.DLL
LoadedModule[97]=C:\Windows\system32\odbcint.dll
LoadedModule[98]=C:\Windows\system32\clusapi.dll
LoadedModule[99]=C:\Windows\system32\resutils.dll
LoadedModule[100]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\xpstar.rll
LoadedModule[101]=C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll
LoadedModule[102]=C:\Windows\assembly\GAC_MSIL\System.Security\2.0.0.0__b03f5f7f11d50a3a\System.Security.dll
LoadedModule[103]=C:\Windows\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll
LoadedModule[104]=C:\Windows\system32\COMRES.DLL
LoadedModule[105]=C:\Windows\system32\XOLEHLP.DLL
LoadedModule[106]=C:\Windows\system32\MSDTCPRX.DLL
LoadedModule[107]=C:\Windows\system32\MTXCLU.DLL
LoadedModule[108]=C:\Windows\system32\ktmw32.dll
LoadedModule[109]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[110]=C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xp_greta_64.dll
LoadedModule[111]=C:\Windows\system32\apphelp.dll
LoadedModule[112]=C:\Windows\system32\dsrole.dll
LoadedModule[113]=C:\Program Files\Microsoft SQL Server\80\COM\sqlvdi.dll
LoadedModule[114]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\odsole70.dll
LoadedModule[115]=C:\Windows\system32\scrrun.dll
LoadedModule[116]=C:\Windows\system32\SXS.DLL
LoadedModule[117]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\odsole70.RLL
LoadedModule[118]=C:\Program Files\Microsoft SQL Server\90\Shared\instapi.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=SQL Server Windows NT - 64 Bit
AppPath=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
Can help me fixed this
Thanks

Thank you for your responses. This server is on a dell poweredge T710 with 192 gb of memory. All the hardware drivers are up to date and so is sql. No memory errors. The only error I get is when sql crashes. The only 3rd party
dll what is on the server would be xp_greta_64.dll. We are looking into that.
I have a question about setting up a link server with 'out of process' We only use sql server link connections with other sql servers. When I try to setup 'out of process' unchecking allow inprocess under SQLNCLI all of my link servers end up
failing and giving me errors. I had to switch it back since this is a production machine. Is there a way to just set up 'out of process' on one link server with SQLNCLI, it seems it is all or nothing. Do I have to delete all the current link
servers and recreate them?
The only other thing that we have changed is that we have added Python 3.3 and ActivePerl 5.16.3 but not on this server. Only on all of our other sql servers.
Here is our last dump from yesterday. Thanks again, If I have too I will open a case up with Microsoft.
Version=1
EventType=APPCRASH
EventTime=130444796758798656
ReportType=2
Consent=1
ReportIdentifier=3b3973c8-dacd-11e3-a1c5-002564fcc042
IntegratorReportIdentifier=3b3973c7-dacd-11e3-a1c5-002564fcc042
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=sqlservr.exe
Sig[1].Name=Application Version
Sig[1].Value=2009.100.4302.0
Sig[2].Name=Application Timestamp
Sig[2].Value=52f5d194
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_9f88
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7601.18247
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=521eaf24
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
Sig[7].Value=00000000000c4102
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.274.10
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=9f88
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=9f887580f62df3cb4138fc685cae8618
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=d54e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=d54ee610c7110c152675c4fdbbef635a
UI[2]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
UI[5]=Check online for a solution (recommended)
UI[6]=Check for a solution later (recommended)
UI[7]=Close
UI[8]=SQL Server Windows NT - 64 Bit stopped working and was closed
UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
UI[10]=&Close
LoadedModule[0]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[5]=C:\Windows\system32\msvcrt.dll
LoadedModule[6]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[7]=C:\Windows\system32\RPCRT4.dll
LoadedModule[8]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_88df89932faf0bf6\MSVCR80.dll
LoadedModule[9]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_88df89932faf0bf6\MSVCP80.dll
LoadedModule[10]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlos.dll
LoadedModule[11]=C:\Windows\system32\Secur32.dll
LoadedModule[12]=C:\Windows\system32\SSPICLI.DLL
LoadedModule[13]=C:\Windows\system32\pdh.dll
LoadedModule[14]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[15]=C:\Windows\system32\GDI32.dll
LoadedModule[16]=C:\Windows\system32\USER32.dll
LoadedModule[17]=C:\Windows\system32\LPK.dll
LoadedModule[18]=C:\Windows\system32\USP10.dll
LoadedModule[19]=C:\Windows\system32\USERENV.dll
LoadedModule[20]=C:\Windows\system32\profapi.dll
LoadedModule[21]=C:\Windows\system32\WINMM.dll
LoadedModule[22]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[23]=C:\Windows\system32\NSI.dll
LoadedModule[24]=C:\Windows\system32\WINNSI.DLL
LoadedModule[25]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\opends60.dll
LoadedModule[26]=C:\Windows\system32\NETAPI32.dll
LoadedModule[27]=C:\Windows\system32\netutils.dll
LoadedModule[28]=C:\Windows\system32\srvcli.dll
LoadedModule[29]=C:\Windows\system32\wkscli.dll
LoadedModule[30]=C:\Windows\system32\LOGONCLI.DLL
LoadedModule[31]=C:\Windows\system32\SAMCLI.DLL
LoadedModule[32]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\BatchParser.dll
LoadedModule[33]=C:\Windows\system32\IMM32.DLL
LoadedModule[34]=C:\Windows\system32\MSCTF.dll
LoadedModule[35]=C:\Windows\system32\psapi.dll
LoadedModule[36]=C:\Program Files\Microsoft SQL Server\100\Shared\instapi10.dll
LoadedModule[37]=C:\Windows\system32\cscapi.dll
LoadedModule[38]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\sqlevn70.rll
LoadedModule[39]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[40]=C:\Windows\system32\rsaenh.dll
LoadedModule[41]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[42]=C:\Windows\system32\BROWCLI.DLL
LoadedModule[43]=C:\Windows\system32\AUTHZ.DLL
LoadedModule[44]=C:\Windows\system32\MSCOREE.DLL
LoadedModule[45]=C:\Windows\system32\ole32.dll
LoadedModule[46]=C:\Windows\system32\credssp.dll
LoadedModule[47]=C:\Windows\system32\msv1_0.DLL
LoadedModule[48]=C:\Windows\system32\cryptdll.dll
LoadedModule[49]=C:\Windows\system32\kerberos.DLL
LoadedModule[50]=C:\Windows\system32\MSASN1.dll
LoadedModule[51]=C:\Windows\system32\schannel.DLL
LoadedModule[52]=C:\Windows\system32\CRYPT32.dll
LoadedModule[53]=C:\Windows\system32\security.dll
LoadedModule[54]=C:\Windows\system32\WS2_32.dll
LoadedModule[55]=C:\Windows\system32\SHELL32.dll
LoadedModule[56]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[57]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\ftimport.dll
LoadedModule[58]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\MSFTE.DLL
LoadedModule[59]=C:\Windows\system32\VERSION.dll
LoadedModule[60]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\dbghelp.dll
LoadedModule[61]=C:\Windows\system32\WINTRUST.dll
LoadedModule[62]=C:\Windows\system32\ntmarta.dll
LoadedModule[63]=C:\Windows\system32\WLDAP32.dll
LoadedModule[64]=C:\Windows\system32\ncrypt.dll
LoadedModule[65]=C:\Windows\system32\bcrypt.dll
LoadedModule[66]=C:\Windows\system32\mswsock.dll
LoadedModule[67]=C:\Windows\System32\wship6.dll
LoadedModule[68]=C:\Windows\System32\wshtcpip.dll
LoadedModule[69]=C:\Windows\system32\ntdsapi.dll
LoadedModule[70]=C:\Windows\system32\DNSAPI.dll
LoadedModule[71]=C:\Windows\system32\rasadhlp.dll
LoadedModule[72]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[73]=C:\Windows\system32\bcryptprimitives.dll
LoadedModule[74]=C:\Windows\system32\SAMLIB.dll
LoadedModule[75]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[76]=C:\Windows\system32\sqlncli10.dll
LoadedModule[77]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_a4d3b9377117c3df\COMCTL32.dll
LoadedModule[78]=C:\Windows\system32\COMDLG32.dll
LoadedModule[79]=C:\Windows\system32\1033\SQLNCLIR10.RLL
LoadedModule[80]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\xpstar.dll
LoadedModule[81]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\SQLSCM.dll
LoadedModule[82]=C:\Windows\system32\ODBC32.dll
LoadedModule[83]=C:\Windows\WinSxS\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_none_8a1a02152edb659b\ATL80.DLL
LoadedModule[84]=C:\Windows\system32\odbcint.dll
LoadedModule[85]=C:\Windows\system32\clusapi.dll
LoadedModule[86]=C:\Windows\system32\resutils.dll
LoadedModule[87]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\xpstar.rll
LoadedModule[88]=C:\Windows\system32\COMRES.DLL
LoadedModule[89]=C:\Windows\system32\XOLEHLP.DLL
LoadedModule[90]=C:\Windows\system32\MSDTCPRX.DLL
LoadedModule[91]=C:\Windows\system32\MTXCLU.DLL
LoadedModule[92]=C:\Windows\system32\ktmw32.dll
LoadedModule[93]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[94]=C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xp_greta_64.dll
LoadedModule[95]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
LoadedModule[96]=C:\Windows\assembly\NativeImages_v2.0.50727_64\mscorlib\bb750d3baf928f94ea3977e96af9769f\mscorlib.ni.dll
LoadedModule[97]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorsec.dll
LoadedModule[98]=C:\Windows\system32\imagehlp.dll
LoadedModule[99]=C:\Windows\system32\GPAPI.dll
LoadedModule[100]=C:\Windows\system32\cryptnet.dll
LoadedModule[101]=C:\Windows\system32\SensApi.dll
LoadedModule[102]=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\SqlAccess.dll
LoadedModule[103]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll
LoadedModule[104]=C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll
LoadedModule[105]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System\350ed175b92e48f5249a1bab538872e5\System.ni.dll
LoadedModule[106]=C:\Windows\assembly\GAC_64\System.Transactions\2.0.0.0__b77a5c561934e089\System.Transactions.dll
LoadedModule[107]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Security\7c4199ce0470f8e4664a7ee345b31235\System.Security.ni.dll
LoadedModule[108]=C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll
LoadedModule[109]=C:\Windows\assembly\GAC_MSIL\System.Security\2.0.0.0__b03f5f7f11d50a3a\System.Security.dll
LoadedModule[110]=C:\Windows\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll
LoadedModule[111]=C:\Windows\system32\apphelp.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=SQL Server Windows NT - 64 Bit
AppPath=C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe

Sql server service crashes a few times yesterday, however, there is no .MDMP file generated in the log folder

hi there:
I've experienced several sql server service crashes yesterday, service was brought up after a few secs as we have an autostart feature.
Today, I'd like to dig more into the errors and on the event viewer -> Application, I saw errors below
"Faulting application sqlservr.exe, version 2009.100.4302.0, time stamp 0x52f5d194, faulting module ntdll.dll, version 6.0.6001.18538, time stamp 0x4cb73957, exception code 0xc0000374, fault offset 0x00000000000a7857, process id 0x15ec, application
start time 0x01cfd7e72b2997d3.
People suggested to check dump file inside C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Log
However, the lastest .mdmp file was on April 11, 2014. Do I need to turn on some settings on sql server in order to have this dump file?
Thanks
Hui
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

Results after sp_readerrorlog 1
LogDate ProcessInfo
Text
2014-09-24 04:03:28.460 Server
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4302.0 (X64)
Feb 7 2014 17:23:24
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.0 <X64> (Build 6001: Service Pack 1)
2014-09-24 04:03:28.460 Server
(c) Microsoft Corporation.
2014-09-24 04:03:28.460 Server
All rights reserved.
2014-09-24 04:03:28.460 Server
Server process ID is 5612.
2014-09-24 04:03:28.460 Server
System Manufacturer: 'IBM', System Model: 'IBM System x3650 -[7979AC1]-'.
2014-09-24 04:03:28.460 Server
Authentication mode is MIXED.
2014-09-24 04:03:28.460 Server
Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Log\ERRORLOG'.
2014-09-24 04:03:28.460 Server
This instance of SQL Server last reported using a process ID of 6780 at 9/24/2014 4:03:20 AM (local) 9/24/2014 11:03:20 AM (UTC). This is an informational message only; no user action is required.
2014-09-24 04:03:28.460 Server
Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\DATA\mastlog.ldf
2014-09-24 04:03:28.480 Server
SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-09-24 04:03:28.480 Server
Detected 4 CPUs. This is an informational message; no user action is required.
2014-09-24 04:03:28.480 Server
Cannot use Large Page Extensions: lock memory privilege was not granted.
2014-09-24 04:03:28.580 Server
Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-09-24 04:03:28.700 Server
Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014-09-24 04:03:28.870 spid7s
Starting up database 'master'.
2014-09-24 04:03:28.940 spid7s
1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2014-09-24 04:03:28.940 spid7s
0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2014-09-24 04:03:28.940 spid7s
Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-09-24 04:03:29.040 spid7s
CHECKDB for database 'master' finished without errors on 2014-09-20 12:00:01.697 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:29.050 spid7s
Resource governor reconfiguration succeeded.
2014-09-24 04:03:29.050 spid7s
SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2014-09-24 04:03:29.050 spid7s
SQL Server Audit has started the audits. This is an informational message. No user action is required.
2014-09-24 04:03:29.050 spid7s
FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQL2008R2'.
2014-09-24 04:03:29.070 spid7s
SQL Trace ID 1 was started by login "sa".
2014-09-24 04:03:29.070 spid7s
Starting up database 'mssqlsystemresource'.
2014-09-24 04:03:29.090 spid7s
The resource database build version is 10.50.4302. This is an informational message only. No user action is required.
2014-09-24 04:03:29.600 spid10s
Starting up database 'model'.
2014-09-24 04:03:29.600 spid7s
Server name is 'BPWDB046\SQL2008R2'. This is an informational message only. No user action is required.
2014-09-24 04:03:29.880 spid13s
A new instance of the full-text filter daemon host process has been successfully started.
2014-09-24 04:03:29.960 spid14s
Starting up database 'msdb'.
2014-09-24 04:03:29.960 spid17s
Starting up database 'DW_Detail'.
2014-09-24 04:03:29.960 spid16s
Starting up database 'ReportServer_MSSQLSSRSTempDB'.
2014-09-24 04:03:29.960 spid13s
Starting up database 'Billing_Rep'.
2014-09-24 04:03:29.960 spid15s
Starting up database 'ReportServer_MSSQLSSRS'.
2014-09-24 04:03:29.960 spid18s
Starting up database 'BCBio_DW'.
2014-09-24 04:03:29.960 spid19s
Starting up database 'ODS'.
2014-09-24 04:03:29.960 spid20s
Starting up database 'ReportServer$SQL2008'.
2014-09-24 04:03:29.970 spid21s
Starting up database 'ReportServer$SQL2008TempDB'.
2014-09-24 04:03:29.970 spid22s
Starting up database 'Billing'.
2014-09-24 04:03:29.970 spid23s
Starting up database 'Billing_Snap'.
2014-09-24 04:03:29.970 spid24s
Starting up database 'DBA'.
2014-09-24 04:03:30.000 Server
A self-generated certificate was successfully loaded for encryption.
2014-09-24 04:03:30.000 Server
Server is listening on [ 'any' <ipv6> 52328].
2014-09-24 04:03:30.000 Server
Server is listening on [ 'any' <ipv4> 52328].
2014-09-24 04:03:30.000 Server
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQL2008R2 ].
2014-09-24 04:03:30.000 Server
Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQL2008R2\sql\query ].
2014-09-24 04:03:30.010 Server
Server is listening on [ ::1 <ipv6> 52329].
2014-09-24 04:03:30.010 Server
Server is listening on [ 127.0.0.1 <ipv4> 52329].
2014-09-24 04:03:30.010 Server
Dedicated admin connection support was established for listening locally on port 52329.
2014-09-24 04:03:30.060 spid10s
CHECKDB for database 'model' finished without errors on 2014-09-20 12:00:17.583 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:30.060 spid10s
Clearing tempdb database.
2014-09-24 04:03:30.140 Server
The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/BPWDB046.bcbio.org:SQL2008R2 ] for the SQL Server service.
2014-09-24 04:03:30.140 Server
The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/BPWDB046.bcbio.org:52328 ] for the SQL Server service.
2014-09-24 04:03:30.140 Server
SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-09-24 04:03:30.480 spid21s
CHECKDB for database 'ReportServer$SQL2008TempDB' finished without errors on 2014-09-20 16:13:10.043 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:30.520 spid14s
2933 transactions rolled forward in database 'msdb' (4). This is an informational message only. No user action is required.
2014-09-24 04:03:30.650 spid7s
0 transactions rolled back in database 'msdb' (4). This is an informational message only. No user action is required.
2014-09-24 04:03:30.650 spid7s
Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
2014-09-24 04:03:30.770 spid14s
CHECKDB for database 'msdb' finished without errors on 2014-09-20 12:00:18.473 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:30.950 spid10s
Starting up database 'tempdb'.
2014-09-24 04:03:30.990 spid52
Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2014-09-24 04:03:31.010 spid52
Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_sqlagent_monitor'. This is an informational message only; no user action is required.
2014-09-24 04:03:31.060 spid14s
The Service Broker protocol transport is disabled or not configured.
2014-09-24 04:03:31.060 spid14s
The Database Mirroring protocol transport is disabled or not configured.
2014-09-24 04:03:31.070 spid14s
Service Broker manager has started.
2014-09-24 04:03:31.330 spid16s
CHECKDB for database 'ReportServer_MSSQLSSRSTempDB' finished without errors on 2014-09-20 12:00:39.873 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:31.500 spid20s
2 transactions rolled forward in database 'ReportServer$SQL2008' (11). This is an informational message only. No user action is required.
2014-09-24 04:03:31.960 spid7s
0 transactions rolled back in database 'ReportServer$SQL2008' (11). This is an informational message only. No user action is required.
2014-09-24 04:03:31.960 spid7s
Recovery is writing a checkpoint in database 'ReportServer$SQL2008' (11). This is an informational message only. No user action is required.
2014-09-24 04:03:32.150 spid20s
CHECKDB for database 'ReportServer$SQL2008' finished without errors on 2014-09-20 16:13:07.583 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:33.170 spid24s
CHECKDB for database 'DBA' finished without errors on 2014-09-20 16:22:41.603 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:33.600 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 1537 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:03:34.820 spid15s
CHECKDB for database 'ReportServer_MSSQLSSRS' finished without errors on 2014-09-20 12:00:32.067 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:48.290 spid13s
Recovery of database 'Billing_Rep' (8) is 1% complete (approximately 1488 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:03:49.520 spid17s
1 transactions rolled forward in database 'DW_Detail' (7). This is an informational message only. No user action is required.
2014-09-24 04:03:50.070 spid7s
0 transactions rolled back in database 'DW_Detail' (7). This is an informational message only. No user action is required.
2014-09-24 04:03:50.070 spid7s
Recovery is writing a checkpoint in database 'DW_Detail' (7). This is an informational message only. No user action is required.
2014-09-24 04:03:50.070 spid7s
Recovery completed for database DW_Detail (database ID 7) in 5 second(s) (analysis 251 ms, redo 4314 ms, undo 44 ms.) This is an informational message only. No user action is required.
2014-09-24 04:03:50.520 spid22s
CHECKDB for database 'Billing' finished without errors on 2013-04-25 18:47:20.743 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:51.620 spid17s
CHECKDB for database 'DW_Detail' finished without errors on 2014-09-20 12:00:46.917 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:03.740 spid13s
Recovery of database 'Billing_Rep' (8) is 2% complete (approximately 1493 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:13.040 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 8052 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:23.220 spid18s
Database BCBio_DW has more than 1000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
2014-09-24 04:04:23.420 spid18s
Recovery of database 'BCBio_DW' (9) is 0% complete (approximately 4664 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:25.640 spid18s
Recovery of database 'BCBio_DW' (9) is 0% complete (approximately 4954 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:25.640 spid18s
Recovery of database 'BCBio_DW' (9) is 3% complete (approximately 74 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:25.730 spid18s
Recovery of database 'BCBio_DW' (9) is 2% complete (approximately 98 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:26.000 spid18s
Recovery of database 'BCBio_DW' (9) is 12% complete (approximately 18 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:28.000 spid19s
Database ODS has more than 1000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
2014-09-24 04:04:28.350 spid19s
CHECKDB for database 'ODS' finished without errors on 2014-09-20 16:07:22.603 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:29.370 spid18s
Recovery of database 'BCBio_DW' (9) is 19% complete (approximately 24 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:31.380 spid18s
Recovery of database 'BCBio_DW' (9) is 25% complete (approximately 22 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:32.490 spid18s
Recovery of database 'BCBio_DW' (9) is 32% complete (approximately 18 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:33.150 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 9805 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:33.860 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 04:04:33.860 Logon
Login failed for user 'ETLAdmin'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.101.33]
2014-09-24 04:04:34.040 spid18s
Recovery of database 'BCBio_DW' (9) is 39% complete (approximately 15 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:35.600 spid18s
Recovery of database 'BCBio_DW' (9) is 46% complete (approximately 13 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:36.740 spid18s
Recovery of database 'BCBio_DW' (9) is 53% complete (approximately 10 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.220 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 10106 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.230 spid13s
Recovery of database 'Billing_Rep' (8) is 2% complete (approximately 2587 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.360 spid13s
Recovery of database 'Billing_Rep' (8) is 1% complete (approximately 3654 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.560 spid13s
Recovery of database 'Billing_Rep' (8) is 3% complete (approximately 1564 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:38.070 spid13s
Recovery of database 'Billing_Rep' (8) is 4% complete (approximately 1328 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:38.830 spid18s
Recovery of database 'BCBio_DW' (9) is 61% complete (approximately 8 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:40.080 spid13s
Recovery of database 'Billing_Rep' (8) is 5% complete (approximately 1268 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:40.680 spid18s
Recovery of database 'BCBio_DW' (9) is 69% complete (approximately 6 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:42.960 spid18s
Recovery of database 'BCBio_DW' (9) is 77% complete (approximately 4 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:44.870 spid18s
Recovery of database 'BCBio_DW' (9) is 85% complete (approximately 3 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:44.870 spid18s
3 transactions rolled forward in database 'BCBio_DW' (9). This is an informational message only. No user action is required.
2014-09-24 04:04:45.120 spid18s
Recovery of database 'BCBio_DW' (9) is 85% complete (approximately 3 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:46.870 spid7s
0 transactions rolled back in database 'BCBio_DW' (9). This is an informational message only. No user action is required.
2014-09-24 04:04:46.870 spid7s
Recovery is writing a checkpoint in database 'BCBio_DW' (9). This is an informational message only. No user action is required.
2014-09-24 04:04:46.870 spid7s
Recovery completed for database BCBio_DW (database ID 9) in 23 second(s) (analysis 2417 ms, redo 19227 ms, undo 1745 ms.) This is an informational message only. No user action is required.
2014-09-24 04:04:47.610 spid18s
CHECKDB for database 'BCBio_DW' finished without errors on 2014-09-20 14:02:10.680 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:47.820 spid23s
Database Billing_Snap has more than 1000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
2014-09-24 04:04:48.570 spid23s
CHECKDB for database 'Billing_Snap' finished without errors on 2014-09-20 16:13:11.037 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:52.970 spid13s
Recovery of database 'Billing_Rep' (8) is 6% complete (approximately 1247 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:05.540 spid13s
Recovery of database 'Billing_Rep' (8) is 7% complete (approximately 1224 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:17.980 spid13s
Recovery of database 'Billing_Rep' (8) is 8% complete (approximately 1202 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:22.450 spid13s
Recovery of database 'Billing_Rep' (8) is 8% complete (approximately 1196 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:22.450 spid13s
1 transactions rolled forward in database 'Billing_Rep' (8). This is an informational message only. No user action is required.
2014-09-24 04:05:22.560 spid13s
Recovery of database 'Billing_Rep' (8) is 8% complete (approximately 1196 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:22.710 spid13s
CHECKDB for database 'Billing_Rep' finished without errors on 2014-09-20 13:25:01.597 (local time). This is an informational message only; no user action is required.
2014-09-24 04:05:22.720 spid13s
0 transactions rolled back in database 'Billing_Rep' (8). This is an informational message only. No user action is required.
2014-09-24 04:05:22.720 spid13s
Recovery is writing a checkpoint in database 'Billing_Rep' (8). This is an informational message only. No user action is required.
2014-09-24 04:05:22.730 spid13s
Recovery completed for database Billing_Rep (database ID 8) in 109 second(s) (analysis 63983 ms, redo 45211 ms, undo 154 ms.) This is an informational message only. No user action is required.
2014-09-24 04:05:22.750 spid7s
Recovery is complete. This is an informational message only. No user action is required.
2014-09-24 07:00:06.930 spid53
Common language runtime (CLR) functionality initialized using CLR version v2.0.50727 from C:\Windows\Microsoft.NET\Framework64\v2.0.50727\.
2014-09-24 07:00:07.720 spid53
AppDomain 2 (mssqlsystemresource.sys[runtime].1) created.
2014-09-24 07:13:38.590 spid51
SQL Server blocked access to STATEMENT 'OpenRowset/OpenDatasource' of component 'Ad Hoc Distributed Queries' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Ad
Hoc Distributed Queries' by using sp_configure. For more information about enabling 'Ad Hoc Distributed Queries', see "Surface Area Configuration" in SQL Server Books Online.
2014-09-24 07:13:53.870 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:53.870 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:56.560 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:56.560 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:57.460 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:57.460 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:57.560 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:57.560 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:57.950 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:57.950 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:14:04.410 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:14:04.410 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:14:04.960 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:14:04.960 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:34:13.330 spid54
Error: 17053, Severity: 16, State: 1.
2014-09-24 07:34:13.330 spid54
V:\log\templog.ldf: Operating system error 112(There is not enough space on the disk.) encountered.
2014-09-24 07:34:14.430 spid54
Error: 9002, Severity: 17, State: 4.
2014-09-24 07:34:14.430 spid54
The transaction log for database 'tempdb' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

SQL server Agent Jobs High Avaialability - Crash on server 1 , automatically resumes from Secondary server

Hi All,
1)We have 2 physical Servers, where SSIS is installed (not clustered) . If machine crashes where Jobs running on server 1, then i want to automatically resumes the job from secondary server sql server job agent ?
2)Can i AUTOMATICALLY resume the job from secondary ssis server on crash of my primary ssis server ?
3)Can it resumes from the same point or we have to restart from begining ?

The functionality which you are looking for is not available in sql server as a standout feature.
You need to do this programattically.
You need to put savepoints in your ssis package/jobs where it logs the steps that it has completed and the steps that it has started. Any time the job is restarted it first has to check the logging table and see where it has reached and restart from the
step where it left off. The packages/jobs should have the ability to do so.
You can also set another job, which will always only run on the sql agent start, which particularly chceks for all jobs which would have stopped/cancelled and see if it has completed or has stopped in between. This will make sure that if sql fails over
or there is a restart of the agent all the jobs which were cancelled would be restarted.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com
This seems to be one of the solutions but as already mentioned by others you have to build this logic - you won't get this functionality out of the box.
Sarabpreet Singh Anand
SQL Server MVP Blog ,
Personal website
This posting is provided , "AS IS" with no warranties, and confers no rights.
Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

Management Studio crashing on local SQL Server console

Unable to start the SQL Server Management Studio on the SQL Server 2012 running on Windows Server 2012 and 2012 R2
We have a number of SQL Servers deployed and in the last month all instances of the SSMS have stopped working with the following error message
Problem signature:
Problem Event Name:                        APPCRASH
Application Name:
Ssms.exe
Application Version:                           2011.110.3000.0
Application Timestamp:                     5081c1cd
Fault Module Name:                          ntdll.dll
Fault Module Version:                        6.3.9600.17476
Fault Module Timestamp:                  54516af9
Exception Code:
c000007b
Exception Offset:
000a36e5
OS Version:
6.3.9600.2.0.0.272.7
Locale ID:
1033
Additional Information 1:                  1abe
Additional Information 2: 1abee00edb3fc1158f9ad6f44f0f6be8
Additional Information 3:                  1abe
Additional Information 4:                  1abee00edb3fc1158f9ad6f44f0f6be8
We have done the following to resolve this without success:
Run a repair from the installation package
Uninstalled SSMS and reinstalled
Copied in another ntdll.dll

This what is generated in the log when trying to start the application:
Date,Source,Severity,Message,Category,Event,User,Computer
01/16/2015 09:39:58,Windows Error Reporting,Information,Fault bucket <c/> type 0<nl/>Event Name: APPCRASH<nl/>Response: Not available<nl/>Cab Id: 0<nl/><nl/>Problem signature:<nl/>P1: Ssms.exe<nl/>P2: 2011.110.3000.0<nl/>P3:
5081c1cd<nl/>P4: ntdll.dll<nl/>P5: 6.2.9200.17046<nl/>P6: 53b485c4<nl/>P7: c000007b<nl/>P8: 00078c9e<nl/>P9: <nl/>P10: <nl/><nl/>Attached files:<nl/><nl/>These files may be available here:<nl/>C:\Users\felgersma\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Ssms.exe_89a64aa0912742cdc59239b0e49f3eea1441adb7_93419cf8<nl/><nl/>Analysis
symbol: <nl/>Rechecking for solution: 0<nl/>Report Id: af322b86-9da6-11e4-9418-ac162d73da9f<nl/>Report Status: 2048<nl/>Hashed bucket:,(0),1001,,cvcnt42
01/16/2015 09:39:56,Application Error,Error,Windows cannot access the file for one of the following reasons: there is a problem with the network connection<c/> the disk that the file is stored on<c/> or the storage drivers installed on this
computer; or the disk is missing. Windows closed the program SQL Server Management Studio because of this error.<nl/><nl/>Program: SQL Server Management Studio<nl/>File: <nl/><nl/>The error value is listed in the Additional Data
section.<nl/>User Action<nl/>1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.<nl/>2. If the file still cannot be accessed and<nl/>
- It is on the network<c/> your network administrator should verify that there is not a problem with the network and that the server can be contacted.<nl/>
- It is on a removable disk<c/> for example<c/> a floppy disk or CD-ROM<c/> verify that the disk is fully inserted into the computer.<nl/>3. Check and repair the file system by running CHKDSK. To run CHKDSK<c/> click Start<c/>
click Run<c/> type CMD<c/> and then click OK. At the command prompt<c/> type CHKDSK /F<c/> and then press ENTER.<nl/>4. If the problem persists<c/> restore the file from a backup copy.<nl/>5. Determine whether other
files on the same disk can be opened. If not<c/> the disk might be damaged. If it is a hard disk<c/> contact your administrator or computer hardware vendor for further assistance.<nl/><nl/>Additional Data<nl/>Error value: 00000000<nl/>Disk
type: 0,(100),1005,,cvcnt42
01/16/2015 09:39:56,Application Error,Error,Faulting application name: Ssms.exe<c/> version: 2011.110.3000.0<c/> time stamp: 0x5081c1cd<nl/>Faulting module name: ntdll.dll<c/> version: 6.2.9200.17046<c/> time stamp: 0x53b485c4<nl/>Exception
code: 0xc000007b<nl/>Fault offset: 0x00078c9e<nl/>Faulting process id: 0x2384<nl/>Faulting application start time: 0x01d031b36fa19f2f<nl/>Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Ssms.exe<nl/>Faulting
module path: C:\Windows\SYSTEM32\ntdll.dll<nl/>Report Id: af322b86-9da6-11e4-9418-ac162d73da9f<nl/>Faulting package full name: <nl/>Faulting package-relative application ID:,(100),1000,,cvcnt42
01/16/2015 09:35:02,Windows Error Reporting,Information,Fault bucket <c/> type 0<nl/>Event Name: APPCRASH<nl/>Response: Not available<nl/>Cab Id: 0<nl/><nl/>Problem signature:<nl/>P1: Ssms.exe<nl/>P2: 2011.110.3000.0<nl/>P3:
5081c1cd<nl/>P4: ntdll.dll<nl/>P5: 6.2.9200.17046<nl/>P6: 53b485c4<nl/>P7: c000007b<nl/>P8: 00078c9e<nl/>P9: <nl/>P10: <nl/><nl/>Attached files:<nl/><nl/>These files may be available here:<nl/>C:\Users\felgersma\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Ssms.exe_89a64aa0912742cdc59239b0e49f3eea1441adb7_9d291751<nl/><nl/>Analysis
symbol: <nl/>Rechecking for solution: 0<nl/>Report Id: fb97f994-9da5-11e4-9418-ac162d73da9f<nl/>Report Status: 2048<nl/>Hashed bucket:,(0),1001,,cvcnt42

SQL Server 2012 Management Studio Crashed when opening the application

Hi,
I had installed SharePoint 2013 with SQL Server 2012 on a single server environment a couple of months ago. Both the tools were working fine. But today morning i found that when opening SQL Server 2012 Management Studio it displays a pop-up message as attached
below:
Event Log:
Faulting application name: Ssms.exe, version: 2011.110.3000.0, time stamp: 0x5081c1cd
Faulting module name: Ssms.exe, version: 2011.110.3000.0, time stamp: 0x5081c1cd
Exception code: 0xc0000005
Fault offset: 0x00004b89
Faulting process id: 0x2b0c
Faulting application start time: 0x01cf54780a2efde8
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Ssms.exe
Faulting module path: C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Ssms.exe
Report Id: 47e02c36-c06b-11e3-946b-00155d040605
Faulting package full name:
Faulting package-relative application ID:
Server Details:
Windows Server 2012 Standard
MS SharePoint 2013
MS SQL Server 2012
IIS 8.0
If anyone has faced the same problem or has a workaround, please share!
Thanks

Hello,
Applying Service Pack 1 for SQL Server 2012 may solve this issue.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Unable to run sql server 2012 setup

Hi All,
I installed SharePoint 2013 on Application Server and Database(Sql Server 2012) on another server. But for reporting application I need to install some components of SQL on Application Server as well. When I try to run the installer it crashes and
shows this below dialog box.
When I debug this I get the below error.
I saw some suggestions saying it won't work with Remote Desktop so directly connected the monitor to the server and tried to install but nothing works again. Let me know if I am doing anything wrong.
Thanks,

Hi,
Did you install the .net framework 4.0?
Meanwhile, for the SQL issue, i think you may ask in SQL forums:
http://social.technet.microsoft.com/Forums/sqlserver/en-US/home?category=sqlserver
Regards.
Vivian Wang

E$ Table in SQL Server - creating issues

Hi All,
After a successful run of an ETL SCD Type2, the E$ table is craeted in the SQL Server but it is not deleted after the run even when it is successful, the second time I run it it causes a failure because of that, how do I automatically delete it after a succesful run, I understand the error table being there after a failure, so we investigate teh cause and then manually delete it. IS tehre a way to automatically delete it after a successful run.
Thanks for your time and help.

Hi,
When you say deleted", do you mean :
- DROPPED (= destructed, a droped table doesn't existe anymore)
- DATA DELETED (= the table is still here but the records are deleted)
By default, the CKM doesn't *drop* the error table. You can activate the "drop error table" option in the "control" tab of your interface. If so, the E$ table will be dropped (=destructed) at the BEGINNING of the interface. The E$ table is NEVER droped at the end of an interface (otherwise, we couldn't be able to read the errors).
But it shouldn't generate crash during the step "create error table" because the flag "ignore errors" is supposed to be true in the CKM step.
And, the CKM ALWAYS delete the errors of your E$ table at the beginning of the interface. It means the errors that were rejected and stored in E$ during the last execution are deleted (... in fact, only the errors due to this interface).

How to Create a Temporary Table with SQL Server

I know you can create a temporary table in SQL Server 2000, but not quite sure how to do it in CFMX 7, i.e., does the SQL go inside a <CFQUERY dbtype="query"> tag?
I'm pulling the main set of records from an Oracle server (1st data source), but it does not contain employee names, only employee IDs. Since I need to show the employee name along with the Emp ID, I'm then pulling a list of "current" employee names from a SQL Server (2nd data source), which is the main database on our CF server.
I've got a QofQ that works fine, except it only matches EmpIDs that exist in both result sets. Employees who are no longer employed, don't match, and don't display. Since I can't do a LEFT OUTER JOIN with a QofQ, what I need to do is get the records from the Oracle server into the SQL Server. Preferably in a temporary table.
I was hoping if I could get those Oracle records written to a temp table on the main SQL Server, in same database as the Employee Name table, I could then write a normal <CFQUERY> that uses a LEFT OUTER JOIN.
I think I could probably write a Stored Procedure that would execute the SQL to create the temporary table, but am trying to avoid having to write the SP, and do it the simplest way.
This query will be a program that can be run hundreds of times per day, with a form that allows users to select date ranges, locations, and other options. That starts the queries, which creates the report. So I just need the temp table to exist only until all the SQL has run, and the <CFOUTPUT> has generated a report.
If the premise is right, I just need some help with the syntax for creating a SQL Server temp table, when you want to write records to it from an external data source. I'm trying the following, but getting an error:
<CFQUERY name="ITE_Temp" datasource="SkynetSQL">
CREATE TABLE #MyTemp
(   INSERT INTO #MyTemp
ITE2.TrueFile char (7) NOT NULL,
ITE2.CountOfEmployee int NULL,
ITE2.DTL_SUBTOT decimal NULL,
ITE2.EMPTYPE char (3) NULL,
ITE2.ARPT_CD char (3) NULL
</CFQUERY>
So I actually created a permanent table on the SQL Server, and wrote the below SQL, which does work, and does write the records to table. I can then write another CFQUERY with a LEFT OUTER JOIN, and get all the records, including those that don't have matching employee name:
<CFQUERY datasource="SkynetSQL">
<CFLOOP index="i" from="1" to = "#ITE2.RecordCount#">
INSERT INTO ITE_Temp
   (FullFile,
   EmployeeCount,
   DTL_Amount,
   EmployeeType,
   station)
VALUES ('#ITE2.TrueFile[i]#',
   #ITE2.CountOfEmployee[i]#,
   #ITE2.DTL_SUBTOT[i]#,
   '#ITE2.EMPTYPE[i]#',
   '#ITE2.ARPT_CD[i]#')
</CFLOOP>
</CFQUERY>
But, I hate to have to create a table and physically write to it. For one, it seems slower, and doing it in temp would be in memory, and probably much faster, correct? Is there some way to code the above, so that it does something similar, but in a TEMPORARY TABLE?   If I can figure out how to do this, I can pull data from multiple data sources and servers, and using SQL Server temp tables, work with the data as if it was all on the same SQL Server, and do some cool reports.
Everything I've done for the past few years, has all been from data from a single source, whether SQL Server, or another server. Now I need to start writing reports where data can come from 3 or 4 different servers, and be able to do joins (inner and outer). Thanks for any advice/help. Much appreciated.
Gary

While waiting to hear back, I was able to write the query results from an outside Oracle server, to a table on the local SQL Server, and do the LEFT OUTER JOIN required for the final query and report to work. That was with this syntax:
<CFQUERY name="AddTableRecords" datasource="MyTable">
TRUNCATE TABLE ITE_Temp
<CFOUTPUT query="ITE2">
INSERT INTO ITE_Temp
(FullFile,EmployeeCount,DTL_Amount,EmployeeType,station)
VALUES
('#TrueFile#', #CountOfEmployee#, #DTL_SUBTOT#, '#EMPTYPE#', '#ARPT_CD#')
</CFOUTPUT>
</CFQUERY>
However, I was not able to write to a temporary table AND read the results. I got the syntax to run to write the above results to a temporary table. But when I tried to read and output the results from the temp table, I got an error. Also, it wouldn't take the single "#" (local) only the global "##" table var, using this syntax. Note that if I didn't have the DROP TABLE in the beginning, the 2nd time you run this query, you get an error telling you the table already exists.
<CFQUERY name="ITE_Temp2" datasource="MyTable">
DROP TABLE ##MyTemp2
CREATE TABLE ##MyTemp2
FullFile char (7) NOT NULL,
EmployeeCount int NULL,
DTL_Amount decimal NULL,
EmployeeType char (3) NULL,
station char (3) NULL
<CFOUTPUT query="ITE2">
INSERT INTO ##MyTemp2 VALUES
'#ITE2.TrueFile#',
#ITE2.CountOfEmployee#,
#ITE2.DTL_SUBTOT#,
'#ITE2.EMPTYPE#',
'#ITE2.ARPT_CD#'
</CFOUTPUT>
</CFQUERY>
So even though the above works, I could use some help in reading/writing the output. I've tried several things similar to below, but they don't work. It't telling me ITE_Temp2 does not exist. It's not easy to find good examples of creating temporary tables in SQL Server.
<CFQUERY name="QueryTest2" datasource="SkynetSQL">
SELECT *
FROM ITE_Temp2
</CFQUERY>
<CFOUTPUT query="ITE_Temp2">
Output from Temp Table<br>
<p>FullFile: #FullFile#, EmployeeCount: #EmployeeCount#</p>
</CFOUTPUT>
Thanks for any help/advice.
Gary.

Calling all SQL Server users! May TechNet Gurus announced!

The results for May's
TechNet Guru competition have been posted!
http://blogs.technet.com/b/wikininjas/archive/2014/01/16/technet-guru-awards-december-2013.aspx
Congratulations to all our new Gurus for May!
We will be interviewing some of the winners and highlighting their achievements, as the month unfolds.
Post your JUNE contributions here:
http://social.technet.microsoft.com/wiki/contents/articles/24692.technet-guru-contributions-for-june-2014.aspx
Read all about June's competition, hopefully in a stickied post, at the top of this forum.
Below is a summary of the medal winners for May. The last column being a few of the comments from the judges.
Unfortunately, runners up and their judge feedback comments had to be trimmed from THIS post, to fit into the forum's 60,000 character limit, however
the full version is available on TechNet Wiki.
Some articles only just missed out, so we may be returning to discuss those too, in future blogs.
BizTalk Technical Guru - May 2014
Peter Lindgren
BizTalk 2010: Call SSO from Orchestration
TGN: "I bet a few people will love you for this, I often see this question at the forums, and you answered it well. Good work!"
Mandi Ohlinger: "Great topic and great explanation. It also makes SSO seem less scary :)"
Sandro Pereira: "Very useful sample, well explained with all the necessary code "
boatseller
BizTalk: Using an Orchestration Sync or Async
Sandro Pereira: "Good sample provide by boatseller and well explained."
TGN: "Hey, great work man! This is a well done article and I love it!"
Steef-Jan Wiggers
Exposing data through BizTalk Service Hybrid Connections
Sandro Pereira: "Nice article with a good overview about BizTalk Service Hybrid Connections and how you can configure them."
TGN: "Good article, well explained and good pictures. Again Steef-Jan, you know what you're doing!"
Mandi Ohlinger: "Nice set-up overview. "
Forefront Identity Manager Technical Guru - May 2014
Sheldon.Jaquay
Forefront Identity Manager - RCDC - Regular Expression
AM: "Great contribution! Option C is clever, and the other examples are also a useful reference. Thanks for sharing your work with the community."
Ed Price: "Nice short article. Great topic, and great blend of code, color, and images!"
Søren Granfeldt: "Nice with a little focus on RegEx with FIM and good help for people wanting to have the portal be just a little more company specific"
GO: "Thanks for the article, but the images weren't clear enough."
Scott Eastin
Installing Oracle MA for FIM R2 on Windows 2012
GO: "EX-CE-LL-EN-T article!"
AM: "Very nice article with clear step-by-step instructions - thanks for putting this together. "
Ed Price: "I love the sections with numbered bullets at the end. They're very clear and easy to read!"
Microsoft Azure Technical Guru - May 2014
João Sousa
Microsoft Azure - Remote Debbuging How To?
GO: "Clever. Well Explained and written. Thanks! You absolutely deserve the GOLD medal."
Ed Price: "Fantastic topic and great use of images!"
Alex Mang
The Move to the New Azure SQL Database Tiers
Ed Price: "Great depth and descriptions! Very timely topic! Lots of collaboration on this article from community members!"
GO: "great article but images are missing"
Alex Mang
Separating Insights Data In Visual Studio Online
Application Insights For Production And Staging Cloud Services
Ed Price: "Good descriptions and clarity!"
GO: "great article but images are missing"
Microsoft Visio Technical Guru - May 2014
Mr X
How to export your Orchestrator Runbooks to Visio and Word
Ed Price: "A basic tip, but very helpful. Good job!"
GO: "Thanks for that!"
SR: "Nice "How To" article explaining the basic steps."
AH: "This article is to the point takes a simple tasks and describes it accurately.
SharePoint 2010 / 2013 Technical Guru - May 2014
Dan Christian
Build a loop workflow using SharePoint 2010
Jinchun Chen: "Excellent article. Personally speaking, the biggest challenge is SharePoint Designer workflow is “while-loop”. Many customers had the same scene as this article set. I am sure they are like this article.
Benoît Jester: "An AWESOME, huge, detailed article by Dan. Did I mention the videos? Thanks Dan!"
GO: "Great article Dan! Thanks!"
Margriet Bruggeman: "Detailed explanation which I admire, but wouldn't be using a vs workflow be more logical in this case?"
Geetanjali Arora
Export User Profile Properties using CSOM
Benoît Jester: "Great article on this new SharePoint 2013 development capability. I appreciate the code explanations."
GO: "This is a great article. Love the way how you explain it."
Margriet Bruggeman: "I will use this piece of code in the future!"
Jinchun Chen: "Nice. How about customized properties? It would be nice more, if a CSOM script version can be attached. "
Inderjeet Singh
Unable
to restore site collection issue
GO: "Simple. Good Written. Clear and Clever. Great article."
Margriet Bruggeman: "Quite handy reference for this particular problem"
Benoît Jester: "Good explanation on the site collection deletion process."
Small Basic Technical Guru - May 2014
Philip Conrod
Programming Home Projects with Microsoft Small Basic: Chapter
1: Writing Programs Using Small Basic
RZ: "Very systematic introduction."
Ed Price: "Good overview article that covers all the basics!"
Michiel Van Hoorn: "Nice introduction into the history of Basic. Needs to be updated to reflect current support for Windows version (Windows NT? LOL )"
Philip Conrod
Programming Home Projects with Microsoft Small Basic: Chapter 6: Flash
Card Math Quiz Project
Michiel Van Hoorn: "This article (or book chapter) is excellent material to learn how to envision, design and build your program. The actual example program is also very usable."
Ed Price: "I love how this tutorial keeps building on itself as it goes!"
Nonki Takahashi
Small Basic: Variable
RZ: "Very nice explanation of the concept of variables!"
Michiel Van Hoorn: "Clear explanation and not frills"
Ed Price: "Great article with fantastic formatting!"
SQL BI and Power BI Technical Guru - May 2014
Durval Ramos
SSIS - Event Handling with "OnError" ou "OnTaskFailed"
Ed Price: "The images are very helpful! Could use a grammar pass. Great descriptions!"
GO: "This article has everything. A conclusion, reference, see also, other languages section. everybody should write actually like this."
NN: "An interesting topic and article but unfortunately a bit hard to understand due to grammar problems"
PT: "This is a good article on a useful topic. Please have your article reviewed and edited for proper language."
S Kamath
Expansion of Time dimension in Analysis Service
PT: "Your article is concise and to the point, and contains useful information. It would be good to conclude with a short summary and perhaps compare this technique to others, discussing best practices."
Ed Price: "Good details on Time Dimension. The images help us understand as we go."
GO: "I like this one, but something is missing. Do not know what, but I had a blast reading the other two's. Does not mean that this one is bad, but there is something missing, maybe my knowledge..."
NN: "Good article, but seems to be missing conclusion. It will also benefit from adding See Also section"
Sherry Li
SSAS – Ignore unrelated dimension or not
NN: "Good and interesting article based on the blog"
GO: "Wonderful article!"
PT: "This is an important topic and contains helpful information but this is a simple topic that can be explained in fewer words. I found this article to be overly detailed and hard to read. I suggest having it reviewed and edited for
proper language."
Ed Price: "Good descriptions. Could be shorter. Good use of images!"
SQL Server General and Database Engine Technical Guru - May 2014
Shanky
Curious Case Of Logging In Online and Offline Index Rebuild In Full Recovery
Model
Jinchun Chen: "Good article. Thank you!"
GO: "One of the best Wiki Articles ever! Thanks buddy!"
DRC: "-- This is a great article which provides in-depth information on internals of Online & Offline rebuild index and Transaction logging. -- The following statement need to be re-written for more clarity. “The less logging can be
attributed to the fact that no information about page allocation is logged information about de-allocation is logged please see below figure 13. Also if you compare amount of record returned in this case we had output containing just 64 rows while offline
index rebuild had ____ rows.” -- Overall, a great article, thoroughly enjoyed reading it."
NN: "Very interesting article, another great contribution by Shanky"
Ed Price: "Thorough descriptions and great solution! Good article!"
Uwe Ricken
SQL Server: Be aware of the correct data type for predicates in queries
Ed Price: "Incredibly well formatted! Great breakdown of sections!"
GO: "Whoo, this is a wonderful article!"
DRC: "-- This article explains the Query execution behaviour when the Query is not optimally written which could cause increased execution time. Great article. -- This topic is clearly explained and documented using a simple example and
sample output which is easy is understand. -- Simple, very well written and great article to read. "
NN: "Very good, easy to understand article and important information to know to all SQL Server developers"
System Center Technical Guru - May 2014
Mr X
Central Management of DSRM password on Domain Controllers using Orchestrator
Ed Price: "The images really carry you through this article. Great execution!"
GO: "Great article. I like your article Mr X! Thanks for your passion!"
Kevin Holman: "Nice to see real world examples of Orchestrator in action solving problems that all customers have. This was very simple, but provides an excellent solution."
W P Chomak
System Center Operations Manager 2012 R2 - Customizing E-Mail Notifications
AB: "Easy reading info that can help many"
Ed Price: "Short and sweet. An incredibly valuable topic and needed addition to the Wiki!"
GO: "Clever and well written. Thanks"
Christoffer S
System Center Configuration Manager 2012 R2 - Install applications in a task sequence based on AD-Groups
Ed Price: "Good mix of code, images, and information. Could use more in-depth descriptions. Great article!"
GO: "Clear and simple! Thank you!"
Transact-SQL Technical Guru - May 2014
Naomi N
T-SQL: Random Equal Distribution
Jinchun Chen: "Nice."
JS: "The crucial thing about such a procedure is to check the data before the randomization and afterwards. You might encounter situations where "John Smith" and "John Meyers" might have exchanged their First names
which is technically correct, but logically and obviously wrong. So make sure that there is one additional check afterwards that makes sure that eventual privicy concerns will not survive the random process. Normally this would not happen, but I have already
checked this is one of my older blog entries, where we exactly had that problem obfuscating data to make that operational and live data will not be recognized afterwards. http://blogs.msdn.com/b/jenss/archive/2009/04/08/when-is-random-random-enough.aspx In
addition to this some attributes are sticky to each other like gender and First Name. You also have to make sure that your distribution might change statistically in relation to other attributes."
Richard Mueller: "Very instructive. Perhaps the See Also section should have more links."
Ed Price: "Great formatting and topic! Could benefit from more descriptions. Great article!"
GO: "Naomi, your article is nice. Simple to understand the 'problem' and execute the 'solution""
Manoj Pandey: "Nice article with a different way to resolve a given problem. I think this can also be done by using NTILE() function. I've added the code in comments section."
Rogge H
Extending SYS.Geometry to Utilize Temporal Data
GO: "Great article, I enjoyed reading it. Thank you"
Manoj Pandey: "I like the idea, but it took me some more time to understand the overall logic as I'm new to Geo datatypes, Thanks."
JS: "For me not using this sort of things regularly, I don't see the problem and the benefit. I have no doubt that this is a brilliant explanations how to cope with a problem, but for me this is missing yet the red line. More pictures
would be helpful describing the problem and outlining the results produced."
Richard Mueller: "Needs more explanation, and perhaps an example. There should be links to relevant references."
Ed Price: "Good job on the opening descriptions! Could benefit from breaking up and explaining the code more. Images and references would be helpful. Good article!"
Hasham Niaz
DataCleanUp() Function Implementation in MS SQL Server
Jinchun Chen: "Good."
JS: "-Does actually not work for Case senstive areas where I want to remoce certain Upper/lower case characters. This might be not interesting for some people, but is extremely important and relevant to other people. The limitation is
that I can´t pass multiple values to be removed from the string, right ? Could this be implemented as well as many people wash out their data from unused / unimportant control characters. "I have tested it on a table which has got more than 11 Million
rows and it executed fine returning the correct results. Since this is a scalar function you will notice decrease in performance." Once you want to maintain the old data and keep the new cleaned up one seperately, you could suggest something like persisting
the data in a computed column which could be indexed and then help improving the performance. This would not be the case for any adhoc queries though."
Richard Mueller: "Very clever and also very useful. There should be links to references, for example to explain the PATINDEX function."
Ed Price: "Great job on this article! Very clear and well executed! See JS's comments for some thoughts about what's possible. Great article!"
Manoj Pandey: "A good utility Function that I can use and tweak for my future needs, Thanks."
Jaliya Udagedara
Calling WCF Service from a Stored Procedure in Microsoft SQL Server 2012
GO: "Gold Winner. For sure!"
Ed Price: "Amazing article! The depth, images, and code formatting make this fantastic!"
NN: "Great article, thorough explanations, great interaction in the comments - very useful tutorial"
Søren Granfeldt: "Nice work."
João Sousa
ASP.NET MVC 5 - Bootstrap 3.0 in 3 Steps
GO: "Thanks for that great article"
Ed Price: "Great formatting! Good use of images!"
NN: "Nice introduction to Bootstrap in ASP.MVC project"
Søren Granfeldt: "Just a little more technical explanation would be nice"
Critical_stop
Using 64-bit shortcuts from a 32-bit application
NN: "Good and short article, right to the point"
Søren Granfeldt: "Mixing and matching 32/64 bit always seems to give people a hassle. This will help those having issues."
GO: "good one!"
Ed Price: "Good article. Short and sweet."
Wiki and Portals Technical Guru - May 2014
XAML guy
TechNet Guru Competition: Judge System Explanation
GO: "No one could do it beter than you Pete! Thanks!"
Richard Mueller: "Excellent explanation of the judging system. Perhaps could use a See Also section."
Ed Price: "Good quote from Shanky in the comments, "Awesome....Kudos to your for your beautiful work" -- Great job!"
NN: "Very good article. It may also benefit from See Also section"
Payman Biukaghazadeh
TechNet Wiki Persian Council
GO: "Go Persion GOOO!"
Richard Mueller: "The Persian Council is an excellent idea. The link to "How to Write an Article" should be in a See Also section, along with other articles."
NN: "Great article, missing a link to other portals and councils pages"
Ed Price: "Thank you to Payman and the Persian community for jumping in! The Wiki is warm!"
Durval Ramos
Wiki: Best Practices for building TechNet Wiki Portals
Ed Price: "Fantastic job from Durval on helping us standardize the portals!"
NN: "Good article, but unfortunately a bit hard to read and understand due to bad grammar. "
Richard Mueller: "Excellent and important topic. Grammar still needs work. I like the links and See Also."
Windows Phone and Windows Store Apps Technical Guru - May 2014
Sara Silva
Authentication using Facebook, Google and Microsoft account in WP8.0 App (MVVM)
Ed Price: "Great article! Great code formatting and good use of code comments for descriptions of what your code's doing! Could be improved by breaking out the code with more descriptions in the article (in addition to
the code comments). Very in-depth article! "
Peter Laker: "An excellent article, pulling together all the bits you need to make this happen"
SubramanyamRaju.B
WindowsPhone Facebook Integration:How to post message/image to FaceBook Fan
Page(C#-XAML)
Ed Price: "Good topic! Code blocks would help with the formatting. Good job on this article!"
Peter Laker: "Love this, very useful to many I'm sure, thanks!"
Saad Mahmood
Creating a custom control in Expression Blend with Custom Properties (WindowsPhone
& Store)
Ed Price: "This has a good mix of descriptions and clarity! The images help a lot!"
Peter Laker: "A nice introduction to our beloved Blend. Great work!"
Windows Presentation Foundation (WPF) Technical Guru - May 2014
Magnus (MM8)
WPF/MVVM: Merging Cells In a ListView
KJ: "Ah the collectionViewSource -- never used it myself but this looks like a good reference article if I ever needed to..."
GO: "Thank you!"
Ed Price: "Great formatting and good descriptions. Short and sweet! Another fantastic entry from Magnus!"
Peter Laker: "Thank you again Magnus"
Windows Server Technical Guru - May 2014
Mr X
How to implement User
Activity Recording for AD-Integrated Critical Servers by combining the use of Group Policy, Powershell and Orchestrator
Philippe Levesque: "Really good information and detailed step."
JH: "brilliant, love how it combines different technologies to achieve a solution, clearly written and well illustrated."
JM: "Another excellent article, thanks again for your many great contributions"
Richard Mueller: "Very creative solution. Great to have such detailed steps and images."
GO: "I like the conclusion. Thanks"
Mr X
How Domain Controllers are located in Windows
GO: "Super article Mr X! Merci!"
JM: "Yet again, excellent article."
Richard Mueller: "Good documentation. An explanation of how the priorities and weights are determined would help. A See Also section would also help."
Philippe Levesque: "Good "In deep" information. Good to know to help diagnose computer problem in AD's site."
JH: "another good article, great diagrams. Some repetition but it does help clarify a complex issue. "
Mahdi Tehrani
Detailed Concepts:Secure Channel Explained
JH: "great article. This fills an important gap in this content space. Editing is a little rough, but diagrams and explanations are clear."
JM: "This is a very good article, however you need to provide more detail in the section on how to fix a broken Channel."
Richard Mueller: "Excellent topic. Grammar needs work. Good images. Could use a See Also section."
Philippe Levesque: "Really good explanation of the secure's channel, I like the debugging step included ! "
GO: "Thanks for this, not everybody know about secure channel."
As mentioned above, runners up and their judge feedback were removed from this forum post, to fit into the forum's 60,000 character limit.
A great big thank you to EVERYONE who contributed an article to last month's competition.
Hopefully we will see you ALL again in this month's listings?
As mentioned above, runners up and comments were removed from this post, to fit into the forum's 60,000 character limit.
You will find the complete post, comments and feedback on the
main post.
Please join the discussion, add a comment, or suggest future categories.
If you have not yet contributed an article for this month, and you think you can write a more useful, clever, or better produced wiki article than the winners above,
here's your chance! :D
More about the TechNet Guru Awards:
TechNet Guru Competitions
#PEJL
Got any nice code? If you invest time in coding an elegant, novel or impressive answer on MSDN forums, why not copy it over to the one and only
TechNet Wiki, for future generations to benefit from! You'll never get archived again!
If you are a member of any user groups, please make sure you list them in the
Microsoft User Groups Portal. Microsoft are trying to help promote your groups, and collating them here is the first step.

Congrats to Shanky and Uwe!
SQL Server General and Database Engine Technical Guru - May 2014
Shanky
Curious Case Of Logging In Online and Offline Index Rebuild In Full Recovery
Model
Jinchun Chen: "Good article. Thank you!"
GO: "One of the best Wiki Articles ever! Thanks buddy!"
DRC: "-- This is a great article which provides in-depth information on internals of Online & Offline rebuild index and Transaction logging. -- The following statement need to be re-written for more clarity. “The less logging can be attributed
to the fact that no information about page allocation is logged information about de-allocation is logged please see below figure 13. Also if you compare amount of record returned in this case we had output containing just 64 rows while offline index rebuild
had ____ rows.” -- Overall, a great article, thoroughly enjoyed reading it."
NN: "Very interesting article, another great contribution by Shanky"
Ed Price: "Thorough descriptions and great solution! Good article!"
Uwe Ricken
SQL Server: Be aware of the correct data type for predicates in queries
Ed Price: "Incredibly well formatted! Great breakdown of sections!"
GO: "Whoo, this is a wonderful article!"
DRC: "-- This article explains the Query execution behaviour when the Query is not optimally written which could cause increased execution time. Great article. -- This topic is clearly explained and documented using a simple example and sample
output which is easy is understand. -- Simple, very well written and great article to read. "
NN: "Very good, easy to understand article and important information to know to all SQL Server developers"
Also worth a mention were the other entries this month:
SQL Server installation error Could Not Find Database Engine Startup Handle by
Shanky
Ed Price: "Wow, what an amazing article! Fantastic code formatting, great descriptions, and the images help you when you need it!"
NN: "I read this article with great interest. The funny thing is that at the same time I was reading someone was having this exact problem in UniversalThread.com forum, so I was able to refer him to this article. UPDATE. Looks like he is still
having problems"
GO: "Thank you so much!"
DRC: " -- This article -- Explains on modifying/deleting the registry keys after backup -- But it doesn't provide the level/how to back up the registry. -- We also need to warn the users that if we modify/delete the wrong registry key it might
lead to crash of SQL or even WINDOWS -- In case there are multiple instances on the same machine following this article would cause all the SQL instance to crash. -- So it would be better to contact the support team or before trying out the action steps. "
5 Top Features Your Company Can Use in SQL Server 2014 Standard Edition by Richard
Douglas
NN: "Very well written and quite interesting. Since it's originated from the blog, it has a personal touch which is more appropriate for a blog "
DRC: " -- Expand the word GA (General Availability) in the below sentence and correct the spelling mistake "it was written before the GA of SQL Server 2014" "SSD technology and a chunk of this session was on BPE" "who doesn't’t like playing
with new cool stuff!" "which doesn't’t sound as impressive" "business from the likes of Oracle et al." -- This is a good article and provides all the required information and links to Microsoft website for more details. "
Ed Price: "Fantastic topic, but it should be made more "Wiki like" and less personalized. Anybody in the community can help us do that! "
Ed Price, Power BI & SQL Server Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

CFquery crashes SQL server

Similar Messages

Maybe you are looking for