Technical Article

Teach Old Data New Tricks with the Fully Loaded Advances in ADO.NET 2.

The Microsoft® .NET Framework 2.0 delivers an updated ADO.NET that will streamline your data access development efforts. The ADO.NET team has worked with both the System.Xml team and the SQL Server™ team to provide a consistently rich developer experience, crossing technology boundaries from ADO.NET to XML and back. This will all be apparent as you dig into ADO.NET 2.0. There are improvements on so many fronts that you will certainly be pleased.

Rather than attempt to list every new and updated feature of ADO.NET 2.0, I will discuss in detail some of the more interesting improvements and focus on performance and flexibility.

SQLServerCentral Article

The Multi Phase Data Pump

SQL Server 2000 has an amazing ETL tool in Data Transformation Services that is included at no charge, something none of the other database vendors include. DTS has great flexibility to make your job easier, but it has some quirks in this version. The Multi Phase Data Pump is hidden inside the tool, but can provide a great programming environment and Dinesh Asanka brings us a look at what you can do wit this tool.

Technical Article

Using Source Control to Develop Smarter

Veteran and novice developers alike need source control management (SCM). Also known as asset management, and source code management, SCM helps you (and your team) manage development projects, and the components and code that make up the project.

There are many benefits to using source control management, most notably the ability to develop code faster, smarter and more accurately. Source control management tools help you control your code; especially in multiple developer projects.

Technical Article

The Trustworthy Computing Security Development Lifecycle

This paper discusses the Trustworthy Computing Security Development Lifecycle (or SDL), a process that Microsoft has adopted for the development of software that needs to withstand malicious attack. The process encompasses the addition of a series of security-focused activities and deliverables to each of the phases of Microsoft's software development process. These activities and deliverables include the development of threat models during software design, the use of static analysis code-scanning tools during implementation, and the conduct of code reviews and security testing during a focused "security push". Before software subject to the SDL can be released, it must undergo a Final Security Review by a team independent from its development group. When compared to software that has not been subject to the SDL, software that has undergone the SDL has experienced a significantly reduced rate of external discovery of security vulnerabilities. This paper describes the SDL and discusses experience with its implementation across Microsoft software.

External Article

All about the 'Case'

When installing SQL Server, regardless of versions and editions, SQL Server database administrators tend to choose the default collation and sort-order, which is SQL_Latin1_General_CP1_CI_AS. Though case insensitiveness makes the life of the database developers and database administrator's easy, there are situations where case sensitivity should be enforced just as password checking is enforced.

In this article, I would like to discuss different methods for achieving case sensitivity in a case insensitive database/server.

SQLServerCentral Article

Automating DTS Execution

Database Transformation Services (DTS) in SQL Server 200 was a breakthrough tool, really paving the way for a low-cost, easy to use, ETL tool. However, it was not a true robust programming environment and contains quite a few quirks that are apparent as you get into more detailed packages. New author Gus Carnu addresses one of those issues with a look at the ExecutePackage task.

SQLServerCentral Article

An Identity Crisis

SQL Server includes autonumber of identity columns despite the fact that they are not SQL-92 compliant. There is quite a bit of debate over the use of them in your database, but if you do decide to use them, you should be aware of potential problems. New author Troy Ketsdever brings us a story about his identity crisis and how it was solved.

External Article

SQL Server 2005 Security - Part 4

In this article, we will conclude our coverage of security related changes in SQL Server 2005 Beta 2 (although we will continue discussion of improvements in other functionality areas throughout the reminder of this series). The topics we will focus on here are code and module signing, modifications of SQL Server Agent and SQL Profiler operations, as well as monitoring and auditing changes.

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