SSIS Basics: Data cleansing using derived columns
On this article I will show you how to perform a basic data cleansing using the derived column data transformation
On this article I will show you how to perform a basic data cleansing using the derived column data transformation
On Monday, Sep 24, 2018, at the Ignite 2018 conference, Microsoft announced the first public preview of SQL Server 2019 (community technical preview (CTP) release of SQL Server 2.0).This new release of SQL Server is packed with many new features to improve performance, integrate your increasing volumes of corporate data, beef up security, and more.
Doing the same thing for too long, and not enjoying it, isn't good for anyone. You might be burned out, or as Steve Jones notes, you might need to change our perspective.
This article will show how you can get the column name for error rows in an SSIS 2016 Data Flow task.
The Extended Events (or XEvents) feature has been part of SQL Server since 2008, but many database professionals struggle to get started using it. In this article, Phil Factor demonstrates several useful Extended Event sessions that measure just one thing in each. He then provides the code necessary to parse the resulting XML into something you can use.
It doesn't seem to be a feature that an auditing system can fail, but the application being audited continues to run.
SQL Server 2016 & 2017 enable a new way to get query performance metrics live via Extended Events.
Whoever creates an AlwaysOn group is, by default, the owner of the endpoint. This is generally not a problem…unless that person leaves the company and you need to delete the login.
When you take a job, do you ask about holidays? Do you consider them a benefit? Andy Warren asks what those holidays might mean to you.
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