The SQL Server 2008 Datetimeoffset Data Type
The Datetimeoffset Data Type was introduced in SQL Server 2008 (and .Net Frameword 3.5) and is the most advanced date and time date type available.
The Datetimeoffset Data Type was introduced in SQL Server 2008 (and .Net Frameword 3.5) and is the most advanced date and time date type available.
A drive on a mission-critical server is reaching capacity, and the new DBA is panicking. How do you approach a ballooning log file that won’t stop growing?
Is there a way to process only the new data for a partition in SQL Server Analysis Services? Yes, this is accomplished in SQL Server Analysis Services with the ProcessAdd option for partitions. Daniel Calbimonte demonstrates how it works.
Steve Jones notes that security can be a reason to upgrade your systems, but it can also result in an endless cycle.
Even when organisations cannot make full use of public cloud for reasons of security or bandwidth limitations, many of the advantages of flexibility and rapid deployment can be made by providing a private cloud. Jaap Wesselius wonders if private clouds provide a new paradigm for enterprises.
Day 2 at the PASS Summit provides some inspiration for Steve Jones at the Women in Technology luncheon.
How much space would compressing a particular index will save? How will this affect query performance? Derek Colley walks you through the effects of using data compression in SQL Server.
Schemas may be largely irrelevant to small databases, where it is no trouble to assign permissions to individual objects, but they are vital for a hard working corporate database that is being actively developed and used by several applications, with thousands of objects that must be assigned the correct permission.
Testing our applications is important, but at what level do we need to test? Steve Jones talks about unit testing today, and wonders if this is prevalent for SQL Server developers.
We asked DBAs to share their worst days. Some are funny, others tragic, many both. Here are the 5 finalists, vote for your favorite story to be THE worst day as a DBA.
It is Friday, the queries are running, and nobody is watching the bill. That...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
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