SQL Server Data Import System to Alert For Missed Imports
In this tip Tim Smith looks at how to set up a system that allows automatic notification if a process doesn't import new data into SQL Server.
In this tip Tim Smith looks at how to set up a system that allows automatic notification if a process doesn't import new data into SQL Server.
So you're keen to take the first steps to the continuous integration of your database. You have to start by getting your database into source control. You can then begin to automate your build processes in order to generate and test a database. By doing this regularly, you'll be much better prepared for the deployment process because you'll have solved integration issues when they happen, and facilitated the broader testing process.
A checklist to help optimize the performance of SQL Server
SQL Saturday is coming to Nashville on January 17 for a free day of SQL Server training and networking. There will also be paid-for pre-cons to this event on Thursday and Friday, so register while space is available.
In order to analyze the data in a line chart better, we want to add trendlines to the graph, such as a weighted average. Here's how to add a "calculated series" to a line chart easily in SQL Server Reporting Services.
The next time you are tempted to hammer a performance problem with hardware, why not instead invest that time in hammering and refining your SQL queries? There are rich rewards to be had.
PowerShell is a very popular and powerful feature in the Microsoft stack. It is extensively used for development, deployment and administration across various ecosystems like SQL Server, SharePoint, Azure Cloud and others. PowerShell cmdlets are available for HDInsight as well and in this tip we will take a look at fundamental aspects of Microsoft Azure PowerShell for HDInsight.
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