Reporting Services!
Mike takes a good first look at Reporting Services. We're trying to add some coverage of this interesting new product. This gives a good overview from a real user perspective.
Mike takes a good first look at Reporting Services. We're trying to add some coverage of this interesting new product. This gives a good overview from a real user perspective.
Dinesh ran into a situation where a client had very specific requirements for generating keys. Take a look at the solution, can you better alternatives? Sometimes you just can't talk the client into changing!
As Robin points out there is no built in way to make sure users have strong passwords when using SQL authentication. There are a couple changes you can make (with appropriate warnings!) that will allow you to do this. Read on to find out why and how.
New Author! We've run a couple articles on similar topics, this one takes a slightly different approach. It's a short article and has two scripts included.
One of the biggest hurdles people new to the IT field face is getting access to all the software they need so they can learn. This new program from Microsoft offers a TON of software for under $400. Caveats apply (don't they always?) but it's worth the 5 minutes to read what it takes.
We've been trying to catch up on reviews lately, Hai was kind enough to give Entegra a try and report back on it. The basic concept is that it lets you do extensive auditing without having to add triggers. If you're trying to find an auditing solution, this is worth considering.
This isn't a SQL site nor can you easily do regular expressions from SQL. That said, sometimes regular expressions are EXACTLY what you need to solve a problem. The downside? They're tricky! This is a great resource to pass on to your development team.
This is a tool to generate C# code based on a sql script. Source code is also available for download. It's free! One caveat is that the site is in Italian.
This article is for developers (and is in C#), looks at how you can avoid requerying by storing data in a hashtable. Mainly code, but you may get a good idea or two from it.
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
It is Friday, the queries are running, and nobody is watching the bill. That...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
Comments posted to this topic are about the item Extreme DAX: Take your Power...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item 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 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