SqlCredit - Part 5: Adding Card, Vendor, and Purchase, Plus Much Refac
As I built out the last pieces of the original table set (Card, Vendor, and Purchase), I found a number of pieces that needed to be fixed in the design.
As I built out the last pieces of the original table set (Card, Vendor, and Purchase), I found a number of pieces that needed to be fixed in the design.
In this column, I discuss how SMO can be used to examine a database’s objects and to perform a variety of administrative tasks.
In this month’s installment, we will add security to the existing code and add new unit tests to prove that security.
In this month’s installment, we will discuss updates based on feedback from part 2 as well as introduce automated unit testing.
SQL Server 2005 has grown to include more versions of the platform than ever before. One of the newest is SQL Server Everywhere, now known as SQL Server Compact Edition. Jacob Sebastian brings us a great introduction for you to understand how this version disappears from the others and where it can be used.
Continuing with this series on building a database system
The purpose of the SqlCredit series is to demonstrate the database design and development portion of a development project. We will build a complete, functioning, tested credit card database to illustrate the complete software development lifecycle.
Making the transition from DTS in SQL Server 2000 to SSIS in SQL Server 2005 is quite a leap as the entire paradigm of ETL development has changed. New author U. K. Padjama brings us an article that compares DTS to SSIS and shows how to get started.
Business intelligence (BI) and service-oriented architecture (SOA) have conflicting principles and needs. This article will show you how to make peace between them.
A synonym is a new object to SQL Server 2005. It is a way to give an alias to an already existing object. For example, if you have a table named SalesHistoryFromArchiveF
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