2005-12-07
1,290 reads
2005-12-07
1,290 reads
2005-11-23
1,411 reads
2005-11-18
1,274 reads
2005-11-17
1,353 reads
2005-11-11
1,374 reads
2005-11-10
1,456 reads
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
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,315 reads
2005-10-24
1,209 reads
The first version of my accounting assistant could not find a single purchase of...
Why isn’t AI paying off yet? Drawing on lessons from digital transformation, Joyful Craftsmen...
By Steve Jones
I’m really excited about some growth in Flyway support. I’ve been asking about this...
Comments posted to this topic are about the item Pay for Performance, which is...
Hi I have this slow query that is pulling data from a linked server....
Comments posted to this topic are about the item Too Many Choices
I have a table, dbo.MasterBrands, with this data:
BrandID OfficialName 1 Samsung 2 Apple 3 Microsoft 4 Adidas 5 Coca-ColaI run this query. What is returned for Coca-Cola?
SELECT CHOOSE(BrandID, 'Conglomerate', 'Tech and Design', 'Desktop', 'Apparel') FROM dbo.MasterBrands;See possible answers