One of the more controversial new features in SQL Server 2005 is the inclusion of the Common Language Runtime (CLR) inside the server. Whether you agree this is a good idea or not, the very knowledgable Chris Hedgate brings us the first article in a series looking at how the CLR fits into your database server.
Microsoft describes its new, free SQL Server 2005 Express Manager (XM) as a "lightweight" database management tool built on top of the .NET Framework 2.0. Better yet, not only can you use XM to manage SQL Server 2005 Developer and Express Edition databases on local and remote computers, you can also use it with SQL Server 2000 and SQL Server 2000 Desktop Engine (MSDE 2000) databases. In this article, Rick Dobson shows you what XM offers DBAs.
Users call and complain and by the time you get to the server, everything looks fine. Even running Profiler sometimes doesn't capture the information. Author Roy Carlson found a solution, a script that you can give to users to dump whatever information you need to an Excel file.
Judging by mainstream news coverage over the past few weeks, the issue of data theft, particularly loss of backup tapes, has reached the tipping point. It might mean that your relatively anonymous existence within your company could come to a screeching halt.
A look at how encrpytion might be if importance to your company.
As we briefly mentioned in the previous installment of this series, among features introduced in the SQL Server 2005 Integration Services there are For and ForEach loops, implemented in the form of containers that can be incorporated into the Control Flow part of a package design.
The Microsoft .NET 2.0 platform introduces a new namespace called System.Transactions that brings in a lightweight, simplified transaction model. This article discusses the shortcomings of current transaction models and introduces System.Transactions for .NET Framework 2.0 beta 2.
Currently there are two transaction models available in the .NET world, both of which are suited for certain situations. The first is part of the rich ADO.NET data providers. The second is the enterprise services transaction. Before we examine System.Transactions, let’s have a look at the current models.
Article number four in this popular series continues exposing Worst Practices! This week Andy continues his tirade by talking about why case sensitive databases should be BANNED from the planet. Is he right or just OUT OF CONTROL? Read the article and join the discussion - your comment may lead to an article, that's what generated this one!
The term “Enterprise Metadata Management” has been in use since the late 1980’s when many of us worked in classic “mainframe environments” using “corporate data dictionaries” to manage our COBOL programs, Job Control Language (JCL), screens, reports, copybooks, and database schema definitions. Fast-forward to 2005 ~ has anything changed? What does “enterprise metadata management” mean today ? I recently surveyed a number of leading metadata management vendors, Global 5000 companies, and industry thought-leaders seeking their input.
In the race to secure data, one basic measure – encryption – is often overlooked. Philip Basham takes a look at the ramifications of data loss and how it can be prevented.
Two in a month? Steve Jones brings us another mistake made by a DBA in SQL Server. Everyone makes them and we may not like to admit to them, everyone that we print hopefully helps a few other SQL Server DBAs avoid that particular mistake. This one looks at the dangers of sorting by aliases.
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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