The Small Print
In today's guest editorial, Phil Factor issues a stark warning against cunning salesmen and hidden costs in cloud computing.
In today's guest editorial, Phil Factor issues a stark warning against cunning salesmen and hidden costs in cloud computing.
Phil Factor is puzzled by reading how difficult a relatrional database is to use for certain tasks.
Check tempdb to see if it has been autogrown since the last restart. If it has, there may be an opportunity to improve server performance.
Recently we started experiencing a very strange issue in our production reporting environment where the Re-indexing and Update Statistics operation suddenly began taking more than 2 days to complete and was thus causing blockage in the database which in turn caused impairment in application performance.
It's incredible what humans can accomplish when they work on a problem with passion. This editorial was originally published on Mar 20, 2008. It is being re-run as Steve is on vacation.
This week Steve Jones looks at the expected lifetimes of SSDs and finds one that might be a nice upgrade for your system.
When you have SSAS cubes with millions of rows of data, it is very helpful to create partitions. If you have a few cubes you could probably do this manually, but if there are many or if you want to automate this process you should look for smarter solutions such as programming the creation of partitions dynamically.
SQL Saturday in the Ukraine. If you want a free day of training, sign up and attend.
The final day of Simon's journey to improve his OLAP knowledge and build a prototype cube.
This article explains how to use the GROUPING clause to generate subtotals for rows in a very easy fashion.
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