2004-01-12
1,999 reads
2004-01-12
1,999 reads
New author! Mahesh presents a solid overview of the replication architecture of SQL 2000.
2007-10-17 (first published: 2003-10-17)
45,495 reads
Changing a replicated table in SQL 7 was a lot of work. SQL 2000 offers some help, but in many cases it's not enough. This article by Andy Warren shows you which changes SQL 2000 will help you with and which ones it won't.
2003-08-08
14,407 reads
This white paper was written by Alain Dumas, founder of Sunopis. Looks interesting. Looks like they sell a tool that does ETL, replication, data cleaning, and more. We haven't reviewed the product, just thought it was something that might be of interest to our readers
2003-04-22
1,023 reads
There are times that you may find yourself on a project where you have one data source and need to publish to many subscribing databases. Often times, Replication is not looked at as a viable solution to achieving this goal. For this project, Demico and Lynn will demonstrate the way we utilized the Horizontal and Vertical partitioning capabilities that Microsoft has added to the Replication utility.
2003-02-07
5,461 reads
Now that Andy has converted Steve Jones to a DMO believer we asked him to spend some time discussing replication. In this kick off article he discussion snapshot replication at a very high level - and looking for reasons to use it. This article isn't about how to do snapshot replication, it's about whether you should.
2002-10-10
11,994 reads
How about getting the data when the table data is first queried? The following script checks to see if the specified table (@MyTable) has been updated today. If so, just return the data found. If not, then get the data from a "fresher source". Great for ASP that performs table reporting and needs "baked daily" […]
2002-04-23
1,564 reads
From this real-world case study, learn how you can boost SQL Server performance and scalability by off-loading reporting from your production SQL Server to a reporting server, using transactional replication.
2002-04-18
1,960 reads
Last year Andy wrote about turning off the log reader as a way to reduce the overhead on a server, primarily when you have many logreaders running. In this follow up article he talks about the downside of using this technique and how the behavior of the logreader can be "tweaked" to make using non-continuous replication a little less of a headache.
2002-03-28
5,158 reads
Direct from Microsoft, learn how to achieve scalable, high-performance merge replication applications.
2002-02-08
1,774 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