Quantcast
Channel: SQL Server Database Engine forum
Viewing all 15930 articles
Browse latest View live
↧

SQL Server 2019 on centos shutdown frequently

July 22, 2020, 10:44 pm
$
0
0

The default virtual hard disk of CentOS virtual machine is 40 Gb. In this case, I add another 1000 GB vhd and mark it as the "/ var" directory. SQL Server 2019 Developer Edition will be installed on it according to the REHL installation script. The MSSQL data and logs will be stored in /var/opt/MSSQL.
However, SQL server will shut down and restart in up to 1 hour. And sometimes it doesn't restart as usual. From July 16, the maximum error log is 25 GB.Do you have any recommendations or best practices for CentOS with two virtual hard disks.

This program has encountered a fatal error and cannot continue running at Thu Jul 23 13:17:30 2020
The following diagnostic information is available:

         Reason: 0x00000006
        Message: Kernel bug check
        Address: 0x6ba3c5b0
     Parameters: 0x12f5c8e240
    Stack Trace:
                 file://package4/windows/system32/sqlpal.dll+0x0000000000342857
                 file://package4/windows/system32/sqlpal.dll+0x0000000000340791
                 file://package4/windows/system32/sqlpal.dll+0x000000000023C60B
                 file:///windows/System32/Drivers/Afd.sys+0x00000000000081A3
                 file:///windows/System32/Drivers/Afd.sys+0x0000000000006456
                 file:///windows/System32/Drivers/Afd.sys+0x0000000000006066
                 file://package4/windows/system32/sqlpal.dll+0x0000000000241C96
                 file://package4/windows/system32/sqlpal.dll+0x0000000000203292
                 file://package4/windows/system32/sqlpal.dll+0x00000000003818E8
                 file:///Windows/system32/mswsock.dll+0x00000000000015EC
                 file:///Windows/SYSTEM32/WS2_32.dll+0x000000000000A6BE
                 file:///binn/sqllang.dll+0x00000000000209DE
                 file:///binn/sqllang.dll+0x00000000000208A0
                 file:///binn/sqllang.dll+0x00000000000123E0
                 file:///binn/sqllang.dll+0x0000000000012555
                 file:///binn/sqllang.dll+0x000000000001B57B
                 file:///binn/sqllang.dll+0x000000000001AAA3
                 file:///binn/sqllang.dll+0x000000000001A52F
                 file:///binn/sqldk.dll+0x00000000000064C3
                 file:///binn/sqldk.dll+0x00000000000066FD
                 file:///binn/sqldk.dll+0x0000000000006A25
                 file:///binn/sqldk.dll+0x000000000002C712
                 file:///binn/sqldk.dll+0x000000000002C2DC
                 file:///binn/sqldk.dll+0x000000000002CA53
                 file:///Windows/SYSTEM32/KERNEL32.DLL+0x0000000000014414
                 file:///windows/system32/ntdll.dll+0x0000000000075541<unknown>+0x00000000A6538A00
        Process: 1243941 - sqlservr
         Thread: 1244226 (application thread 0x464)
    Instance Id: 1115e0b1-1edf-4f3b-907c-fbfcda240d15
       Crash Id: 6333d713-4f92-4d7c-8ec5-c7e0d3bc63e6
    Build stamp: a124f6613b72a676a2865df07cdee1d53ddeab4d18e3e13305275e13aa69318a
   Distribution: CentOS Linux 8 (Core)
     Processors: 8
   Total Memory: 67277205504 bytes
      Timestamp: Thu Jul 23 13:17:30 2020
     Last errno: 11
Last errno text: Resource temporarily unavailable

↧
Search

UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered. Master

July 7, 2012, 4:01 am
$
0
0

I am getting the following event every minute in the event log:

UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered. Master

+System
-Provider
[ Name] MSSQLSERVER
-EventID17053
[ Qualifiers] 49152
Level2
Task2
Keywords0x80000000000000
-TimeCreated
[ SystemTime] 2012-07-07T10:55:22.000000000Z
EventRecordID4171276
ChannelApplication
ComputerClinSQL.clinlogix.com
Security
-EventData
UpdateUptimeRegKey
5(Access is denied.)
9D420000100000000800000043004C0049004E00530051004C000000070000006D00610073007400650072000000

Binary data:

In Words

