I have 90 sql servers instances on which i have to check these are accessible or not for me, but its hard to connect one by one instance via SSMS & check i am able to connect sql server or not. for that i need to create a batch file in which i can call all 90 sql instances name & which would get result me in one text file if there is any server is not accessible.

I am stuck with this as this one is only work for single sql server...sqlcmd -S server_name -E -oC:\test.txt

is anybody know how to create batch file?

Hi,

Is there some way to clear or force a rollover on files of asynchronous_file_target of an extended events session ?

Thank you!

Dennes - Se resolveu, classifique a mensagem, por favor - [http://www.bufaloinfo.com.br] NOVO DVD Segurança no ASP.NET : http://www.bufaloinfo.com.br/LearingSeriesSegurancaASPNET2.asp

Ola Hallengren's SQL Server Maintenance Solution and it is working out great. I would like to reduce the period for which database backups are retained. I believe that the job that does this is "sp_delete_backuphistory" and that the number to edit in his command is the 30 in bold, below.

sqlcmd -E -S $(ESCAPE_SQUOTE(SRVR)) -d msdb -Q "DECLARE @CleanupDate datetime SET @CleanupDate = DATEADD(dd,-30,GETDATE()) EXECUTE dbo.sp_delete_backuphistory @oldest_date = @CleanupDate" -b

I would just like confirmation from other users.

Thanks!

Nazareth Berlanga Sarcastic, annoyed tech.

I have 2 instances on 2 server for each I have the default set up and then an instance called Test.

i.e. Server1, Server2 and Server1/Test, Server2/Test

I have set up "Always on", on the default instances, and have a database called Test on both so I know that is working correctly.

As soon as the Server1/Test and Server2/Test instances are set up it automatically picks up the Always On Group and Test database.

Is it possible to stop this as I would like to use the separate instance for different databases?

Thanks

Chris

Hello All,

When I am trying to login to my default SQL 2008R2 SP2 instance in windows 2003 server via ssms, I am getting the below error

A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (.Net SqlClient Data Provider)

When I looked into the error log and i could see lot of these messages.

The server was unable to load the SSL provider library needed to log in; the connection has been closed. SSL is used to encrypt either the login sequence or all communications, depending on how the administrator has configured the server. See Books Online for information on this error message: 14 Not enough storage is available to complete this operation.

Force protocol encryption is set to off.

I am not sure what is the underlying problem. server's total RAM is 4 Gb and max_server_memory is set to 2 GB. CPU utilization is very normal at the time of issue.

I restarted the SQL service and i am able to connect to the instance, but the issue is repeating and i need to find a permanent fix.

Thanks

Hi,

This question arises during a performance test - on SQL Server 2012 with SP2.

In the following example, table has only column and that is of data type INT.

When inserted 592 records of data type INT it is doing only 1 logical read but as soon another record is inserted SP is reporting 2 logical reads. Why?

In the code, i have highlighted difference between 

statistics io - logical reads and sys.dm_exec_procedure_stats.total_logical_reads

to understand the difference between these 2 information.

set nocount on
GO
create table dbo.test_storage_and_logical_reads
(
employee_number int --primary key
)
GO

go
CREATE procedure dbo.test_sp_logical_reads
as
begin
	select 
	employee_number
	from dbo.test_storage_and_logical_reads
	order by employee_number desc
end
go

insert into dbo.test_storage_and_logical_reads 
(employee_number)
VALUES (1)
GO 592

EXEC sp_spaceused 'dbo.test_storage_and_logical_reads'


--set statistics io on
--GO

exec dbo.test_sp_logical_reads
GO
----Table 'test_storage_and_logical_reads'. Scan count 1, logical reads 1, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
---- But sys.dm_exec_procedure_stats.total_logical_reads is reporting 3 instead.

truncate table dbo.test_storage_and_logical_reads
GO

insert into dbo.test_storage_and_logical_reads 
(employee_number)
VALUES (1)
GO 593

EXEC sp_spaceused 'dbo.test_storage_and_logical_reads'

exec dbo.test_sp_logical_reads
GO
----Table 'test_storage_and_logical_reads'. Scan count 1, logical reads 2, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.
---- But sys.dm_exec_procedure_stats.total_logical_reads is reporting 4 instead.

--drop procedure dbo.test_sp_logical_reads
--drop table dbo.test_storage_and_logical_reads
GO

NB: I do understand the logical and physical reads. Thanks.

For quick review of new features, try virtual labs: http://msdn.microsoft.com/en-us/aa570323

Has anyone come across a situation where a delete statement doesn't give an error, but also doesn't delete the rows specified?

Yes the rows exist as outside the scope of the running application, we can run the same SQL and it does delete the expected rows.

• It's sql server 2005 sp4
• It's an ad-hoc delete, i.e. not inside a transaction.
• The table is accessed via a View which just cuts down the result set on one column's content.
• The underlying table has several indexes, several foreign key parents and 2 foreign key children (both children are on delete cascade).
• There are no triggers on the table.
• The client app is connecting via odbc.

A colleague rememebers something like this in sql 2000 where deletes on tables with foreign keys had problems building an execution plan, and that just failed silently, but I can't find any details of that.

Any ideas?

Thanks
-Ade

I am using sp_send_dbmail on SQL 2008 to send email. I found when I set to use multiple recepient , there is problem

for example:

mail1@mail.com,mail2@mail.com          not work!!!         only send tomail1@mail.com

mail1@mail.com;mail2@mail.com          work          send to both

what's the problem?~! before use ',' also work

Is there anything I can do for a OLEDB wait type?  

After restarting my instance, I started a DBCC checkdb on a 200 GB database that uses the spatial data type.  A couple of tables have 250 million rows.  There are no indexes on computed columns or filtered indexes.  It's been running about 2 hours and the percent complete is about 2%.  The estimated completion date (4 days from now) has been increasing by about and hour a minute.  It might be weeks before it completes.  (I'm using a db restored on my desktop - 6-core Zeon, 16 GB, and 2 SSDs - with SQL 2012 Developer SP2.  I enabled trace flags 2562 and 2549 enabled.  Compatibility on the db was changed to 2012 from 2008.) 

