2005-11-17
1,343 reads
Security
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
2005-10-18
990 reads
Hacker's-eye view of SQL Server
If a hacker sets sights on your SQL Server, there are four primary methods he can use to take control and carry out unauthorized, malicious activity. I will look at each of these: Password compromise, Account compromise, SQL injection, Buffer overflows
2005-10-07
4,718 reads
Blogs
Redgate Summit Comes to the Windy City
By Steve Jones
I love Chicago. I went to visit three times in 2023: a Redgate event,...
Non-Functional Requirements
By Brian Kelley
I have found that non-functional requirements (NFRs) can be hard to define for a...
Techorama 2024 – Slides
You can find the slidedeck for my Techorama session “Microsoft Fabric for Dummies” on...
Forums
AG listener cant be removed
Testing with AG on Linux with Cluster=NONE. it was all going ok and as...
Remove comma inside Comma Delimited File csv in SSIS Using Script task
Hi, I have two tables: one for headers with 9 fields and another for...
Inserting 100K rows Performance - Baseline Performance
We're trying to understand how quick new versions of SQL server can be. Obviously...
Question of the Day
The "ORDER BY" clause behavior
Let’s consider the following script that can be executed without any error on both SQL Sever and PostgreSQL. We define the table t1 in which we insert three records:
create table t1 (id int primary key, city varchar(50)); insert into t1 values (1, 'Rome'), (2, 'New York'), (3, NULL);If we execute the following query, how will the records be sorted in both environments?
select city from t1 order by city;See possible answers