0000: 0000429D 00000010 00000008 004C0043
0008: 004E0049 00510053 0000004C 00000007
0010: 0061006D 00740073 00720065 0000

In Bytes

0000: 9D 42 00 00 10 00 00 00 B......
0008: 08 00 00 00 43 00 4C 00 ....C.L.
0010: 49 00 4E 00 53 00 51 00 I.N.S.Q.
0018: 4C 00 00 00 07 00 00 00 L.......
0020: 6D 00 61 00 73 00 74 00 m.a.s.t.
0028: 65 00 72 00 00 00 e.r...

-<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
-<System>
<ProviderName="MSSQLSERVER" />
<EventID Qualifiers="49152">17053</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreatedSystemTime="2012-07-07T10:55:22.000000000Z" />
<EventRecordID>4171276</EventRecordID>
<Channel>Application</Channel>
<Computer>ClinSQL.domain.com</Computer>
<Security/>
</System>
-<EventData>
<Data>UpdateUptimeRegKey</Data>
<Data>5(Access is denied.)</Data>
<Binary>9D420000100000000800000043004C0049004E00530051004C000000070000006D00610073007400650072000000</Binary>
</EventData>
</Event>

Appears to be with the Master database. I tried changing the SA password but did not correct the problem.

Any ideas?

↧
↧

Xevent statement completed

July 6, 2020, 12:25 am
$
0
0

I just wondering what are the differences of the following event capture ? Will it affect the actual performance when the xevent session capturing the following events?

•sqlserver.rpc_completed

•sqlserver.sql_batch_completed
•sqlserver.sp_statement_completed
↧

SQL Server 2019 BDC hardware requirement

July 8, 2020, 9:05 pm
$
0
0
what's the minimal requirement for deploying BDC on-prem ? How many physical server need ? and also the CPU/REM and disk ?
↧

ANSI_NULL vs ANSI_NULLS database setting

July 13, 2020, 9:23 am
$
0
0

What's the difference between the following ?

↧
↧

Failover cluster permission

July 23, 2020, 2:16 pm
$
0
0

as DBA (sysadmin) on SQL 2014 ( on Win 2012) FCI, I need to failover instance from one node to the other. 

I have local admin on both nodes and have access to Failover Cluster manager. 

is there any other permission needed other than local admin, in order to failover between nodes?

Thank you,

↧

Recompile or DISABLE_PARAMETER_SNIFFING

July 23, 2020, 9:39 am
$
0
0

If I would like to make the query to compile the plan for individual parameter, 

should I should recompile or DISABLE_PARAMETER_SNIFFING?

What's the different ?

↧

Copy databse from one server to another Failed

July 5, 2020, 9:44 pm
$
0
0

Copy wizard received Windows Event log:

↧
Search

Linked server access issue for windows account.

July 7, 2020, 12:03 am
$
0
0

HI Experts,

Earlier we have a linked servers in our environment configured with SQL logins, due to security issues we have changed to Windows accounts and we have done delegation of computers and svc accounts as well to make it work.

test connection is also working fine but intermittent we are getting error

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. Reason: Could not find a login matching the name provided. 

Could you please suggest for the same.

Thanks 

Raghavendra

Thanks & Regards Raghavendra Petla

↧
↧

PolyBase : Access Data in cosmodb using mongodb fails with error

July 18, 2020, 9:16 am
$
0
0

Hi All,

