2007-04-05
1,100 reads
2007-04-05
1,100 reads
2007-03-28
1,036 reads
SQL Server 2005 has changed replication dramatically and one of the changes is that subscriber tables have the identity
column. SQL Server guru Andy Warren takes a look at what impact this has on transactional replication.
2007-03-28
8,598 reads
This script is basically a front-end for the sp_"scriptproc" stored procedures that ship with MSSQL. This will allow you to create ALL of your procs (INS, UPD and DEL) on the fly using the article name instead of having to first search for the article ID. It also uses sp_scriptdynamicupdproc where appropriate. This facilitates quick […]
2007-04-23 (first published: 2007-03-27)
1,753 reads
Work table method for transferring any table across replication in usable transactional chunks. Very useful for publishers requiring bulk insert operations on source tables.
2007-08-13 (first published: 2007-01-11)
794 reads
2006-12-28
998 reads
2006-12-19
989 reads
2006-12-13
979 reads
2006-12-05
1,042 reads
Setting up replication can be fairly easy, but deviating from the follow-the-wizard approach can be tricky. New author Claudia Rego brings us a primer on setting up transactional replication without requiring an initial snapshot.
2006-11-20
8,597 reads
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