Introduction to message-based applications in SQL Server 2005
Tim Chapman discusses the concept of message-based applications, and the new foundation for building these applications included in SQL Server 2005.
Tim Chapman discusses the concept of message-based applications, and the new foundation for building these applications included in SQL Server 2005.
I recently read a blog post on doing case-insensitive text searches on SQL Server 2005. The post said that an index on a computed column might be used even if the computed column itself wasn't used in the WHERE clause. I was curious to test that and see how far I might take it.
SQL Server 2005, the next evolution of SQL Server, should be growing the capacities as well as the capabilities of the product. With some research, Steve Jones brings you the best current information he could find about SQL Server 2005, comared with the SQL Server 7 and 2000 values.
Damon Armstrong presents an extremely powerful and flexible token replacement mechanism for your ASP.NET applications. It is based on regular expressions so allows you to search for dynamic text, instead of just a static token, in a given string.
Service Broker is one of the more interesting and useful new enhancements in SQL Server 2005, however many DBAs are not familiar with this subsystem. New author Santhi Indukuri brings us a practical example of how you can build a distributed application using Service Broker.
This article deals specifically with insider threats to IT describing how IT professionals are implementing the necessary products, policies, and procedures to reduce insider threats and provide the necessary reporting for regulatory compliance.
This is the fourth part of an ongoing series. The series is titled The Data Stewardship Approach to Data Governance. For information regarding future chapters, please use my contact information below. Previous articles were titled The Data Won't Govern Itself, Data Governance Is NOT a Methodology and The Tools of Data Governance.
Arthur Fuller recently instructed a colleague on how to automate the process of trimming table data in SQL Server 2005. Find out how he is able to turn an onerous task into a breeze.
One of the best benefits of the .NET Framework over lower level programming is that it enables developers to create very complex, custom solutions, without writing low-level code. Zach Smith explores how you could take advantage of the built-in .NET Framework functionality to develop a simple object oriented database in less than 140 lines of code.
Every DBA should know what is going on with their database servers, but this is a chore that requires some type of tool to help. SQLCentric from Pearl Knowledge Solutions is a tool that can help you and SQL Server MVP Satya Shyam brings us a look how to setup and use this tool in your environment.
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