I am trying to access data in my azure cosmosdb  using SQL Server PolyBase (cosmosdb was created using "Azure Cosmos DB for MongoDB API) 

I am able to connect and access documents using mongo shell. However when trying to create external table, getting below error.

Searched  though PolyBase logs and could not find any useful information which can help troubleshoot the issue.

Hence posting it here.

SQL Server version : Microsoft SQL Server 2019 (RTM-CU4) (KB4548597) 

CREATE DATABASE SCOPED CREDENTIAL azure_cosmos_db_cred_using_mongodb_connect_string

WITH IDENTITY = 'username', 
Secret = 'Key';

CREATE EXTERNAL DATA SOURCE AZ_CosmosDB_mongodb_connect
WITH ( 
LOCATION = 'mongodb://comsodb.mongo.cosmos.azure.com:10255', 
CREDENTIAL = azure_cosmos_db_cred_using_mongodb_connect_string ) 


CREATE EXTERNAL TABLE Cosmosdb_doc_mongodb_test (
[_id] NVARCHAR(24) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, 
[id] NVARCHAR(100) COLLATE SQL_Latin1_General_CP1_CI_AS 
)
WITH
(

LOCATION='sgcosdb.sgcosdbcnt', 
DATA_SOURCE = AZ_CosmosDB_mongodb_connect ) 


Msg 105083, Level 16, State 1, Line 13
105083;The following columns in the user defined schema are incompatible with the external table schema for table 'Cosmosdb_doc_mongodb_test': user defined column: 'id' was not found in the external table. The detected external table schema is: ([_id] NVARCHAR(24) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL).


↧

dm_db_index_physical_stats

July 15, 2020, 1:44 am
$
0
0

are there any calculation for column avg_fragmentation_in_percent ?

So avg_fragment_size_in_pages = Page_count/fragment_count.  

↧

Error provider: Shared Memory Provider, error: 0 - The pipe has been ended.

July 24, 2020, 10:51 am
$
0
0

Hi All

  I am running the below query 

EXEC sp_MSset_oledb_prop N'Microsoft.ACE.OLEDB.12.0', N'AllowInProcess', 1
GO
EXEC sp_MSset_oledb_prop N'Microsoft.ACE.OLEDB.12.0', N'DynamicParameters', 1
GO


USE Master;
Go
SELECT * INTO [dbo].[MK03] FROM OPENDatasource('Microsoft.ACE.OLEDB.12.0',
    'Data Source=C:\Users\sarita\Documents\ABC\abc.xlsx;Extended Properties=Excel 12.0')...[Sheet1$];

But it is throwing the below error 

A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)

TCP/IP protocol is already enabled and Sql service is also running

I am using below version

Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64)   Sep 24 2019 13:48:23   Copyright (C) 2019 Microsoft Corporation  Express Edition (64-bit) on Windows 10 Enterprise 10.0 <X64> (Build 18363: ) 

How i can resolve this

↧

row records that require for later update

July 24, 2020, 3:20 am
$
0
0

Suppose a transaction require to read some values for later update . 

we should use 

HOLDLOCK

UPLOCK 

or 

Set transaction isolation level to repeatable read ?

↧
↧

Alter index reorg will also fix avg_page_used_in_percent

July 25, 2020, 12:47 am
$
0
0

I have the following table and content 

--Table Creation
Create Table IndexMaintTest
(
EmpID int,
LastName Varchar(50),
FirstName Varchar(50),
Age int
)
--Index Creation
Create Clustered Index IX_IndexMaintTest_EmpID on IndexMaintTest(EmpID)

Declare @counter int = 0 
While @counter <100000
Begin
Insert Into IndexMaintTest (EmpID,LastName,FirstName,Age) Values (cast(rand()*1000000 as int),'LastName','FirstName',0)
set @counter+=1
End

--- Random insert 

and now check the fragmentation from dm_db_index_physical_stats

is 

avg_fragmentation_in_percent is 98.8219895287958

avg_space_used_in_percent is 68

alter regor 

ALTER INDEX IX_IndexMaintTest_EmpID on dbo.IndexMaintTest REORGANIZE

and check agian 

0.381679389312977

avg_fragmentation_in_percent is 0.381679389312977

avg_space_used_in_percent is 99.4621447986163

Then I start from the begining, but this time I use REBUILD , and give 

avg_fragmentation_in_percent is 0 

avg_space_used_in_percent is 99.654163577959

And seems the results are the same . Why index reorg also fix avg_space_used_in_percent ??


avg_fragmentation_in_percent is 98.8219895287958

avg_space_used_in_percent is 68

avg_fragmentation_in_percent is 98.8219895287958

avg_space_used_in_percent is 68

avg_fragmentation_in_percent is 98.8219895287958

avg_space_used_in_percent is 68

↧

How to get the information why SQL server and windows server went hung state?

July 18, 2020, 9:32 am
$
0
0

Hello Experts,

 

SQL server is in windows cluster 2012 and it is in VM ware. Some times this server is going hung state and it is fail over to another node with out showing any error message. 

 

And there was no activity in background to at least to assume there is something. 

 

But last time i heard that it is because of Vmotion and holding sql server log files and trying to move to another vm node.  But this time there is no error message but sql went to stopped state. 

 

Is there any method to capture the information why sql server and windows server is going to hung state? 

 

 

 

This is the large error message i found it before it went to stopped state.

 

 

