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
Every organization I talk to has the same problem dressed up in different clothes....
By DataOnWheels
I am delighted to host this month’s T-SQL Tuesday invitation. If you are new...
By alevyinroc
Ten years (and a couple jobs) ago, I wrote about naming default constraints to...
Comments posted to this topic are about the item The day-to-day pressures of a...
Comments posted to this topic are about the item Using OPENJSON
Comments posted to this topic are about the item Data Modeling with dbt for...
I have some data in a table that looks like this:
BeerID BeerName brewer beerdescription 1 Becks Interbrew Beck's is a German-style pilsner beer 2 Fat Tire New Belgium Toasty malt, gentle sweetness, flash of fresh hop bitterness. 3 Mac n Jacks Mac & Jack's Brewery This beer erupts with a floral, hoppy taste 4 Alaskan Amber Alaskan Brewing Alaskan Brewing Amber Ale is an "alt" style beer 8 Kirin Kirin Brewing Kirin Ichiban is a Lager-type beerIf I run this, what is returned?
select t1.key
from openjson((select t.* FROM Beer AS t for json path)) t1 See possible answers