Dynamic SSRS report documentation via a ReportServer.dbo.Catalog query
This article demonstrates a method of generating SSRS report documentation by using an SSRS report that queries the ReportServer.dbo.Catalog table.
This article demonstrates a method of generating SSRS report documentation by using an SSRS report that queries the ReportServer.dbo.Catalog table.
In some scenarios we can find different SQL Server collations between the server instance and its databases. Douglas P. Castilho explains a simple way to correct the collations in a few steps.
Just because something works, is it prudent to implement a solution knowing there is a chance this design flaw will be stricken from future revs of SQL Server? It depends.
This article explores aspects of a job that help one feel satisfied at work.
In this article, I will show a procedure to isolate the replication traffic from the public network.
Learn how to scale an Azure SQL Datawarehouse up or down, and how to pause it when not in use.
Is 'Always Encrypted' SQL Server 2016's most widely important new feature? It is significant that 'Always Encrypted' in SQL Server is in all editions of SQL Server. Because of the increasing importance of encryption to data governance, it allows encryption for the sensitive application data for everywhere beyond the application's client connection, including network, server, database and storage. Robert Sheldon explains what it is, why you should try it out, and how to set about it.
This week Steve Jones is asking if you stage your database changes ahead of application changes.
Learn about the time savings, blocking scenarios, limitations and more for the SQL Server 2016 online ALTER COLUMN operation.
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...
Because we are NABL Accredited Laboratories, our personal care and cosmetics research center provides...
WhatsApp:0817-866-887 Jl. Ahmad Yani No.31, Pattunuang, Kec. Wajo, Kota Makassar, Sulawesi Selatan 90174 (@bcakcumakassar)
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