Cluster resource 'SQL Server' of type 'SQL Server' in clustered role 'SQL Server (MSSQLSERVER)' failed.

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

↧
Search

Scheduling a job from date to date on monthly basis - SQL Server 2014-2019

February 19, 2020, 8:34 am
$
0
0

Hi,

for a my SQL Server Agent job I need to schedule it from the 25th day to 28th day of each month, but a such schedule seems not possible to implement.

Any suggests to me to solve this issue? Perhaps, is it possible to create a schedule by a T-SQL script?

Many thanks

↧

Design question regarding non-unique Clustered Index

July 27, 2020, 2:22 pm
$
0
0

Hi,  I am trying to do performance tuning on a very large table (with 500 million+ records) and primary used by multiple reports

The current structure of the table is like this: 

[row_id]  int  ,             (surrogate key & identity column)
[year]   smallint,
[month]  smallint,
other columns .....

[row_id] is the primary key for this table but it's a non-clustered index,  There is a non-unique clustered index created for this table based on column  ([year], [month])   

I checked the query access patterns for this table  and 90% of the queries accessing this table have  [year] & [month] in where clause.   Also,  [row_id] is a column not used by any queries accessing this table (since the value is meaningless for reporting)  

They are so many rows with duplicated clustered index values and I am not sure if that's the best design for a table this big, but I also not very certain about creating a clustered index on a column that will never be used by any query.

 

At this point, I probably will do one of following two things:

1.  Keep the existing clustered index (year,month) as-is,  but drop the primary key column [row_id] from the table.  Since it's a field just taking disk space and not serving any purpose at all.   

Or

2. Make the [row_id] as the clustered index for this table,  and change the index based on (year, month) to a non-clustered index.

I believe this will be a choice (tradeoff) between read speed  vs.  insert & update speed?

What will be the read performance penalty if I changed the existing non-unique cluster index to non-clustered index?    (Read performance has higher priority over insert & update performance for this table)  

btw: this is on SQL Server 2012 (so clustered columnstore index for the entire table is not an option) 




↧
↧

SQL Server is terminating because of fatal exception c0000005 SQL sever 2016 Cluster instance

July 7, 2020, 9:23 am
$
0
0

We have SQL server 2016 standard edition cluster setup. Active active cluster setup. 

We ran into some disk errors on node two DBS02. We had replaced the failed disk and upgraded the firmware. 

After upgrade and disk replacement we were not able to failover the first Instance that is SQL01 to node DBS02

The instance SQL01 is running smoothly on DBS01 (i.e node 01)

Below error is logged in SQL logs

 SQL Server detected 4 sockets with 10 cores per socket and 20 logical processors per socket, 80 total logical processors; using 48 logical processors based on SQL Server licensing. This is an informational message; no user action is required.

2020-06-09 23:02:32.09 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2020-06-09 23:02:32.09 Server      Detected 392901 MB of RAM. This is an informational message; no user action is required.
2020-06-09 23:02:32.09 Server      Using locked pages in the memory manager.
2020-06-09 23:02:32.72 Server      Machine supports memory error recovery. SQL memory protection is enabled to recover from memory corruption.
2020-06-09 23:02:32.89 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2020-06-09 23:02:32.89 Server      Automatic soft-NUMA was enabled because SQL Server has detected hardware NUMA nodes with greater than 8 physical cores.
2020-06-09 23:02:32.91 Server      Error: 17311, Severity: 16, State: 1.
2020-06-09 23:02:32.91 Server      SQL Server is terminating because of fatal exception c0000005. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
2020-06-09 23:02:32.91 Server      Using 'dbghelp.dll' version '4.0.5'
2020-06-09 23:02:32.91 Server      **Dump thread - spid = 0, EC = 0x0000000000000000

2020-06-09 23:02:32.91 Server      * *******************************************************************************

2020-06-09 23:02:32.91 Server      *

2020-06-09 23:02:32.91 Server      * BEGIN STACK DUMP:

2020-06-09 23:02:32.91 Server      *   06/09/20 23:02:32 spid 15344

2020-06-09 23:02:32.91 Server      *

2020-06-09 23:02:32.91 Server      * ex_handle_except encountered exception C0000005 - Server terminating

2020-06-09 23:02:32.91 Server      *

2020-06-09 23:02:32.91 Server      *
* MODULE LISTING:
*