I looked at the wait stats and see the OLEDB wait type at almost 100%.  When I look at the activity monitor "Resource Waits", the only wait I see is Network IO - about 1 sec per sec.  "Data File IO" is at 0.0 MB/sec with response times normally at 0 ms, but can be 2 ms from time to time.  CPU use is about 10%.  My machine feels idle. 

An AVG scan recently started and just finish.  It did not seem to slow anything down or change the waits.  But that makes me wonder.  Can a real-time virus scanner be a source of the OLEDB waits?  Would it also show up as network io wait? 

Any advice that can help me find the bottleneck would be appreciated.  It would great if I could move the bottleneck to CPU or disk. 

Thanks.

Randy in Marin

What is AWE ? Enabling AWE memory for sql server 2008 r2 (instance) is a good or bad practice? If Enabled what is advantages and disadvantages ?

Thanks in Advance...

The Index maintenence job is getting failed with following message. 

Note- (I)Job owner is SA

         (II)Agent Service account is Sysadmin.

What can be the cause of failing the job. Previously the job was running successfully. Can it be any active directory issue? 

Pranshul Gupta

Actually I have joined a new company and appoint as L3,I want to take Handover.

I want to take a SQL Server DBA L3 Handover in my new company.

Is there any process pdf / website or excel which I can follow.

Thanks

My company is experiencing intermittent MSSQL crashes.  The crashes seem to lock up the entire SQL server to the point that the only thing we can do to resolve the issue is to reboot the server.

The events leading up to the crash are as follows:

1) Scribe Server runs DTS package 'ExportRealTime_Member.dts'
2) DTS package calls 'select * from ExportRealTime_Member' (ExportRealTime_Member is a view using a nested base view and the checksum() function.  It returns members that need to be updated in the Microsoft CRM system, based on checksum values.  The base view pulls data from a replicated database and the CRM database)
3) An EXCEPTION_ILLEGAL_INSTRUCTION exception is thrown.
4) We are unable to kill the process calling 'select * from ExportRealTime_Member', and the process runs forever unless we reboot the server.

We are hoping someone else has had a similar issue and can shed some light on how to prevent this from happening.

The following is found in the exception.log:

04/04/14 06:53:22 spid 83 Exception 0xc000001d EXCEPTION_ILLEGAL_INSTRUCTION at 0x000007FEC6060470
04/18/14 18:09:42 spid 82 Exception 0xc000001d EXCEPTION_ILLEGAL_INSTRUCTION at 0x000007FEC8AC046D
04/30/14 16:48:44 spid 98 Exception 0xc000001d EXCEPTION_ILLEGAL_INSTRUCTION at 0x000007FA173F046D
05/14/14 00:30:10 spid 151 Exception 0xc000001d EXCEPTION_ILLEGAL_INSTRUCTION at 0x000007FDB561046D
05/18/14 08:15:26 spid 158 Exception 0xc000001d EXCEPTION_ILLEGAL_INSTRUCTION at 0x000007FFB49F046D
05/20/14 06:05:29 spid 61 Exception 0xc000001d EXCEPTION_ILLEGAL_INSTRUCTION at 0x000007FF97DE046D
05/23/14 14:44:48 spid 192 Exception 0xc000001d EXCEPTION_ILLEGAL_INSTRUCTION at 0x000007FD00A00470
06/23/14 00:00:23 spid 96 Exception 0xc000001d EXCEPTION_ILLEGAL_INSTRUCTION at 0x000007FC2E43046D
07/26/14 14:09:50 spid 212 Exception 0xc000001d EXCEPTION_ILLEGAL_INSTRUCTION at 0x000007FC2C23046D
07/29/14 09:53:28 spid 141 Exception 0xc000001d EXCEPTION_ILLEGAL_INSTRUCTION at 0x000007FE5FC8046D

