2005-11-23
1,403 reads
Security
2005-11-18
1,266 reads
2005-11-17
1,343 reads
2005-11-11
1,363 reads
2005-11-10
1,448 reads
SQL Server 2000 SP3 and xp_cmdshell Woes
The problems caused by the SQL Sapphire Worm, also know as the SQL Slammer, have caused many sites to do a quick upgrade to SQL Server 2000 Service Pack 3 (SP3). It includes the fix that prevents infection by the worm. While moving to the latest service pack is usually a good thing, to do so without thorough testing risks breaking a working application. That is exactly what happened to one of my clients over the weekend.
2005-11-02
2,068 reads
SQL Server 2005 Secures Your Data Like Never Before
Right out of the box, SQL Server 2005 does not install many of its services (such as SQL Server Reporting Services) or does not have features turned on by default (.NET integration), thereby reducing the attack vectors that hackers could use to compromise your data security.
2005-10-27
2,024 reads
2005-10-25
1,304 reads
2005-10-24
1,199 reads
2005-10-21
1,319 reads
Blogs
The Book of Redgate: We Value Teams
By Steve Jones
This value is something that I still hear today: our best work is done...
Troubleshooting TempDB Log Full Errors When SSMS Won’t Connect
By gbargsley
Have you ever received the dreaded error from SQL Server that the TempDB log...
Accelerating AI with Confidence: Why Microsoft Purview is Key to Responsible Innovation
By Chris Yates
Artificial intelligence is no longer a distant concept. It is here, embedded in the...
Forums
Planning for tomorrow, today - database migrations
Comments posted to this topic are about the item Planning for tomorrow, today -...
Bottlenecks on SQL Server performance
We have a BI-application that connects to input tables on a SQL Server 2022...
Is there some good routines for updating SQL Server database objects with GitHub
At work we've been getting better at writing what's known as GitHub Actions (workflows,...
Question of the Day
The Tightly Linked View
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