2020-06-09 23:02:32.91 Server      *  MODULE                          BASE      END       SIZE

2020-06-09 23:02:32.91 Server      * sqlservr                       00007FF6F7870000  00007FF6F78D7FFF  00068000

2020-06-09 23:02:32.91 Server      * ntdll                          00007FFAC9800000  00007FFAC99ACFFF  001ad000

2020-06-09 23:02:32.91 Server      * KERNEL32                       00007FFAC7F10000  00007FFAC804EFFF  0013f000

2020-06-09 23:02:32.91 Server      * KERNELBASE                     00007FFAC6D70000  00007FFAC6E84FFF  00115000

2020-06-09 23:02:32.91 Server      * NETAPI32                       00007FFAC2F60000  00007FFAC2F75FFF  00016000

2020-06-09 23:02:32.91 Server      * pdh                            00007FFAC51F0000  00007FFAC523EFFF  0004f000

2020-06-09 23:02:32.91 Server      * ADVAPI32                       00007FFAC7BB0000  00007FFAC7C59FFF  000aa000

2020-06-09 23:02:32.91 Server      * ole32                          00007FFAC7560000  00007FFAC76F3FFF  00194000

2020-06-09 23:02:32.91 Server      * SQLOS                          00007FFAAE100000  00007FFAAE106FFF  00007000

2020-06-09 23:02:32.91 Server      * sqlmin                         00007FFA96E10000  00007FFA9930AFFF  024fb000

2020-06-09 23:02:32.91 Server      * sqllang                        00007FFA94840000  00007FFA96E09FFF  025ca000

2020-06-09 23:02:32.91 Server      * sqlTsEs                        00007FFA93FB0000  00007FFA9483FFFF  00890000

2020-06-09 23:02:32.91 Server      * sqldk                          00007FFA93AE0000  00007FFA93FA8FFF  004c9000

2020-06-09 23:02:32.91 Server      * opends60                       00007FFAADBF0000  00007FFAADBF8FFF  00009000

2020-06-09 23:02:32.91 Server      * qds                            00007FFA9BBD0000  00007FFA9BCABFFF  000dc000

2020-06-09 23:02:32.91 Server      * MSVCP120                       00007FFABCDB0000  00007FFABCE55FFF  000a6000

2020-06-09 23:02:32.91 Server      * MSVCR120                       00007FFABCE60000  00007FFABCF4EFFF  000ef000

2020-06-09 23:02:32.91 Server      * netutils                       00007FFAC2EF0000  00007FFAC2EFBFFF  0000c000

2020-06-09 23:02:32.91 Server      * srvcli                         00007FFAC6500000  00007FFAC6525FFF  00026000

2020-06-09 23:02:32.91 Server      * wkscli                         00007FFAC2ED0000  00007FFAC2EE6FFF  00017000

2020-06-09 23:02:32.91 Server      * msvcrt                         00007FFAC6FC0000  00007FFAC7069FFF  000aa000

2020-06-09 23:02:32.91 Server      * RPCRT4                         00007FFAC7780000  00007FFAC78BFFFF  00140000

2020-06-09 23:02:32.91 Server      * sechost                        00007FFAC7EB0000  00007FFAC7F08FFF  00059000

2020-06-09 23:02:32.91 Server      * combase                        00007FFAC7070000  00007FFAC727FFFF  00210000

2020-06-09 23:02:32.91 Server      * GDI32                          00007FFAC7280000  00007FFAC73CBFFF  0014c000

2020-06-09 23:02:32.91 Server      * USER32                         00007FFAC73D0000  00007FFAC7546FFF  00177000

2020-06-09 23:02:32.91 Server      * CRYPT32                        00007FFAC6AE0000  00007FFAC6CBEFFF  001df000

2020-06-09 23:02:32.91 Server      * Secur32                        00007FFAC5C70000  00007FFAC5C7BFFF  0000c000

2020-06-09 23:02:32.91 Server      * WS2_32                         00007FFAC97A0000  00007FFAC97F9FFF  0005a000

2020-06-09 23:02:32.91 Server      * WINHTTP                        00007FFAC0DF0000  00007FFAC0EB8FFF  000c9000

2020-06-09 23:02:32.91 Server      * bcrypt                         00007FFAC63D0000  00007FFAC63F5FFF  00026000

2020-06-09 23:02:32.91 Server      * OLEAUT32                       00007FFAC6EB0000  00007FFAC6F76FFF  000c7000

