SQLServerCentral Article

Who Is Using SQL Server 2005?

The release of SQL Server 2005 is a few months away and there are many people that are excited and looking forward to moving the new release into production. But what percentage of people are really looking to adopt the new platform soon? Edgewood Solutions has put together a survey to see. Enter and you could win a prize.

SQLServerCentral Article

Where Logic Lives

We recently published an article about logic in the database about how you might structure the TSQL code in your SQL Server and decide what goes inside the database. New author Mike Dillon brings us a response to that article and some ideas about how you might make those decisions.

SQLServerCentral Article

Adventures in Replication

SQL Server 2000 replication is the easiest so far to setup and work with. However there are some areas that you can get yourself into trouble with if you are not careful. New author Chris Rock brings us a few lessons learned in getting replication working with a remote office.

External Article

SQL Server 2005 - SQL Server Integration Services - Part 6

In this article, we are continuing coverage of Foreach Loop container functionality, by discussing different types of loop enumerators. So far, we have presented methods for working with files in a folder as well as records in a recordset (using Foreach File and Foreach ADO enumerators, respectively). Our next enumerator is based on the SQL Server Management Objects technology (hence it is referred to as the SMO enumerator), which is the SQL Server 2005, .NET-based management framework providing replacement for COM-based DMO (Distributed Management Objects) that served an equivalent role in earlier versions of SQL Server.

Technical Article

Business Intelligence with SQL Server Reporting Services - Part 3

Reporting Services exposes web methods via XML web services to facilitate cross platform reports management and delivery. It's a simple SOAP based API makes it very easy to add full functionality of reporting services in your application. It provides a set of rendering and viewing functions as well as complete set of management routines. Reporting services web service is the one stop shop for subscription, management, publishing, scheduling and rendering reports.

Blogs

Fabric for Operational Reporting & SQL Endpoint Trap

By

With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...

Crawl, Walk, Run with Agentic Development of Power BI Assets

By

If you’ve been watching AI roll through the data community and thinking, “this seems...

How AgentDBA Diagnoses SQL Server Issues Fast

By

Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...

Read the latest Blogs

Forums

SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About

By Terry Jago

Comments posted to this topic are about the item SQL Art, Part 4: Happy...

Finding 'bad' characters

By Barcelona10

Hi All I am trying to find 'bad' characters that users might type in....

Extreme DAX: Take your Power BI and Fabric analytics skills to the next level

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Extreme DAX: Take your Power...

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