Joining Tables Part 2
In this session, Kathi continues her popular series and shows some of the more advanced joining techniques in T-SQL. She shows T-SQL self, outer and cross joins and gives many examples on how to use them.
In this session, Kathi continues her popular series and shows some of the more advanced joining techniques in T-SQL. She shows T-SQL self, outer and cross joins and gives many examples on how to use them.
Relational Data Warehouse or Reporting work loads are characterized by low volumes of very large transactions. These applications are often identified as having predominately read workloads (e.g. Decision Support, Analysis, and Reporting) with periodic feeds or batch loads. It is important to keep these characteristics in mind as we examine the significance of database design, resource utilization and system performance. The top performance bottlenecks or gotchas to avoid for Data Warehouse or Reporting applications are outlined below.
SQL Maestro, maker of tools for a variety of database platforms, is offering a 20% discount on their tools to the SQLServerCentral.com
community.
A whitepaper on getting the best performance from your system.
The topic of cursors is the ultimate "hot potato" in the world of SQL Server. Everyone has a view on when they should and mainly should not be used. By example and testing Robyn Page proves that, when handled with care, cursors are not necessarily a "bad thing".
Maintaining SQL Server security is fast becoming a big part of a SQL Server DBA's job. Longtime security expert Brian Kelley takes a
look at a security scanner: Typhon III
This article shows how the Fuzzy Lookup Transformation in SQL Server Integration Services (SSIS) can be used to make matches.
Danny Lesandrini reviews SQL Refactor, a SQL Server Add-In that works with the new SQL Server Management Studio.
We continue with our look at the people behind SQL Server with a very interesting interview from one of the senior support
engineers, Bob Dorr.
This series will illustrate the various ways of using the SQL Server 2005 command line utility “SQLCMD”.
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