Track source dates when loading a data warehouse
A primer on how to reduce network and source system load when reading a relational source into the data warehouse.
A primer on how to reduce network and source system load when reading a relational source into the data warehouse.
Service Broker is a technology built into SQL Server and utilized by the engine for its internal asynchronous processing. The great thing about Service Broker is that its functionality is exposed so we can build our own custom data integrations. Deanna Dicken introduces you to the concepts needed to create a service broker integration.
Great DBAs collect all kinds of metrics on their instances and let them manage themselves. However many administrators need help monitoring and interpreting the data. Today Steve Jones asks if you think this data needs extra security or is it less of an issue than other PII data.
This article shows a few simple techniques to summarize table data using T-SQL.
This component needs little explanation. It generates random integer (DT_I4) and string (DT_WSTR) data and places them in the pipeline. You specify how many columns of each you would like and for any string columns you pass a fixed length value. You then need to specify how many rows in total you require to be generated. This component is used by us to do testing of the pipeline and components downstream.
Dropbox has grown tremendously in the last few years and Steve Jones talks about a concept of running with less headroom as a way to cope with that rapid growth. Is it something you'd be interested in with a SQL Server?
SMO can be a valuable tool for working with SQL Server when you don't have access to all the tools that come with the platform. In this article, SMO helps solve an issue with a SQL Server.
Sparse columns and column sets in SQL Server 2012 provide a way of accomodating the less-structured data that has always proved to be tricky for the relational model. They can be used very effectively where the attributes are sparse for any given entity and very numerous across all entities. Seth Delconte shows how to use them.
Free training in New York. Come learn about SQL Server, meet other pros, and then enjoy a night in the city.
Today Steve Jones talks about how you can find a really good job. And how you can make changes in your life to get you there.
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,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
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
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
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