Big SQL Server 2005 News
Confidential until the official release at 9:00am Pacific Time today. Check back after that time to get the big news!
Confidential until the official release at 9:00am Pacific Time today. Check back after that time to get the big news!
If you are working with SQL Server 2005, you really need Visual Studio 2005 as well. And since they are both in Beta, there are some interesting issues when installing both of these pre-products. New author David Russell brings us some technical notes he made while installing both of these many times in a corporate environment.
You may never need to work with them, but if you do then you will quickly realize how complicated barcodes can be. Michael Coles recently had a project and developer a toolkit to actually print barcodes from SQL Server.
The regular expression transformation exposes the power of regular expression matching within the pipeline. One or more columns can be selected, and for each column an individual expression can be applied. If all columns selected pass their tests then rows are passed down the successful match output. Rows that fail to pass all tests are directed down the alternate output.
Clustering, partitioning, database snapshots, database mirroring, SQL Server SAN storage design and more are all in the September issue of the SQL Server Standard.
SQL Server 2000 has a fantastic subsystem for alerting the DBA and keeping him or her informed as to the state of the server. However the email subsystem introduces a dependency on Outlook for alerts that can be a problem for some environments. Author Roy Carlson brings us an ingenious method for reading logs and sending alerts without Exchange or Outlook.
Hopefully you've heard about Reporting Services. But have you tried it? James says you'll be sorry if you don't read the docs first! Reporting is something every enterprise struggles with, maybe this will make things better? Here's how to get started.
Lest the headline mislead you as to my biases, I consider software patents to be both stupid and insane. I raise this issue because it is currently rearing its ugly mug in the world of open source software, but it has affected much development in the proprietary worlds of Windows as well.
First of all, patent laws were created long ago, which is not to say the thinking was correct then either, but we have to recognize the intellectual and technological climate back then.
We have a few interviews of the SQL Server team and this time we talk with the lead for Notification Services. Get some insight into Shyam Pather and and this add on for the SQL Server 2005 platform.
Don Kiely contends that exercising administrative rights over our computers is a major cause of insecure systems. In the first of five articles, he explains the concept of "least privilege" and shows why software developers should be happy to operate as "mere users."
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
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...
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