Day 8 of 31 Days of Disaster Recovery (T-SQL Tuesday #38): Resolutions for All DBAs
T-SQL Tuesday #38
This post is not only day 7 of my 31 Days of Disaster Recovery series, it is...
2013-01-08
1,363 reads
T-SQL Tuesday #38
This post is not only day 7 of my 31 Days of Disaster Recovery series, it is...
2013-01-08
1,363 reads
An algorithm that starts with the word “regression” seems an unlikely candidate to move forward with this series of self-tutorials...
2013-01-08
4,450 reads
This month’s T-SQL Tuesday is hosted by Jason Brimhall. Being as this is January, lots of people are making New...
2013-01-08
763 reads
Day 7 of 31 Days of Disaster Recovery: Writing SLAs for Disaster Recovery
31 Days of Disaster Recovery
Today is day...
2013-01-08
1,610 reads
Last week I sent out an invite for the monthly TSQL Tuesday party. The theme for the party is a take on the words resolve or resolution. I was...
2013-01-08
17 reads
Last week I sent out an invite for the monthly TSQL Tuesday party.
The theme for the party is a take...
2013-01-08
1,159 reads
I ran down the rabbit hole on transaction logs recently. I started with Paul Randal’s post over at the SQL...
2013-01-07
1,202 reads
Late in December, one the long awaited portions of functionality inside SSDT was released to an eager public, that being...
2013-01-07
1,772 reads
As a part of my series leading up to Christmas 2012, I shared a script to Report on SSRS Subscriptions. It was soon found to have a bug with...
2013-01-07
14 reads
As a part of my series leading up to Christmas 2012, I shared a script to Report on SSRS Subscriptions....
2013-01-07
1,877 reads
Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...
By Steve Jones
Next year the PASS Data Community Summit is in DENVER! and London, but Denver...
By Steve Jones
Yesterday was the first day of sessions at the PASS Data Community Summit (after...
Comments posted to this topic are about the item Pay for Performance, which is...
Comments posted to this topic are about the item Switching Schemas I
Comments posted to this topic are about the item Enforcing Unique Customer Emails When...
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 one row back for an object named dbo.beer. There is an ETL schema and both of these are nonpartitioned tables. I run this code:
ALTER TABLE dbo.beer switch TO etl.beerWhat happens? See possible answers