SQL Prompt Tips #5 - Current Statement Execution
Learn how a new feature in SQL Prompt 6.4 can help you avoid costly mistakes in coding.
2015-11-11 (first published: 2015-01-12)
7,834 reads
Learn how a new feature in SQL Prompt 6.4 can help you avoid costly mistakes in coding.
2015-11-11 (first published: 2015-01-12)
7,834 reads
Jonathan Allen takes a peak at the EAP release of SQL Prompt 6 and some of the cool new things you can do to speed up writing SQL.
2013-08-21
1,637 reads
A quick tip to help you set your object names to your preferred case in T-SQL code.
2015-10-21 (first published: 2012-05-01)
2,283 reads
A quick tip to help you get system object suggestions from SQL Prompt.
2015-11-04 (first published: 2012-05-01)
1,250 reads
Another quick tip for SQL Prompt, using the snippets to increase your productivity.
2015-10-28 (first published: 2012-05-01)
1,507 reads
A quick tip to help you get the most out of SQL Prompt.
2015-10-14 (first published: 2012-05-01)
1,675 reads
Fabiano Amorim is hooked on today's Integrated Development Environments with built-in Intellisense, so he looked forward keenly to SQL Server 2008's native intellisense. He was disappointed at how it turned out, so turned instead to SQL Prompt. Fabiano explains why he prefers to SQL Prompt, why he reckons it fits in with the way that database developers work, and goes on to describe some of the features he'd like to see in it
2010-04-09
4,030 reads
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
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...
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