2020-06-09 23:02:32.91 Server      * ODBC32                         00007FFABC8E0000  00007FFABC9A1FFF  000c2000

2020-06-09 23:02:32.91 Server      * USERENV                        00007FFAC5EB0000  00007FFAC5ED0FFF  00021000

2020-06-09 23:02:32.91 Server      * AUTHZ                          00007FFAC5B80000  00007FFAC5BC7FFF  00048000

2020-06-09 23:02:32.91 Server      * WINTRUST                       00007FFAC6A80000  00007FFAC6AD0FFF  00051000

2020-06-09 23:02:32.91 Server      * XmlLite                        00007FFAC34E0000  00007FFAC3518FFF  00039000

2020-06-09 23:02:32.91 Server      * dhcpcsvc                       00007FFAC2B20000  00007FFAC2B39FFF  0001a000

2020-06-09 23:02:32.91 Server      * WINMM                          00007FFABC770000  00007FFABC791FFF  00022000

2020-06-09 23:02:32.91 Server      * SspiCli                        00007FFAC6A00000  00007FFAC6A2DFFF  0002e000

2020-06-09 23:02:32.91 Server      * MSASN1                         00007FFAC69E0000  00007FFAC69F0FFF  00011000

2020-06-09 23:02:32.91 Server      * NSI                            00007FFAC78C0000  00007FFAC78C8FFF  00009000

2020-06-09 23:02:32.91 Server      * profapi                        00007FFAC6930000  00007FFAC6944FFF  00015000

2020-06-09 23:02:32.91 Server      * WINMMBASE                      00007FFABC740000  00007FFABC769FFF  0002a000

2020-06-09 23:02:32.91 Server      * LOGONCLI                       00007FFAC5EE0000  00007FFAC5F1EFFF  0003f000

2020-06-09 23:02:32.91 Server      * cfgmgr32                       00007FFAC6A30000  00007FFAC6A7EFFF  0004f000

2020-06-09 23:02:32.91 Server      * DEVOBJ                         00007FFAC5760000  00007FFAC5787FFF  00028000

2020-06-09 23:02:32.91 Server      * SAMCLI                         00007FFAC1020000  00007FFAC1036FFF  00017000

2020-06-09 23:02:32.91 Server      * SOPHOS~1                       00007FFAC6870000  00007FFAC68ABFFF  0003c000

2020-06-09 23:02:32.91 Server      * PSAPI                          00007FFAC7550000  00007FFAC7556FFF  00007000

2020-06-09 23:02:32.91 Server      * kernel.appcore                 00007FFAC5580000  00007FFAC558AFFF  0000b000

2020-06-09 23:02:32.91 Server      * CRYPTBASE                      00007FFAC6760000  00007FFAC676AFFF  0000b000

2020-06-09 23:02:32.91 Server      * bcryptPrimitives               00007FFAC66F0000  00007FFAC6752FFF  00063000

2020-06-09 23:02:32.91 Server      * instapi130                     00007FFABC810000  00007FFABC81FFFF  00010000

2020-06-09 23:02:32.91 Server      * CRYPTSP                        00007FFAC6180000  00007FFAC619FFFF  00020000

2020-06-09 23:02:32.91 Server      * rsaenh                         00007FFAC5DC0000  00007FFAC5DF5FFF  00036000

2020-06-09 23:02:32.91 Server      * imagehlp                       00007FFAC7700000  00007FFAC7715FFF  00016000

2020-06-09 23:02:32.91 Server      * ncrypt                         00007FFAC63A0000  00007FFAC63C4FFF  00025000

2020-06-09 23:02:32.91 Server      * NTASN1                         00007FFAC6360000  00007FFAC6396FFF  00037000

2020-06-09 23:02:32.91 Server      * gpapi                          00007FFAC5AD0000  00007FFAC5AF3FFF  00024000

2020-06-09 23:02:32.91 Server      * CLUSAPI                        00007FFABA040000  00007FFABA0ADFFF  0006e000

2020-06-09 23:02:32.91 Server      * cryptdll                       00007FFAC62A0000  00007FFAC62B9FFF  0001a000

2020-06-09 23:02:32.91 Server      * RESUTILS                       00007FFAB2AA0000  00007FFAB2AEBFFF  0004c000

