Administration

Technical Article

INF: Understanding How to Configure a SQL Server Connection Affinity

  • Article

In an online transaction processing (OLTP) environment, the connection affinity mask option may provide performance enhancement in high-end, enterprise-level SQL Server environments that are running on computers with 16 or more CPUs. In particular, this option is useful when there are a significant number of network interactions (more than 10,000 per second) between the middle-tier application servers and the back-end SQL Server system.

2001-08-28

1,500 reads

SQLServerCentral Article

Data Warehouse Version Management

  • Article

In most tables it is enough to have a stored procedure that performs Update Else Insert logic for data managment. However, in some cases we do not want to destroy the old data with an update statement. Instead we want to maintain history up to a certain number of versions. This article presents a method for doing so.

You rated this post out of 5. Change rating

2001-08-27

3,310 reads

SQLServerCentral Article

Design Oversight - Preliminary Review

  • Article

We all know what the ideal application design environment is for building a database back-end: an experienced DBA takes inputs from end users and developers and creates the database design in order to support the application being developed. But in reality, we don't get the opportunity to do application design like this very often. This article covers how to quickly find and fix problems in a design.

You rated this post out of 5. Change rating

2001-08-20

8,217 reads

Technical Article

Microsoft SQL Server 2000 Security

  • Article

This document introduces SQL Server administrators and developers to the new security features of SQL Server 2000. In addition to outlining the new features, there is a detailed discussion about how to best implement security in a Microsoft Windows® 2000 domain environment as well as source code examples.

2001-08-02

1,383 reads

SQLServerCentral Article

The Basics of Sizing a SQL Server Database

  • Article

Sizing a database can be one of the most arduous tasks a DBA, analyst or developer must attend to. It?s time consuming and more hours go into analyzing the database than actually sizing it. This article focuses on how to monitor the database?s growth after its deployed and contains some tips on how to size it before deployment. We will also dive a little into how to benchmark your database against a robust data load.

(21)

You rated this post out of 5. Change rating

2008-08-01 (first published: )

43,884 reads

Blogs

Prime Day Recommendations

By

It’s Prime Day. A few of my recommendations, since I want to do some...

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...

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