More Overloads
The overloading of terms creates confusion, which means that communication is more difficult.
The overloading of terms creates confusion, which means that communication is more difficult.
Power BI is as extensible as it is powerful In this article you will see how to impress your users with added visuals
For T-SQL Tuesday #78, Aaron Bertrand takes a look at whether RID Lookups are faster than Key Lookups, with a small battery of fairly simple duration tests.
A great developer is worth more than an average one, but how much more? Steve Jones has a few thoughts for you to think about.
When wrestling with technical problems or ideas, it is good to discuss with, argue against, present ideas to, and listen to your colleagues. This is true of anyone working in IT, but really important for the likes of database professionals who are engaged in a very rapidly-developing engineering specialism that demands that you keep up […]
The most frustrating thing with any new system is often just working out how to connect to it. Oddly, you can’t use SSMS with SQL Data Warehouse, but it is fine with SSDT, SSIS, Power BI desktop, sqlcmd, BCP, and a range of Microsoft cloud services - there are PowerShell Cmdlets too. Rob Sheldon provides the details.
Today we have a guest editorial from Kellyn Pot'Vin that tackles the tough topic of diversity.
This article describes methods of creating dynamic queries without the use of dynamic SQL to efficiently access large tables.
SQL Server database developers seem reluctant to use diagrams when documenting their databases. It is probably because it has, in the past, been difficult to automatically draw precisely what you want, other than a vast Entity-relationship diagram. However, you can do it without buying any third-party tool, just using some existing Java-based open-source tools; and can even automate it entirely, using SQL and PowerShell. Phil Factor shows how.
Diagnosing and resolving parallelism-related latching and blocking in SQL Server using DMV’s, the activity monitor, procedure execution plans, and index tuning.
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