Looking in the ERRORLOG file I see the following relevent information:

2014-07-29 09:53:28.47 spid141     Using 'dbghelp.dll' version '4.0.5'
2014-07-29 09:53:28.51 spid141     ***Stack Dump being sent to D:\Program Files\Microsoft SQL Server\MSSQL11.TESTCRMSQL2012E\MSSQL\LOG\SQLDump0019.txt
2014-07-29 09:53:28.51 spid141     SqlDumpExceptionHandler: Process 141 generated fatal exception c000001d EXCEPTION_ILLEGAL_INSTRUCTION. SQL Server is terminating this process.
2014-07-29 09:53:28.51 spid141     * *******************************************************************************
2014-07-29 09:53:28.51 spid141     *
2014-07-29 09:53:28.51 spid141     * BEGIN STACK DUMP:
2014-07-29 09:53:28.51 spid141     *   07/29/14 09:53:28 spid 141
2014-07-29 09:53:28.51 spid141     *
2014-07-29 09:53:28.51 spid141     *
2014-07-29 09:53:28.51 spid141     *   Exception Address = 000007FE5FC8046D Module(sqlmin+000000000015046D)
2014-07-29 09:53:28.51 spid141     *   Exception Code    = c000001d EXCEPTION_ILLEGAL_INSTRUCTION
2014-07-29 09:53:28.51 spid141     * Input Buffer 119 bytes -
2014-07-29 09:53:28.51 spid141     *  ÿÿ      &  ÿÿÿÿ  c ff ff 0d 00 00 00 00 01 26 04 04 ff ff ff ff 00 00 63
2014-07-29 09:53:28.51 spid141     *        Ð 4ÿÿÿÿ  cH  00 00 00 00 09 04 d0 00 34 ff ff ff ff 00 00 63 48 00
2014-07-29 09:53:28.51 spid141     *      Ð 4H   S E L E 00 00 09 04 d0 00 34 48 00 00 00 53 00 45 00 4c 00 45
2014-07-29 09:53:28.51 spid141     *   C T   *   F R O M 00 43 00 54 00 20 00 2a 00 20 00 46 00 52 00 4f 00 4d
2014-07-29 09:53:28.51 spid141     *     E x p o r t R e 00 20 00 45 00 78 00 70 00 6f 00 72 00 74 00 52 00 65
2014-07-29 09:53:28.51 spid141     *   a l T i m e _ A c 00 61 00 6c 00 54 00 69 00 6d 00 65 00 5f 00 41 00 63
2014-07-29 09:53:28.51 spid141     *   c o u n t         00 63 00 6f 00 75 00 6e 00 74 00
2014-07-29 09:53:28.51 spid141     * 
2014-07-29 09:53:28.51 spid141     *
2014-07-29 09:53:28.51 spid141     *  MODULE                          BASE      END       SIZE
2014-07-29 09:53:28.51 spid141     * sqlservr                       000007F627110000  000007F62714DFFF  0003e000
2014-07-29 09:53:28.51 spid141     * ntdll                          000007FE6D4F0000  000007FE6D6ADFFF  001be000
2014-07-29 09:53:28.51 spid141     * KERNEL32                       000007FE6B180000  000007FE6B2B6FFF  00137000
2014-07-29 09:53:28.51 spid141     * KERNELBASE                     000007FE6A580000  000007FE6A673FFF  000f4000
2014-07-29 09:53:28.51 spid141     * ADVAPI32                       000007FE6B750000  000007FE6B82DFFF  000de000
2014-07-29 09:53:28.51 spid141     * MSVCR100                       00000000526B0000  0000000052781FFF  000d2000
2014-07-29 09:53:28.51 spid141     * MSVCP100                       00000000525E0000  0000000052677FFF  00098000
2014-07-29 09:53:28.51 spid141     * sqlos                          0000000052030000  0000000052036FFF  00007000
2014-07-29 09:53:28.51 spid141     * NETAPI32                       000007FE683D0000  000007FE683E4FFF  00015000
2014-07-29 09:53:28.51 spid141     * pdh                            000007FE61A80000  000007FE61ACBFFF  0004c000
2014-07-29 09:53:28.51 spid141     * opends60                       0000000052020000  0000000052027FFF  00008000
2014-07-29 09:53:28.51 spid141     * sqlmin                         000007FE5FB30000  000007FE61A70FFF  01f41000
2014-07-29 09:53:28.51 spid141     * sqllang                        000007FE5DAA0000  000007FE5FB2BFFF  0208c000
2014-07-29 09:53:28.51 spid141     * sqlTsEs                        000007FE5D210000  000007FE5DA96FFF  00887000
2014-07-29 09:53:28.51 spid141     * sqldk                          000007FE5CD90000  000007FE5D208FFF  00479000
2014-07-29 09:53:28.51 spid141     * msvcrt                         000007FE6BAF0000  000007FE6BB94FFF  000a5000
2014-07-29 09:53:28.51 spid141     * sechost                        000007FE6D4A0000  000007FE6D4E7FFF  00048000
2014-07-29 09:53:28.51 spid141     * RPCRT4                         000007FE6B440000  000007FE6B584FFF  00145000
2014-07-29 09:53:28.51 spid141     * netutils                       000007FE69230000  000007FE6923DFFF  0000e000
2014-07-29 09:53:28.51 spid141     * srvcli                         000007FE6A080000  000007FE6A0A3FFF  00024000
2014-07-29 09:53:28.51 spid141     * wkscli                         000007FE69240000  000007FE69254FFF  00015000
2014-07-29 09:53:28.51 spid141     * USER32                         000007FE6B5A0000  000007FE6B6EBFFF  0014c000
2014-07-29 09:53:28.51 spid141     * ole32                          000007FE6AFF0000  000007FE6B16DFFF  0017e000
2014-07-29 09:53:28.51 spid141     * OLEAUT32                       000007FE6BBA0000  000007FE6BC62FFF  000c3000
2014-07-29 09:53:28.51 spid141     * Secur32                        000007FE66480000  000007FE6648AFFF  0000b000
2014-07-29 09:53:28.51 spid141     * PSAPI                          000007FE6AFE0000  000007FE6AFE6FFF  00007000
2014-07-29 09:53:28.51 spid141     * WS2_32                         000007FE6B6F0000  000007FE6B747FFF  00058000
2014-07-29 09:53:28.51 spid141     * USERENV                        000007FE6A560000  000007FE6A57EFFF  0001f000
2014-07-29 09:53:28.51 spid141     * AUTHZ                          000007FE69700000  000007FE69746FFF  00047000
2014-07-29 09:53:28.51 spid141     * WINTRUST                       000007FE6A500000  000007FE6A554FFF  00055000
2014-07-29 09:53:28.51 spid141     * WINMM                          000007FE66370000  000007FE6638FFFF  00020000
2014-07-29 09:53:28.51 spid141     * GDI32                          000007FE6AB00000  000007FE6AC40FFF  00141000
2014-07-29 09:53:28.51 spid141     * combase                        000007FE6A8E0000  000007FE6AA8FFFF  001b0000
2014-07-29 09:53:28.51 spid141     * NSI                            000007FE6B360000  000007FE6B368FFF  00009000
2014-07-29 09:53:28.51 spid141     * profapi                        000007FE6A430000  000007FE6A444FFF  00015000
2014-07-29 09:53:28.51 spid141     * CRYPT32                        000007FE6A700000  000007FE6A8D0FFF  001d1000
2014-07-29 09:53:28.51 spid141     * MSASN1                         000007FE6A410000  000007FE6A425FFF  00016000
2014-07-29 09:53:28.51 spid141     * WINMMBASE                      000007FE5CD50000  000007FE5CD82FFF  00033000
2014-07-29 09:53:28.51 spid141     * SSPICLI                        000007FE6A130000  000007FE6A15CFFF  0002d000
2014-07-29 09:53:28.51 spid141     * cfgmgr32                       000007FE6A6B0000  000007FE6A6FEFFF  0004f000
2014-07-29 09:53:28.51 spid141     * DEVOBJ                         000007FE6A680000  000007FE6A6A1FFF  00022000
2014-07-29 09:53:28.51 spid141     * LOGONCLI                       000007FE699D0000  000007FE69A03FFF  00034000
2014-07-29 09:53:28.51 spid141     * SAMCLI                         000007FE6A300000  000007FE6A315FFF  00016000
2014-07-29 09:53:28.51 spid141     * CRYPTBASE                      000007FE6A1C0000  000007FE6A1C9FFF  0000a000
2014-07-29 09:53:28.51 spid141     * bcryptPrimitives               000007FE6A160000  000007FE6A1BBFFF  0005c000
2014-07-29 09:53:28.51 spid141     * instapi110                     000007FE663D0000  000007FE663DDFFF  0000e000
2014-07-29 09:53:28.51 spid141     * cscapi                         000007FE625E0000  000007FE625F0FFF  00011000
2014-07-29 09:53:28.51 spid141     * sqlevn70                       0000000051250000  00000000514C9FFF  0027a000
2014-07-29 09:53:28.51 spid141     * CRYPTSP                        000007FE69C30000  000007FE69C49FFF  0001a000
2014-07-29 09:53:28.51 spid141     * rsaenh                         000007FE698D0000  000007FE6991AFFF  0004b000
2014-07-29 09:53:28.51 spid141     * imagehlp                       000007FE6B420000  000007FE6B433FFF  00014000
2014-07-29 09:53:28.51 spid141     * ncrypt                         000007FE69E00000  000007FE69E26FFF  00027000
2014-07-29 09:53:28.51 spid141     * bcrypt                         000007FE69E30000  000007FE69E54FFF  00025000
2014-07-29 09:53:28.51 spid141     * NTASN1                         000007FE69DC0000  000007FE69DF4FFF  00035000
2014-07-29 09:53:28.51 spid141     * gpapi                          000007FE69650000  000007FE6966EFFF  0001f000
2014-07-29 09:53:28.51 spid141     * VERSION                        000007FE66350000  000007FE66358FFF  00009000
2014-07-29 09:53:28.51 spid141     * msv1_0                         000007FE69B70000  000007FE69BC2FFF  00053000
2014-07-29 09:53:28.52 spid141     * cryptdll                       000007FE69D20000  000007FE69D33FFF  00014000
2014-07-29 09:53:28.52 spid141     * kerberos                       000007FE69C50000  000007FE69D1EFFF  000cf000
2014-07-29 09:53:28.52 spid141     * schannel                       000007FE69960000  000007FE699C9FFF  0006a000
2014-07-29 09:53:28.52 spid141     * MSCOREE                        000007FE65BF0000  000007FE65C5EFFF  0006f000
2014-07-29 09:53:28.52 spid141     * mscoreei                       000007FE65B50000  000007FE65BE8FFF  00099000
2014-07-29 09:53:28.52 spid141     * CLUSAPI                        000007FE57430000  000007FE5748EFFF  0005f000
2014-07-29 09:53:28.52 spid141     * RESUTILS                       000007FE57500000  000007FE5759CFFF  0009d000
2014-07-29 09:53:28.52 spid141     * security                       000007FE66390000  000007FE66392FFF  00003000
2014-07-29 09:53:28.52 spid141     * ualapi                         000007FE663A0000  000007FE663C0FFF  00021000
2014-07-29 09:53:28.52 spid141     * ESENT                          000007FE65DE0000  000007FE6609EFFF  002bf000
2014-07-29 09:53:28.52 spid141     * SHELL32                        000007FE6C1C0000  000007FE6D49FFFF  012e0000
2014-07-29 09:53:28.52 spid141     * SHLWAPI                        000007FE6C170000  000007FE6C1BFFFF  00050000
2014-07-29 09:53:28.52 spid141     * clbcatq                        000007FE6B2C0000  000007FE6B355FFF  00096000
2014-07-29 09:53:28.52 spid141     * sqlncli11                      0000000050980000  0000000050CD2FFF  00353000
2014-07-29 09:53:28.52 spid141     * COMCTL32                       000007FE591C0000  000007FE59263FFF  000a4000
2014-07-29 09:53:28.52 spid141     * COMDLG32                       000007FE6B370000  000007FE6B410FFF  000a1000
2014-07-29 09:53:28.52 spid141     * SHCORE                         000007FE68DA0000  000007FE68E34FFF  00095000
2014-07-29 09:53:28.52 spid141     * SQLNCLIR11                     0000000050940000  0000000050977FFF  00038000
2014-07-29 09:53:28.52 spid141     * DPAPI                          000007FE69280000  000007FE69287FFF  00008000
2014-07-29 09:53:28.52 spid141     * netbios                        000007FE57110000  000007FE57119FFF  0000a000
2014-07-29 09:53:28.52 spid141     * clr                            000007FE651E0000  000007FE65B4AFFF  0096b000
2014-07-29 09:53:28.52 spid141     * MSVCR110_CLR0400               000007FE65100000  000007FE651D1FFF  000d2000
2014-07-29 09:53:28.52 spid141     * ntmarta                        000007FE66850000  000007FE6687DFFF  0002e000
2014-07-29 09:53:28.52 spid141     * mscorlib.ni                    000007FE63620000  000007FE64C19FFF  015fa000
2014-07-29 09:53:28.52 spid141     * SqlAccess                      00000000166A0000  000000001670CFFF  0006d000
2014-07-29 09:53:28.52 spid141     * clrjit                         000007FE5C480000  000007FE5C5B0FFF  00131000
2014-07-29 09:53:28.52 spid141     * BatchParser                    00000000503D0000  00000000503FAFFF  0002b000
2014-07-29 09:53:28.52 spid141     * ftimport                       0000000060000000  0000000060024FFF  00025000
2014-07-29 09:53:28.52 spid141     * MSFTE                          0000000049980000  0000000049D2DFFF  003ae000
2014-07-29 09:53:28.52 spid141     * dbghelp                        00000000507A0000  0000000050935FFF  00196000
2014-07-29 09:53:28.52 spid141     * mswsock                        000007FE69BD0000  000007FE69C2BFFF  0005c000
2014-07-29 09:53:28.52 spid141     * ntdsapi                        000007FE683F0000  000007FE68413FFF  00024000
2014-07-29 09:53:28.52 spid141     * DSPARSE                        000007FE663E0000  000007FE663EAFFF  0000b000
2014-07-29 09:53:28.52 spid141     * DNSAPI                         000007FE69A10000  000007FE69AA7FFF  00098000
2014-07-29 09:53:28.52 spid141     * rasadhlp                       000007FE66430000  000007FE66437FFF  00008000
2014-07-29 09:53:28.52 spid141     * IPHLPAPI                       000007FE66CB0000  000007FE66CD9FFF  0002a000
2014-07-29 09:53:28.52 spid141     * WINNSI                         000007FE66C90000  000007FE66C99FFF  0000a000
2014-07-29 09:53:28.52 spid141     * fwpuclnt                       000007FE66B40000  000007FE66BA0FFF  00061000
2014-07-29 09:53:28.52 spid141     * ncryptsslp                     000007FE571B0000  000007FE571C8FFF  00019000
2014-07-29 09:53:28.52 spid141     * xpsqlbot                       0000000077160000  0000000077167FFF  00008000
2014-07-29 09:53:28.52 spid141     * xpstar                         0000000076E00000  0000000076E6FFFF  00070000
2014-07-29 09:53:28.52 spid141     * ATL100                         0000000052680000  00000000526AAFFF  0002b000
2014-07-29 09:53:28.52 spid141     * SQLSCM                         0000000050750000  000000005075EFFF  0000f000
2014-07-29 09:53:28.52 spid141     * ODBC32                         000007FE57000000  000007FE570BDFFF  000be000
2014-07-29 09:53:28.52 spid141     * xpstar                         0000000076DD0000  0000000076DF4FFF  00025000
2014-07-29 09:53:28.52 spid141     * xplog70                        0000000076D90000  0000000076DA3FFF  00014000
2014-07-29 09:53:28.52 spid141     * BROWCLI                        000007FE58BA0000  000007FE58BB1FFF  00012000
2014-07-29 09:53:28.52 spid141     * xplog70                        0000000076D80000  0000000076D82FFF  00003000
2014-07-29 09:53:28.52 spid141     * DSROLE                         000007FE66EC0000  000007FE66EC8FFF  00009000
2014-07-29 09:53:28.52 spid141     * dbghelp                        0000000076510000  00000000766A5FFF  00196000
2014-07-29 09:53:28.52 spid141     *
2014-07-29 09:53:28.52 spid141     *     P1Home: FFFFFFFFFFFFFFFE: 
2014-07-29 09:53:28.52 spid141     *     P2Home: 000007FE5CD9ADAA:  7142820F08FE8040  483024448B480001  24748B4838245C8B  90C35F20C4834840  8948909090909090  20EC83485618245C 
2014-07-29 09:53:28.52 spid141     *     P3Home: 00000001E69B3930:  000007FE5FB8DC50  0000000252640AC0  00000002528149B0  006E006100000002  0000000252814060  00000001E69B3CB0 
2014-07-29 09:53:28.52 spid141     *     P4Home: 0000000000000038: 
2014-07-29 09:53:28.52 spid141     *     P5Home: 0000000000000002: 
2014-07-29 09:53:28.52 spid141     *     P6Home: 00000000000006B0: 
2014-07-29 09:53:28.52 spid141     * ContextFlags: 000000000010005F:  005AF00000003C00  00003E00005B0400  005B5800005B4400  005B900000003800  00003E00005BA400  0010B800005BE400 
2014-07-29 09:53:28.52 spid141     *      MxCsr: 0000000000001FA0: 
2014-07-29 09:53:28.52 spid141     *      SegCs: 0000000000000033: 
2014-07-29 09:53:28.52 spid141     *      SegDs: 000000000000002B: 
2014-07-29 09:53:28.52 spid141     *      SegEs: 000000000000002B: 
2014-07-29 09:53:28.52 spid141     *      SegFs: 0000000000000053: 
2014-07-29 09:53:28.52 spid141     *      SegGs: 000000000000002B: 
2014-07-29 09:53:28.52 spid141     *      SegSs: 000000000000002B: 
2014-07-29 09:53:28.52 spid141     *     EFlags: 0000000000010246: 
2014-07-29 09:53:28.52 spid141     *        Rax: 00000001E69C4174:  0000209D00000000  0000123B00000000  0000003000000000  0000000800000000  0000000000000000  E69C53D000000002 
2014-07-29 09:53:28.52 spid141     *        Rcx: 00000001E69C4F30:  000007FE5FBFD710  00000001E69C4174  00000001E69C5180  000000025267CF00  000007FE5FBFD710  00000001E69C4174 
2014-07-29 09:53:28.52 spid141     *        Rdx: 00000002528035A0:  00000001E69F4258  00000001E69F4448  00000001E69F48D8  00000001F43BE150  0000000000000000  0000000000000000 
2014-07-29 09:53:28.52 spid141     *        Rbx: 00000001E69B3930:  000007FE5FB8DC50  0000000252640AC0  00000002528149B0  006E006100000002  0000000252814060  00000001E69B3CB0 
2014-07-29 09:53:28.52 spid141     *        Rsp: 000000001332C4C8:  000007FE5FC571F3  0000000100000001  00000001E69B3930  0000000000000000  00000001E69C4060  0000000000000005 
2014-07-29 09:53:28.52 spid141     *        Rbp: 0000000000000000: 
2014-07-29 09:53:28.52 spid141     *        Rsi: 00000001E69C4060:  000007FE5FB8DC50  000000025262A4B0  00000002528149B0  000C3B0000000002  0000000252814060  00000001E69C43D0 
2014-07-29 09:53:28.52 spid141     *        Rdi: 00000002528035A0:  00000001E69F4258  00000001E69F4448  00000001E69F48D8  00000001F43BE150  0000000000000000  0000000000000000 
2014-07-29 09:53:28.52 spid141     *         R8: 00000001E69B3B10:  2401100100000000  00000000007A175C  0000000000000000  632E6C6900000000  0000000000000000  0000000000000000 
2014-07-29 09:53:28.52 spid141     *         R9: 0000000000000000: 
2014-07-29 09:53:28.52 spid141     *        R10: 0000000000000020: 
2014-07-29 09:53:28.52 spid141     *        R11: 00000000000031A8: 
2014-07-29 09:53:28.52 spid141     *        R12: 00000002528035A0:  00000001E69F4258  00000001E69F4448  00000001E69F48D8  00000001F43BE150  0000000000000000  0000000000000000 
2014-07-29 09:53:28.52 spid141     *        R13: 00000002528035A0:  00000001E69F4258  00000001E69F4448  00000001E69F48D8  00000001F43BE150  0000000000000000  0000000000000000 
2014-07-29 09:53:28.52 spid141     *        R14: 0000000000000000: 
2014-07-29 09:53:28.52 spid141     *        R15: 0000000000000001: 
2014-07-29 09:53:28.52 spid141     *        Rip: 000007FE5FC8046D:  6BBEE9086F894C2F  0000841F0F66FFFD  8D48088B48000000  83482871894C3041  00001C33840F0038  50E8184F8D48E9EB 
2014-07-29 09:53:28.52 spid141     * *******************************************************************************
2014-07-29 09:53:28.52 spid141     * -------------------------------------------------------------------------------
2014-07-29 09:53:28.52 spid141     * Short Stack Dump
2014-07-29 09:53:28.54 spid141     000007FE5FC8046D Module(sqlmin+000000000015046D)
2014-07-29 09:53:28.55 spid141     Stack Signature for the dump is 0x00000000003F0D47
2014-07-29 09:53:29.99 spid141     External dump process return code 0x20000001.
External dump process returned no errors.