2020-06-09 23:02:32.91 Server      * cscapi                         00007FFAB8A00000  00007FFAB8A11FFF  00012000

2020-06-09 23:02:32.91 Server      * sqlevn70                       00007FFA937F0000  00007FFA93ADFFFF  002f0000

2020-06-09 23:02:32.91 Server      * VERSION                        00007FFAC4EB0000  00007FFAC4EB9FFF  0000a000

2020-06-09 23:02:32.91 Server      * dbghelp                        00000000723C0000  0000000072555FFF  00196000

2020-06-09 23:02:32.91 Server      *
* PROCESSOR SPECIFIC CONTEXT:
*

2020-06-09 23:02:32.91 Server      *     P1Home: 00007FFAC7898A60:  6C894810245C8948  8348564157561824  0000B0998B4830EC  00000160B18B4800  48000000A8B18B4C  DB8548F98B48EA8B  

2020-06-09 23:02:32.91 Server      *     P2Home: 0000000000000000:  

2020-06-09 23:02:32.91 Server      *     P3Home: 0000000000000000:  

2020-06-09 23:02:32.91 Server      *     P4Home: 0000000000000000:  

2020-06-09 23:02:32.91 Server      *     P5Home: 0000000000000000:  

2020-06-09 23:02:32.91 Server      *     P6Home: 0000000000000000:  

2020-06-09 23:02:32.91 Server      * ContextFlags: 000000000010004F:  

2020-06-09 23:02:32.91 Server      *      MxCsr: 0000000000001FA0:  

2020-06-09 23:02:32.91 Server      *      SegCs: 0000000000000033:  

2020-06-09 23:02:32.91 Server      *      SegDs: 000000000000002B:  

2020-06-09 23:02:32.91 Server      *      SegEs: 000000000000002B:  

2020-06-09 23:02:32.91 Server      *      SegFs: 0000000000000053:  

2020-06-09 23:02:32.91 Server      *      SegGs: 000000000000002B:  

2020-06-09 23:02:32.91 Server      *      SegSs: 000000000000002B:  

2020-06-09 23:02:32.91 Server      *     EFlags: 0000000000000206:  

2020-06-09 23:02:32.91 Server      *        Rax: 0000005411949178:  00000000C0000100  0000005410B50CC0  000000540000002C  0000000000000020  000000000000003F  0000000000000001  

2020-06-09 23:02:32.91 Server      *        Rcx: 000000000000079A:  

2020-06-09 23:02:32.91 Server      *        Rdx: 00007FFAC983BE9D:  C68B413B34894666  F88348FFFFFF00E9  7824448B48197301  000023BE41C1FF48  E9C68B41088948C0  37894566FFFFFEE1  

2020-06-09 23:02:32.91 Server      *        Rbx: 0000000000000000:  

2020-06-09 23:02:32.91 Server      *        Rsp: 00000054119496B0:  0000000000000000  0000000000000000  0000000000000000  00007FFA93B4C140  00000000000042AC  0000000000000000  

2020-06-09 23:02:32.91 Server      *        Rbp: 0000000000000000:  

2020-06-09 23:02:32.91 Server      *        Rsi: 0000000000000000:  

2020-06-09 23:02:32.91 Server      *        Rdi: 00007FFA93B4C140:  6C894808245C8948  5718247489481024  8B48F18B30EC8348  330019EAED0D8BEA  480011122915FFDB  F88039481C74C085  

2020-06-09 23:02:32.91 Server      *         R8: 00000000C0000100:  

2020-06-09 23:02:32.91 Server      *         R9: 0000005410B50CC0:  0000000000900000  0000000000000000  0000005410B4E8B0  0000005410B50000  000000200000010A  0000000000000000  

2020-06-09 23:02:32.91 Server      *        R10: 000000540000002C:  

2020-06-09 23:02:32.91 Server      *        R11: 0000000000000020:  

2020-06-09 23:02:32.91 Server      *        R12: 000000000000003F:  

2020-06-09 23:02:32.91 Server      *        R13: 0000000000000001:  

2020-06-09 23:02:32.91 Server      *        R14: 0000000000000000:  

2020-06-09 23:02:32.91 Server      *        R15: 0000000000000000:  

2020-06-09 23:02:32.91 Server      *        Rip: 00007FFAC6D788DC:  000000C0248C8B48  FFFF8B54E8CC3348  C3000000D8C48148  9090909090909090  38418B4D28EC8348  11E8D18B49CA8B48  

