Removing Email from msdb Database
Is your msdb database growing bigger every day? If so you might want to consider purging some of the history records. Greg Larsen explains.
2017-01-04
6,454 reads
Is your msdb database growing bigger every day? If so you might want to consider purging some of the history records. Greg Larsen explains.
2017-01-04
6,454 reads
Identify the Database Server which is used to mount the database in Sharepoint 2010
2017-01-03
1,893 reads
2017-01-03
2,390 reads
Triggers are generally over-used in SQL Server. They are only rarely necessary, can cause performance issues, and are tricky to maintain If you use them, it is best to keep them simple, and have only one operation per trigger. Joe Celko describes a feature of SQL that 'gets complicated fast'.
2017-01-03
3,807 reads
Aaron Bertrand explains a few details about the memory limits in SQL Server 2016 Service Pack 1 that make this upgrade even more compelling.
2017-01-02
3,926 reads
How does a column store index compare to a (traditional)row store index with regards to performance
2016-12-30 (first published: 2015-05-14)
15,480 reads
Manvendra Singh takes a look at a SQL Server function that you can use to read the transaction log to see what entries are made for database transactions.
2016-12-30
4,902 reads
SQL Server 2016 does not allow computed columns to co exist with columnstore indexes and clustered btree indexes on same table.
2016-12-29
909 reads
SQL Server 2016 brings native support to advanced analytics in the database itself, using R Services. In this article, Arshad Ali explains what R is, what the on-premise advanced analytics options from Microsoft are, and shows how to get started using R Services with SQL Server 2016.
2016-12-29
4,325 reads
This article compiles some common questions and answers about Azure SQL Data Warehouse.
2016-12-28
9,283 reads
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....
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
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