Data Cleanup
Steve wishes we could do some data cleanup and archival every year. Or even more often.
2022-01-03
324 reads
Steve wishes we could do some data cleanup and archival every year. Or even more often.
2022-01-03
324 reads
2019-09-26
587 reads
2019-09-09
595 reads
With most innovative new technologies, Azure Stretch Database demos make it look completely easy. Here is a step by step to get going, with examples. Part One of a Two-Part series.
2019-08-26
4,952 reads
Learn how you can enable the Stretch Database feature in SQL Server 2016.
2020-07-03 (first published: 2019-01-15)
4,740 reads
In many cases Azure SQL Database offers an economically and functionally viable alternative to SQL Server deployments. However, there are also scenarios where we might discover that rather than serving as a replacement, it provides synergy, working side by side with your on-premises databases. One of technologies that illustrate this paradigm is Stretch Database, introduced in SQL Server 2016. Marcin Polichtdescribes its basic characteristics and reviews its implementation steps in this article.
2016-09-07
4,849 reads
Tim Radney of SQLskills shows how the Stretch Database feature has evolved from its early CTP beginnings to the RTM version released earlier this month.
2016-08-10
2,545 reads
2016-06-29
983 reads
2016-06-16
1,113 reads
Arshad Ali explains and demonstrates the impact of enabling the Stretch database feature on backup and restore operations. He also discusses ways to pause, resume, and disable this feature altogether when not needed.
2016-01-19
4,779 reads
By Kevin3NF
Don’t Let Trouble Sneak Up on You Most SQL Servers run quietly. Until...
By Steve Jones
I had a conversation with a customer asking this question: how can I tell...
By Chris Yates
There was a time when the Chief Data Officer lived in the shadows of...
Comments posted to this topic are about the item Create an HTML Report on...
Hi everyone I am getting an error when I create the index but I...
Good morning all, I have been running into a very random weird issue that...
I have two calls to the GENERATE_SERIES TVF in this code:
SELECT TOP 10 gs.value FROM GENERATE_SERIES(1, 10) AS gs ORDER BY NEWID () OPTION (RECOMPILE); go DECLARE @a int = 10; SELECT TOP (@a) gs.value FROM GENERATE_SERIES(1, @a) AS gs ORDER BY NEWID () OPTION (RECOMPILE);In the actual query plans, what is the estimated number of rows for each batch in SQL Server 2022? See possible answers