Hi all. May I know how to read the following output of DBCC PAGE number 3 GAM page. ?
which mean extent 0 - 26432 are allocated ?
Hi all. May I know how to read the following output of DBCC PAGE number 3 GAM page. ?
which mean extent 0 - 26432 are allocated ?
I am reading the following docs:
https://docs.microsoft.com/en-us/sql/relational-databases/databases/tempdb-database?view=sql-server-ver15#memory-optimized-tempdb-metadata
it mention this feature for SQL Server 2019
.......memory-optimized tempdb metadata, which effectively removes this bottleneck and unlocks a new level of scalability for tempdb-heavy workloads. In SQL Server 2019 (15.x), the system tables involved in managing temporary table metadata can be moved into latch-freenon-durable memory-optimized tables..........
So I just curious
1. I have done some test , after enable this features, all the PAGELATCH_EX gone , for resource of page of metadata table sys sysschobjs. So after enable the feature , the page of sysschobjs do not need a PAGELATCH_ to lock this resource when multiple session are modifying it ? or it's just too fast to release the lock that I can't notice it ?
2 what mean non-durable?
If I have a server have 16 cores , 64 bits, can I tune max worker thread (instance setting) to 1000 ?
And if calculating max worker thread will be using physical core or logical core or the CPU ?
hi folks:
Our Azure VM SQL is using 2016 SP2 entCU8. We have a list of databases with TDE enabled and backup was using compression with the following parameters
WITH FORMAT, COMPRESSION, MAXTRANSFERSIZE = 4194304, BLOCKSIZE = 65536, STATS = 1
for smaller databases less than 1TB , they went through without an issue.
For bigger dbs over 1TB, one is with 2TB and the other was 8TB. It was causing huge I/O async waitype to the point it caused
locks to many processes and we have to stop it.
has anyone seen such issue before and any suggestions?
We are also in contact with MSFT premier support and initial words was that at one point of time, disk performance dropped dramatically and we've asked all teams but they said no schedule jobs running during that backup time . We've verified and confirmed.
One thing I noticed that these two big databases, VLF size is over 20G though Active VLF size is under 200MB
I know that it is not recommended to backup tlog with over 4G VLF, does that apply to full back?
Cheers
HS
Hi,
We are migrating from SQL Server 2016 which is on ReFS/64k block size. We have OLTP and OLAP system ranging from 10 to 15TB sizes.
What is the best practice? Shall i continue same ReFS with 64k block size or any other recommendation?
Thanks
Hi,
I have 3 Node SQL AOAG Cluster.
Recently , while trying to check the Application status , I started seeing below error in previous primary (AG Replica1) where as the status is working in now primary (previous secondary AG Replica2). Please share some thoughts on the issue below.
Internal error occurred in sync. Please see details for contextual information.
Organisation.RE.APP.Sync.Common.Exceptions.SyncCriticalSqlException: Critical issue requires administrative attention. ---> System.REta.SqlClient.SqlException: The network name cannot be found ---> System.ComponentModel.Win32Exception: The network
name cannot be found
at System.REta.SqlTypes.SqlFileStream.OpenSqlFileStream(String path, Byte[] transactionContext, FileAccess access, FileOptions options, Int64 allocationSize) at System.REta.SqlTypes.SqlFileStream..ctor(String path, Byte[] transactionContext, FileAccess
access, FileOptions options, Int64 allocationSize) at System.REta.SqlTypes.SqlFileStream..ctor(String path, Byte[] transactionContext, FileAccess access) at Organisation.RE.APP.Framework.Implementation.REta.SqlFileStreamHelper.GetSqlFileStream(String
PstrFileStreamPath, Byte[] PabyTransactionContext, FileAccess PeFileAccess)
CreateChangeBatch: Critical issue requires administrative attention.
The network name cannot be found
The network name cannot be found
Best Regards,SQLBoy
I have check the following memory usage for the sqlserver
so how to derive 4591.1MB usage on the first screen ?
ccommit size and working set (memory) have what difference ?
what are
commited ? Cached? Paged pool and non-paged pool?
May I know Multipage allocation vs Large Pageallocation are the same concept ?
Any example of what type of Multipage allocation are?
I check in my sys.dm_os_memory_clerks that column page_sizes_in_bytes are all 8192 .
https://docs.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-os-memory-pools-transact-sql?view=sql-server-ver15
By default pool_id 0 is internal pool and pool_id 1 is default pool ?
https://www.sqlskills.com/help/waits/cmemthread/
what's actually "TREAD-safe-memory-object" ?
I run a dbcc checkdb and use performance counter to monitor .
Page Reads/s around 22,970 .
While disk read : 1607. , it's a huge difference and why ?? Page reads doesn't mean page read from disk ?
May i know if the current committed will also include stack memory allocation ? (which is not control by max server memory ) ?
Hi All
https://docs.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-os-memory-brokers-transact-sql?view=sql-server-ver15
what's the memory broker that monitor the allocation for buffer cache ?
our applications are using sa to connect to sql serer
we want to get away from that
we are attempting to rename sa to be satemp and assign with limited permisisons
to accomplish this I am attempting to understand all dependencies on sql server objects on the sa account
how to determine what objects are owned by sa
is there a script to determine the effective permissions of a login , especially sa