2014-07-29 09:54:46.89 Server      Using 'dbghelp.dll' version '4.0.5'
2014-07-29 09:54:46.90 Server      ***Unable to get thread context for spid 0
2014-07-29 09:54:46.90 Server      * *******************************************************************************
2014-07-29 09:54:46.90 Server      *
2014-07-29 09:54:46.90 Server      * BEGIN STACK DUMP:
2014-07-29 09:54:46.90 Server      *   07/29/14 09:54:46 spid 1948
2014-07-29 09:54:46.90 Server      *
2014-07-29 09:54:46.90 Server      * Non-yielding Scheduler
2014-07-29 09:54:46.90 Server      *
2014-07-29 09:54:46.90 Server      * *******************************************************************************
2014-07-29 09:54:46.90 Server      Stack Signature for the dump is 0x000000000000025F
2014-07-29 09:54:49.13 Server      External dump process return code 0x20000001.
External dump process returned no errors.

2014-07-29 09:54:49.13 Server      Process 0:0:0 (0x864) Worker 0x0000000212DA4160 appears to be non-yielding on Scheduler 3. Thread creation time: 13051108483343. Approx Thread CPU Used: kernel 62 ms, user 70138 ms. Process Utilization 12%. System Idle 87%. Interval: 70266 ms.
2014-07-29 09:55:49.24 Server      Process 0:0:0 (0x864) Worker 0x0000000212DA4160 appears to be non-yielding on Scheduler 3. Thread creation time: 13051108483343. Approx Thread CPU Used: kernel 62 ms, user 130853 ms. Process Utilization 12%. System Idle 87%. Interval: 132604 ms.
2014-07-29 09:56:49.35 Server      Process 0:0:0 (0x864) Worker 0x0000000212DA4160 appears to be non-yielding on Scheduler 3. Thread creation time: 13051108483343. Approx Thread CPU Used: kernel 93 ms, user 190820 ms. Process Utilization 12%. System Idle 87%. Interval: 192708 ms.
2014-07-29 09:57:49.45 Server      Process 0:0:0 (0x864) Worker 0x0000000212DA4160 appears to be non-yielding on Scheduler 3. Thread creation time: 13051108483343. Approx Thread CPU Used: kernel 140 ms, user 250818 ms. Process Utilization 12%. System Idle 87%. Interval: 252814 ms.
2014-07-29 09:58:49.53 Server      Process 0:0:0 (0x864) Worker 0x0000000212DA4160 appears to be non-yielding on Scheduler 3. Thread creation time: 13051108483343. Approx Thread CPU Used: kernel 187 ms, user 310831 ms. Process Utilization 12%. System Idle 87%. Interval: 312916 ms.
2014-07-29 09:59:49.60 Server      Process 0:0:0 (0x864) Worker 0x0000000212DA4160 appears to be non-yielding on Scheduler 3. Thread creation time: 13051108483343. Approx Thread CPU Used: kernel 187 ms, user 370907 ms. Process Utilization 12%. System Idle 87%. Interval: 372986 ms.

