Replication

Technical Article

Script to generate BCP Statements for a Database

  • Script

The Script below creates a Stored Procedure that returns a Macro SQL Statement. When this SQL statement is executed, it inturn returns BCP Out Statements for all the tables in a given database. The database name should be passed as a parameter to the procedure. Before the procedure is created, the SA Password must be […]

(1)

You rated this post out of 5. Change rating

2002-01-07

3,871 reads

SQLServerCentral Article

Review of Data Compare v.151

  • Article

In this product review Andy takes a look at Data Compare, the second of three products in the SQL Bundle available from Red-Gate software. It's a very handy program that lets you compare data between two tables and optionally generate sql statements to syncronize the data. An interesting alternative to replication!

You rated this post out of 5. Change rating

2001-10-31

8,805 reads

Technical Article

Transfer Logins and Passwords Between SQL Server 7.0 Servers

  • Script

The SQL Server 7.0 Data Transformation Services (DTS) Object Transfer feature transfers logins and users between two servers, but it does not transfer the passwords for SQL Server authenticated logins. (DTS in Microsoft SQL Server 2000 does transfer passwords.)

You rated this post out of 5. Change rating

2001-10-01

1,664 reads

Technical Article

Merge Wizard

  • Script

In our environment, we needed to create and drop replication over and over in our test environment and I got realy tired of having to manualy go to each table with an identity column to set its ranges. This sproc will create or drop the publications and/or subscriptions for all or some of the objects […]

(1)

You rated this post out of 5. Change rating

2006-11-15 (first published: )

763 reads

SQLServerCentral Article

Duplicate Key Inserted Error During Replication

  • Article

If you allow users write access to replicated tables on the subscriber, you can run into cases where a record is inserted on the wrong server - which will result in a replication stopping error if the same primary key is later inserted on the publisher. Find out how to fix it without pushing a new snapshot.

(1)

You rated this post out of 5. Change rating

2004-10-15 (first published: )

9,682 reads

Blogs

Five Ways Redshift Serverless Quietly Eats Your Budget

By

It is Friday, the queries are running, and nobody is watching the bill. That...

A Career of Memories

By

Annabel retired from Redgate Software this week. Across most of my career at Redgate,...

Rethinking Index Maintenance: Why avg_fragmentation_in_percent Is Outdated and What You Should Do Instead

By

As a SQL Server DBA with years of experience tuning production environments, I’ve seen...

Read the latest Blogs

Forums

What is the Cloud?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item What is the Cloud?

Changing the Schema

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Changing the Schema

Index Fragmentation Explained: Page Splits, Logical Reads, and What to Do

By Sanket Parmar

Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...

Visit the forum

Question of the Day

Changing the Schema

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
GO
I 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
GO
This worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3;
GO
What happens with this code?
SETUSER 'USER2'
GO
SELECT * FROM MySchema.MyTable
GO

See possible answers