Schema-Owned Tables and Generated DROP Scripts (SQL Spackle)
Not all SQL-generated scripts are created equal (or correctly) for alternative schema-owned objects.
Not all SQL-generated scripts are created equal (or correctly) for alternative schema-owned objects.
Humans are often the weakest links in any computer process, but we do need human input. Steve Jones talks about a few issues, and how we should be changing our workflow to reduce issues.
A corollary to Murphy's Law states that disaster is most likely to strike when your senior people are out of the office.
When using SQL Server, you frequently need to work with data that represents intervals of time. For example, consider intervals representing sessions, contracts, projects, and so on. Tasks related to interval manipulation are typically quite intriguing, especially because coming up with efficient solutions isn't easy. Itzik Ben-Gan explains
SQL Saturday is coming to Baton Rouge for a free day of SQL Server training and Networking on August 3.
There is also a pre-conference session presented by Bill Pearson on Practical Self-Service BI with PowerPivot for Excel on August 2nd.
Wouldn't be nice if we can set the "read only" property of any table to be on or off easily with one simple stored procedure call?
Today Phil Factor talks about Big Data, and all the hype that's in the news.
When you're monitoring SQL Server, it's better to capture a baseline for those aspects that you're checking, such as workload, Physical I/O or performance. Once you know what is normal, then performance tuning and resource provisioning can be done in a timely manner before any problems becomes apparent. We can prevent problems by being able to predict them. Louis shows how to get started.
SQL Saturday is returning to St Louis for a full day of free SQL Server training and networking. This year's event will be on August 3, 2013 at the Saint Louis University's Center for Workforce & Organizational Development. We hope to see you there.
This article contains a set of instructions for configuring SQL Server mirroring, including pre-requisites. It also includes notes on how to resolve a few issues that I have encountered.
If you’ve been watching AI roll through the data community and thinking, “this seems...
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
It is Friday, the queries are running, and nobody is watching the bill. That...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
I set up a few users on my SQL Server 2022 instance.
CREATE LOGIN User1 WITH PASSWORD = 'Demo12#1' CREATE USER User1 FOR LOGIN User1 GO CREATE LOGIN User2 WITH PASSWORD = 'Demo12#2' CREATE USER User2 FOR LOGIN User2 GO CREATE LOGIN User3 WITH PASSWORD = 'Demo12#3' CREATE USER User3 FOR LOGIN User3 GOI then created a schema that one of them owned. Under this schema, I added a table with some data.
CREATE SCHEMA MySchema AUTHORIZATION User1
GO
CREATE TABLE Myschema.MyTable(myid INT)
GO
INSERT MySchema.MyTable
(
myid
)
VALUES
(1), (2), (3)
GO
SELECT * FROM MySchema.MyTable
GO
I granted rights and verified that User2 could access this table.
GRANT SELECT ON Myschema.MyTable TO User2 GO SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOThis worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3; GOWhat happens with this code?
SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOSee possible answers