SQL Server Management Objects
In this column, I discuss how SMO can be used to examine a database’s objects and to perform a variety of administrative tasks.
2007-06-18
2,930 reads
In this column, I discuss how SMO can be used to examine a database’s objects and to perform a variety of administrative tasks.
2007-06-18
2,930 reads
In this month’s installment, we will add security to the existing code and add new unit tests to prove that security.
2007-06-15
2,657 reads
In this month’s installment, we will discuss updates based on feedback from part 2 as well as introduce automated unit testing.
2007-06-14
2,494 reads
Continuing with this series on building a database system
2007-06-13
3,926 reads
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.
2007-06-12
3,306 reads
Business intelligence (BI) and service-oriented architecture (SOA) have conflicting principles and needs. This article will show you how to make peace between them.
2007-06-11
6,335 reads
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
2007-06-08
3,890 reads
If you've ever used SQL Server 2005 Integration Services (SSIS), you will have come across raw files. Microsoft introduced them with SSIS as a mechanism for storing data on the local file system. The design of raw files enables data to be written very quickly but, unfortunately, to achieve this performance Microsoft has used a proprietary binary storage format.
2007-06-07
3,167 reads
The only way to guarantee that your business rules are always enforced for all your data is by using constraints. Learn how to use them to enforce business rules in the database.
2007-06-05
3,215 reads
In systems that require, for auditing purposes, advanced logging and reproducibility of reports between runs, a straightforward update, insert, or delete may be counter-productive. In such circumstances, a bitemporal model is necessary
2007-06-04
2,464 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers