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
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