Articles

SQLServerCentral Article

SQLsnake Worm Hits SQL Servers and Networks Hard

If you haven't changed the SA password on your SQL Server, you may be soon paying the price. Beginning last week, an old worm has come back in full force, infecting about 100 SQL Servers an hour. Reports of heavy port 1433 scanning began in early may but by the 22nd, the virus really began to take its hold on systems with no SA password.

You rated this post out of 5. Change rating

2002-05-28

4,813 reads

SQLServerCentral Article

Maintenance Plans - Behind the Scenes

Andy did "Under the Covers" last week, what the heck will it be next week? Read this article to see how maintenance plans update statistics, rebuild indexes, and remove free space from your databases. Add your comments to the article, maybe even a suggestion or two for better titles!

(1)

You rated this post out of 5. Change rating

2002-05-27

10,428 reads

Blogs

Flyway Tips: AI Generating Migration Script Names

By

AI is a big deal in 2026, and at Redgate, we’re experimenting with how...

The Book of Redgate: Get the right stuff done

By

Another of our values: The facing page has this quote: “We admire people who...

Runing tSQLt Tests with Claude

By

Running tSQLt unit tests is great from Visual Studio but my development workflow...

Read the latest Blogs

Forums

No Defaults Passwords Ever

By Steve Jones - SSC Editor

Comments posted to this topic are about the item No Defaults Passwords Ever

Introduction of OPTIMIZE_FOR_SEQUENTIAL_KEY = ON

By saum70

Hi, We have low latency high volume system. I have a table having 3...

The Long Name

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Long Name

Visit the forum

Question of the Day

The Long Name

I run this code to create a table:Create table with unicode nameWhen I check the length, I get these results:Table with length of name shown as 132 charactersA table name is limited to 128 characters. How does this work?

See possible answers