Identity Values – Two things to know
I saw someone post a question recently about running out of identity values in an INT column. It happens, it’s...
I saw someone post a question recently about running out of identity values in an INT column. It happens, it’s...
When I first reported to my duty assignment with the US Air Force, there were 3 sergeants in my shop....
Even after you have applied proper indexing along with re-factoring your TSQLs with best practices, some data access routines might still be there, which would be expensive, in terms of their execution time. There must have been some smart ways to deal with these. Yes there are. SQL server offers you some rich indexing techniques that you might have not used earlier. These could surprise you with the performance benefits they possibly offer. Let us start implementing those advanced indexing techniques:
Steve Jones says we need to stick together in IT, at least from the perspective of the client. Otherwise we can all look bad as an industry.
A Rolled back transaction will increase the snapshot sparse file usage. New author Subash brings us an examination of how those database snapshots actually work.
Steve Jones says we need to stick together in IT, at least from the perspective of the client. Otherwise we can all look bad as an industry.
Steve Jones says we need to stick together in IT, at least from the perspective of the client. Otherwise we can all look bad as an industry.
Steve Jones says we need to stick together in IT, at least from the perspective of the client. Otherwise we can all look bad as an industry.
Recent installments of our SQL Server 2005 Express Edition series have been discussing its implementation of Full Text Indexing. This article focuses on data searches, which leverage existing indexes, taking into account such features as noise words and thesaurus files.
This article from Ed Swiedler looks at using SQL Server to log activity from various sources. Service Broker and Windows Services are used to create a generic logging service that will build log files for you to examine outside of any application.
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