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-2019
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):
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.
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:
How to merge multiple filegroup data files to a single data file?
Have a single 500gb DB with a single file group consisting of 4 data files. This was due to old SAN volume space restrictions that are no longer in play on the new SAN. Would like to consolidate these 4 data files back down to a single data file if possible. What are the different ways to consolidate these data files down to a single data file?
Can you safely log ship between primary and secondary servers on different cumulative update versions?
Need to update primary from 2019-CU14 to 2019 CU15 and a few hours/days later update secondary to CU 15 once the primary is deemed stable. Can you safely log ship between primary and secondary servers on different cumulative update versions (CU-15 to CU-14 in this case)?
ALTER causes “Time-out occurred while waiting for buffer latch type 2”
The following statement fails with Time-out occurred while waiting for buffer latch type 2 for page (1:4365112), database ID 12.:
Extended events capture all calls by login/user and sql text containing a value
I’m using below extended events session to capture the data that contains a value 9999 by login xEventsTest. But I don’t see any data captured with the filters added, but I could see this call when no filters are added to the events.
What’s the modern recommendation for SQL Server’s physical storage configuration
It’s 2022. I’m setting up a SQL Server that will support a single medium size web app. I have physical hardware with 4 NVMes that I need to configure. What’s the best practice? On which physical drives do the volumes for OS, data, logs, tempdb, and backups go? Or should I just go RAID 10 and create a volume for each concern?