You’ve heard that shrinking a database is bad because it introduces both external and internal fragmentation, it causes blocking, it causes transaction log growth while it runs, and it’s slow and single-threaded. You understand that if it’s just a matter of 10-20-30% of a database, and the database is only 100-200GB, you might as well just leave the space there, because you’re gonna end up using it anyway.
Learn how you can use Polybase technology in Azure Synapse to load data into your warehouse.
Phil Factor dissects and disentangles the various SQL Compare options.
In this article we look at different T-SQL code examples that can help you build a range of date rows based on a starting and ending date.
A failed SQL Server Service Pack upgrade is fixed with a trace flag.
Steve reflects on some of the ideas of how Microsoft imagines the future of computing.
In this article we cover many different questions about the SQL Server TempDB database to give a better understanding of what is and what it is used for.
It's time for T-SQL Tuesday #198! This month's topic is change detection. The post T-SQL...
By James Serra
Model Context Protocol, or MCP, is one of those technical ideas that sounds more...
When starting with AWS RDS Aurora for managing relational databases in the cloud, many...
We suffered a SPAM attack from May 1-6, which unfortunately corresponded with time off...
Jl. Raden Saleh No. 13, 15, 17A, Daerah Khusus Ibukota Jakarta 10430
Jl. K.H. Wahid Hasyim No.183 A-B, Kb. Kacang, Kecamatan Tanah Abang, Kota Jakarta Pusat,...
I have this data in a table called dbo.NFLTeams
TeamID TeamName City YearEstablished ------ -------- ---- --------------- 1 Cowboys Dallas 1960 2 Eagles Philadelphia 1933 3 Packers Green Bay 1919 4 Chiefs Kansas City 1960 5 49ers San Francisco 1946 6 Broncos Denver 1960 7 Seahawks Seattle 1976 8 Patriots New England 1960If I run this code, how many rows are returned?
SELECT TOP 2
json_objectagg('Team' : TeamName)
FROM dbo.NFLTeams;
See possible answers