I was able to use windbg to look at the SQLDump:

0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

FAULTING_IP:
sqlmin!CXPipe::ReleasePacket+af
000007ff`b49f046d 2f              ???

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 000007ffb49f046d (sqlmin!CXPipe::ReleasePacket+0x00000000000000af)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  0000000000000000 -- (.cxr 0x0;r)
rax=0000000000000080 rbx=0000000000000000 rcx=0000000000001858
rdx=000007ffbf856b00 rsi=0000000000000064 rdi=0000000000001858
rip=000007ffc22c2c2a rsp=000000000e919628 rbp=000000000e91a580
r8=00000000006a8e80  r9=0000000000000607 r10=000000000000000a
r11=000000000e918990 r12=0000000000000000 r13=0000000000000000
r14=000000000e919658 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000287
ntdll!NtWaitForSingleObject+0xa:
000007ff`c22c2c2a c3              ret

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

PROCESS_NAME:  sqlservr.exe

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

NTGLOBALFLAG:  0

APP:  sqlservr.exe

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

MANAGED_STACK: !dumpstack -EE
No export dumpstack found

PRIMARY_PROBLEM_CLASS:  WRONG_SYMBOLS

BUGCHECK_STR:  APPLICATION_FAULT_WRONG_SYMBOLS

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 000007ffb49f046d

