Compressed Microsoft SQL Server Backups by Default
Learn how to create default database compression for your SQL Server databases.
2019-04-30
Learn how to create default database compression for your SQL Server databases.
2019-04-30
The script estimate compression benefits per each object in the database for which the page compression has not been implemented.
2018-02-15 (first published: 2018-01-15)
2,052 reads
This is an investigation, to get an impression on the impact of the used disk space before and after compression considering different index types.
2017-03-23
2,370 reads
Erin Stellato takes a look at the new COMPRESS and DECOMPRESS functions, comparing their impact on space and performance to traditional data compression.
2017-02-15
6,456 reads
My SQL Server database has some very big tables that can be compressed. The tables are simple, non-partitioned tables and I want a quick tool to compress them. I
2016-08-12
2,979 reads
Sharing our experience using Data Compression as a space savings option in MS SQL Server 2008
2018-10-19 (first published: 2016-01-18)
4,436 reads
This will log output of estimate compression for both PAGE and ROW for all tables and indexes
2015-12-10 (first published: 2015-11-20)
2,507 reads
This script is used to compress tables and indexes. It is designed for page compression on all. Just a little ditty to help with our EDW storage and processing.
2015-11-11 (first published: 2015-10-09)
1,325 reads
2015-02-19 (first published: 2014-02-03)
1,923 reads
2014-01-30
2,011 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...
WhatsApp:0817-866-887 Jl. Ahmad Yani No.31, Pattunuang, Kec. Wajo, Kota Makassar, Sulawesi Selatan 90174 (@bcakcumakassar)
Hi All I am trying to find 'bad' characters that users might type in....
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