The Daily Database Build
From SQLTeam's Bill Granazio, a look at how he ensures his database scripts are always working.
From SQLTeam's Bill Granazio, a look at how he ensures his database scripts are always working.
Continuing with Dinesh Asanka's series on SQL Server and Infopath 2003, he shows us this time how to build a report that joins two tables and includes some conditional formatting. Infopath 2003 is part of Office 2003 and is a great quick and dirty tool for getting to your SQL Server data.
A short tutorial on building database back-ended applications with SQL Server and CE. If you're looking to build mobile apps, this is a good place to start.
We've added a new store section. Read on and visit to see if there's anything worth your while.
In this article, we will examine "rolling average" aggregations, a common business requirement. "Rolling," or "moving," averages, involve a measure, the average under consideration, that is aggregated over a progressively moving window of time periods.
Do you have a SQL Server disaster plan? What about something less than a disaster? Steve Jones has worked more than his share of disasters or incidents, some of them self-inflicted. He's taken some of his experience and started a new series looking at a framework for dealing with incidents. Read part 1 about getting prepared.
In this article, we began with a discussion of general business needs as related to the concept of relative time. We then undertook a practical, multi-step exercise, based upon a hypothetical business need, to illustrate a potential solution for a stated requirement.
NULL values in columns can indicate a few things, the value isn't known, it's not yet been filled in, or perhaps, as Leo Peysakhovich argues, the column isn't being used? How many SQL Server tables do you have with extra tables and columns that are not being used? Or maybe never have been? This article looks at a statistical analysis of columns using NULLs to determine if you might be able to remove certain columns.
In this article and others subsequent to it, we will focus on time considerations in our MDX queries., and how we can successfully report change over time, as well as to accumulate those changes to present the precise snapshots, trends and other time-based metrics so dearly appreciated in business.
Hurricane Charlie had a pretty substantial impact on residents and businesses in Central Florida. Andy lives in the Orlando area and wrote up some notes on the various challenges he ran into it. Out of it you might find a couple things worth thinking about adding into your DR plan.
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