STACK_TEXT:
00000000`0e91c5c8 00000000`00000000 : 00000001`c2f7b930 00000001`d7fe35a0 000007ff`b49f096e 00000000`0001ce80 : sqlmin!CXPipe::ReleasePacket+0xaf

STACK_COMMAND:  ~0s; .ecxr ; kb

FAILED_INSTRUCTION_ADDRESS:
sqlmin!CXPipe::ReleasePacket+af
000007ff`b49f046d 2f              ???

FOLLOWUP_IP:
sqlmin!CXPipe::ReleasePacket+af
000007ff`b49f046d 2f              ???

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  sqlmin!CXPipe::ReleasePacket+af

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: sqlmin

IMAGE_NAME:  sqlmin.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  50deb26e

FAILURE_BUCKET_ID:  WRONG_SYMBOLS_c000001d_sqlmin.dll!CXPipe::ReleasePacket

BUCKET_ID:  APPLICATION_FAULT_WRONG_SYMBOLS_BAD_IP_sqlmin!CXPipe::ReleasePacket+af

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:wrong_symbols_c000001d_sqlmin.dll!cxpipe::releasepacket

FAILURE_ID_HASH:  {a53ab1c7-326d-0e24-27ee-5a2dc06b5829}

Followup: MachineOwner

Hi,

 I've just had a chat with a  colleague about SQL best practices, specifically:

 - SQL DBs should be in their own folder and not on the root of the drive (even if on a separate drive)

 - NTFS indexing on the database volume should be disabled

My database is 10GB, but may grow up to 300 GB after 5 years. I'm using file groups, but not filestream.

How applicable are these best practices?

If a SQL cluster is already setup and happily running with DBs on the disk root, is it a worthwhile exercise to go back and move the DBs into a folder?

Thanks

Hi All.. Its it possible to get OS level infro from TSQL.

I want to get like the follow

Windows 2003           Standard           R2  SP2   32bits

Windows 2008           Enterprise         R2   SP1   64bits

Hi all, 

I am trying to configure Windows Cluster on windows 2008r2 and windows 2012 . the Validation went ok During the Cluster creation it erroed out . 

If there is standard documention on Creating a Cluster please povide me .. 

Thanks 

Regards

K.muthus 

k.muthus