Mixed page allocation
MIXED_PAGE_ALLOCATION is a new option introduced with SQL Server 2016. It controls whether the database can create initial pages using a mixed extent for the first eight pages of...
2017-04-08
25 reads
MIXED_PAGE_ALLOCATION is a new option introduced with SQL Server 2016. It controls whether the database can create initial pages using a mixed extent for the first eight pages of...
2017-04-08
25 reads
MIXED_PAGE_ALLOCATION is a new option introduced with SQL Server 2016. It controls whether the database can create initial pages using a mixed extent for the first eight pages of...
2017-04-08
49 reads
MIXED_PAGE_ALLOCATION is a new option introduced with SQL Server 2016. It controls whether the database can create initial pages using...
2017-04-08
5,859 reads
A good security practice is to backup our SQL Servers to a network share but not allow users to be...
2017-04-13 (first published: 2017-04-08)
1,417 reads
The cloud is calling to you. Or more specifically, Jody Roberts (b | @) and I (b | @) are looking to the community to find some presenters interested in...
2017-04-07
37 reads
The cloud is calling to you. Or more specifically, Jody Roberts (b | @) and I (b | @) are looking to the community...
2017-04-07
973 reads
Recently a client requested some new transactional replication publications on a relatively new pre-production server. The client has plenty of...
2017-04-13 (first published: 2017-04-07)
2,331 reads
SQL Server uses identity columns to auto generate values, normally keys. When you create an identity column, it has a...
2017-04-07
575 reads
Once again I’m heading back to the Valley. I was accepted to speak at SQL Saturday #621 – Silicon Valley on...
2017-04-07
644 reads
As this is being published I’m on my way up to Dublin airport to head on over to the UK...
2017-04-07
156 reads
By DesertDBA
I did not expect 27 responses to my T-SQL Tuesday #204 invitation, but it...
Should you adopt an off-the-shelf AI tool, partner with a specialist, build in-house, or...
By ReviewMyDB
Part 1 of my What's New in SQL Server for the Developer series. IIF,...
Comments posted to this topic are about the item Switching Schema II
Comments posted to this topic are about the item A Practical Approach to Automating...
Comments posted to this topic are about the item Data Lost in the Cloud
I run this query:
SELECT s.name AS schemaname , o.name AS objectname FROM sys.objects o INNER JOIN sys.schemas s ON s.schema_id = o.schema_id WHERE o.name = 'Beer'I get two rows back for the objects, named dbo.beer and etl.beer. Both the tables have identical schemas and are not partitioned. There are 25 rows in dbo.beer and 0 rows in etl.beer. I run this code:
ALTER TABLE dbo.beer switch TO etl.beerWhat happens? See possible answers