2020-06-09 23:02:32.91 Server      * *******************************************************************************

2020-06-09 23:02:32.91 Server      * -------------------------------------------------------------------------------

2020-06-09 23:02:32.91 Server      * Short Stack Dump

2020-06-09 23:02:32.92 Server      00007FFAC6D788DC Module(KERNELBASE+00000000000088DC)

2020-06-09 23:02:32.92 Server      00007FFA9587828E Module(sqllang+000000000103828E)

2020-06-09 23:02:32.92 Server      00007FFA9587C009 Module(sqllang+000000000103C009)

2020-06-09 23:02:32.92 Server      00007FFA94DA8486 Module(sqllang+0000000000568486)

2020-06-09 23:02:32.93 Server      00007FFA93B4BC62 Module(sqldk+000000000006BC62)

2020-06-09 23:02:32.93 Server      00007FFAC6E516D2 Module(KERNELBASE+00000000000E16D2)

2020-06-09 23:02:32.93 Server      00007FFAC989F173 Module(ntdll+000000000009F173)

2020-06-09 23:02:32.93 Server      00007FFAC9881DD6 Module(ntdll+0000000000081DD6)

2020-06-09 23:02:32.93 Server      00007FFAC989345D Module(ntdll+000000000009345D)

2020-06-09 23:02:32.93 Server      00007FFAC9854937 Module(ntdll+0000000000054937)

2020-06-09 23:02:32.93 Server      00007FFAC98925EA Module(ntdll+00000000000925EA)

2020-06-09 23:02:32.93 Server      00007FFA93C25B16 Module(sqldk+0000000000145B16)

2020-06-09 23:02:32.93 Server      00007FFA93C252C2 Module(sqldk+00000000001452C2)

2020-06-09 23:02:32.93 Server      00007FFA93C250CB Module(sqldk+00000000001450CB)

2020-06-09 23:02:32.93 Server      00007FFA95EDE27A Module(sqllang+000000000169E27A)

2020-06-09 23:02:32.93 Server      00007FFA95E5DAB6 Module(sqllang+000000000161DAB6)

2020-06-09 23:02:32.93 Server      00007FF6F787D1C8 Module(sqlservr+000000000000D1C8)

2020-06-09 23:02:32.93 Server      00007FF6F787EEB3 Module(sqlservr+000000000000EEB3)

2020-06-09 23:02:32.93 Server      00007FF6F78784F8 Module(sqlservr+00000000000084F8)

2020-06-09 23:02:32.94 Server      00007FFAC7EB5ADA Module(sechost+0000000000005ADA)

2020-06-09 23:02:32.94 Server      00007FFAC7F113D2 Module(KERNEL32+00000000000013D2)

2020-06-09 23:02:32.94 Server      00007FFAC98154F4 Module(ntdll+00000000000154F4)

2020-06-09 23:02:32.94 Server      Stack Signature for the dump is 0x000000000ADDB46F
2020-06-09 23:02:32.94 Server      Unable to create dump because SQLDUMPER library is not available.
2020-06-09 23:02:32.94 Server      SQL Server shutdown has been initiated


↧

SQL Server 2017 CU 21 FileStream failed to load RsFx0504.sys

July 28, 2020, 4:21 am
$
0
0

SQL Server 2017 with CU 21 installed. Operating System is Windows Server 2012.

The SQL Server FileStream cant be initialized on instance start, since CU 21 is installed. When i try to configure the Filestream with the SQL Server Configuration Manager i get the Error: 0x80070241

In the Eventviewer - System - is a message: "\SystemRoot\system32\DRIVERS\RsFx0504.sys failed to load"

Before CU21 the SQL Server Filestream worked. The driver "\SystemRoot\system32\DRIVERS\RsFx0503.sys" was active. 

Is there a way back to the Driver "RsFx0503.sys"?
Can i uninstall the SQL Server 2017 CU 21? Or is there a msi-package that allows me to install a prior version of RsFx for the SQL Server 2017?

Best regards
Paolo 

 

↧

Convert run_date and run_time into a DateTime Format

October 25, 2017, 7:20 am
$
0
0

Hello Forum

Does anyone know how to convert the run_date and run_time in sysJobsHistory into a DateTime format?

Please click "Mark As Answer" if my post helped. Tony C.

↧
Viewing all 15930 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>