A SQL Server 2005 feature that I appreciate and want to demonstrate is the OUTPUT clause. The OUTPUT clause helps in returning the actual data from a table soon after an insert. Applications require return values such as the new identity value, the computed column value or the default value generated by the default constraint.
The third part of a great data warehousing series from Vincent Rainardi looks different methods of extracting data from the source system along with the advantages and disadvantages of each.
This article examines the problem of complex data in integration projects and presents solutions for handling this data to create seamless integration throughout the enterprise.
After a bit of a hiatus, the interviews are back. This time we take a few minutes with Dan Jones of the SQL Server development team.
Testing is key to ensuring a process actually works when it comes time to implement, rather than finding out when time may be of the essence. This holds true for testing SQL Server restores as well.
Joe discusses why he prefers command line tools over GUI, then launches into a how-to about querying sysperfinfo to resolve performance issues. Couple nice sample queries included!
If you deliver applications to a customer, then you have struggled with the challenges of updating schemas as they change. New author Serhiy Snisarenko brings us his comprehensive process and code to make this task easier.
A SELECT query returns results as a rowset. You can optionally retrieve formal results of a SQL query as XML by specifying the FOR XML clause in the query.
The second part of a great data warehousing series from Vincent Rainardi looks at the decision to stage data prior to moving it into the warehouse versus directly loading it. This is a must read for those contemplating a data warehouse.
Throughout our series of articles dedicated to SQL Server 2005 Integration Services, we have been working mainly with packages using the Business Intelligence Development Studio interface (although more recently, we also discussed SSIS-related functionality available in SQL Server Management Studio). Even though, as part of our exercises, we have worked with a number of packages, we have not yet explored the various options related to their storage. We will cover them in this article
By gbargsley
Have you ever received the dreaded error from SQL Server that the TempDB log...
By Chris Yates
Artificial intelligence is no longer a distant concept. It is here, embedded in the...
Every Scooby-Doo mystery starts with a haunted house, a strange villain, and a trail...
At work we've been getting better at writing what's known as GitHub Actions (workflows,...
Comments posted to this topic are about the item The Tightly Linked View
Comments posted to this topic are about the item Build a Test Lab of...
I try to run this code on SQL Server 2022. All the objects exist in the database.
CREATE OR ALTER VIEW OrderShipping
AS
SELECT cl.CityNameID,
cl.CityName,
o.OrderID,
o.Customer,
o.OrderDate,
o.CustomerID,
o.cityId
FROM dbo.CityList AS cl
INNER JOIN dbo.[Order] AS o ON o.cityId = cl.CityNameID
GO
CREATE OR ALTER FUNCTION GetShipCityForOrder
(
@OrderID INT
)
RETURNS VARCHAR(50)
WITH SCHEMABINDING
AS
BEGIN
DECLARE @city VARCHAR(50);
SELECT @city = os.CityName
FROM dbo.OrderShipping AS os
WHERE os.OrderID = @OrderID;
RETURN @city;
END;
go
What is the result? See possible answers