Generate JSON with property names that include dot using SELECT FOR JSON
I need to generate the folowing JSON payload (shortened) from a table in SQL Server. Please note the dot in the property name. This is a special syntax called OData.
sql-server
SQL Server / SSMS taking up lots of disk space
I installed SQL Server + SSMS for my univ class and ever since then my disk space is going missing (every so often, approx. 3 gb of space goes missing). I strongly suspect SQL Server and/or SSMS to be at fault (since it only happened after I installed them), however I have no idea how to track down that missing space. Is it doing massive amounts of logging? Backups? No idea.
SQL Server: Is it worth checking for change in a field before the update?
I’m investigating this statement performance on SQL Server 2019 (I’ve extracted the important part):
Azure SQL Database – contained users password
Where is the password saved when creating a contained user for the Azure SQL database (PaaS)?
DateTime2 and Page Life Expectancy (PLE)
As I understand it, when you define a column on a table you define its precision. This precision takes 1 byte and is stored at the column level. If you use a precision of 5 or more, then a DateTime2 column will take 8 bytes per row. (The precision is not stored at the row level.)
SQL Server Extended Events odd behavior trying to capture statements coming from SAS
The problem: the Extended Events (EE) session we created to capture queries against a certain table is not working when the request comes from SAS.
Index Optimization for tables that are truncated and charged everyday
I’m a recently recruited Data Engineer, I have made a bunch of ETL pipelines planned to run daily, the destination tables are truncated and charged again. The DBMS is on-prem SQL Server.
What is the num of NUMA nodes for MAXDOP calculation when there is discrepancy between various ways to count the NUMA nodes?
Querying the dm_os_performance_counters shows that I have 2 NUMA nodes:
Non-clustered Primary Key and Clustered Index
It is my understanding that in SQL Server, you can have a Primary Key that is non-clustered, and have another index that is the clustered one.