Foreign Keys
Foreign keys are an important part of a relational database. New author Ravi Lobo takes a look at foreign keys from the perspective of a new DBA with some scripts to help you ensure your database is setup correctly.
Foreign keys are an important part of a relational database. New author Ravi Lobo takes a look at foreign keys from the perspective of a new DBA with some scripts to help you ensure your database is setup correctly.
Should IT managers understand technical issues, or is a full appreciation of the technology somehow unworthy and unnecessary for senior staff? In such a rapidly changing industry where fortunes are made and lost by attempting to exploit gaps in the market too thin to see with the naked eye, the answer would seem obvious. However, I have repeatedly come across amazing gaps in the technical knowledge of managers.
One of the difficult parts of developing anaylsis services cubes is determining which aggregations should be chosen. Yaniv Mor brings us the second part of his series and examines using Usage Based Optimization in SQL Server 2005.
This project was done using SQL Server 2005 Enterprise Edition (with SP1 beta) using the BULK INSERT command with 60 parallel input files, each of approximately 16.67 GB. The best time I got was 50 minutes. Hewlett Packard was kind enough to loan me some time one night on the machine they use to do the TPC-H tests. It is an Itanium2 Superdome with 64 1.6GHZ 9M (Madison) CPUs. For the insert tests the system was equipped with 256GB of RAM. The HP SAN configuration is rated at 14GB per second throughput.
At just about every talk I give I always try to make several consistent statements. One of which is: ‘Whenever possible use stored procedures to access your data’.
Let me start by stating some disclaiming remarks. I'm not against stored procedures in general, I find that the choice why procedures should be used, should be based on proper facts, not on claims without any proof.
Part 1 of a 4 part series about ADO, this is a beginner level article designed to get you started using the ADO connection object. If you haven't used ADO so far, why not see what it's all about?
This is a good explanation on how to acctually bill a customer for your service over a credit card in your web application.
Everyone wants a highly available system, but achieving 4 or 5 9s of uptime is hard to do. Especially when you have cost limitations. New author Mark Cook takes a look at how his company analyzed the challenges and which method they chose along with some implementation details.
Continuing our coverage of topics dealing with various aspects of managing SQL Server 2005 Integration Services packages, which we started with an overview of their storage and deployment, we now turn our focus to their execution.
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