Additional Articles


Technical Article

Auditing Your SQL Server Environment Part I

This article is the first of a series that I plan on writing and placing on my website to help other DBAs in auditing a new SQL Server environment. This article deals with determing which SQL Server logins have weak passwords, with the definition of weak being, no password, password the same as the login name or having a password of only one character.The stored procedure used for this article is embedded in the article and it has been submitted as a independent script named spAuditPasswords.

2003-01-21

66 reads

Technical Article

forceSQL - Free SQL Password Auditing Tool

forceSQL v2.0 is a much improved version of our SQL Password command-line tool. It now incorporates Brute Force in addition to Dictionary attacks. It works significantly faster because it now bypassess the SQL/ODBC API and directly goes to the network.
A free download and a much more detailed description is available at http://www.nii.co.in/tools.html

2002-12-23

48 reads

Technical Article

Best SoftTool Announces SQLSourceSafe 2.0

Best SoftTool, Inc. today announces that its flagship product SQLSourceSafe 2.0 is available for download and purchase. SQLSourceSafe is the integrated solution that Best SoftTool provides to meet the mounting market demand for a solid version control system for SQL Server database development. SQLSourceSafe integrates Microsoft Visual SourceSafe® and Microsoft SQL Server® together, offers robust and advanced version control functions to database scripts in SQL Server.

2002-11-18

59 reads

Blogs

Accessing the Data API Builder MCP Server from VS Code

By

I recently started playing with the MCP Server for SQL Server, which is a...

From DBA or Data Engineer to AI Engineer: A Realistic Path

By

If you spend your days tuning queries, managing pipelines, or keeping a production database...

Asynchronous Replication of Snapshots from an ActiveCluster Pod to a Third Array

By

I’ve been rebuilding my three-site SQL Server demo lab, and I ran into something...

Read the latest Blogs

Forums

ALAMAT BCA KCU TEGAL Tlp:08218154374

By layanan_Bca88

Hub Via Wa 628218154374 Alamat Jl. A. R. Hakim No.2, Mangkukusuman, Kec. Tegal Tim.,...

ALAMAT BCA KCU SALATIGA Tlp:08217555651

By m4rt1n4

Hub Via Wa 628217555651 Alamat Jl. Jend. Sudirman Jl. Diponegoro No.15, Salatiga, Kec. Sidorejo,...

ALAMAT BCA KCU PEKALONGAN Tlp:0817825533

By R4nt4u

Hub Via Wa:62817825533 Alamat Jl. Diponegoro No.27, Dukuh, Kec. Pekalongan Utara, Kota Pekalongan, Jawa...

Visit the forum

Question of the Day

Rebuilding All Indexes

I have added a few indexes to one of my tables in SQL Server 2025:

ALTER TABLE dbo.CustomerContact
ADD CONSTRAINT PK_CustomerContact
    PRIMARY KEY (CustomerID);

-- Create index on CustomerEmail
CREATE INDEX IX_CustomerContact_CustomerEmail
ON dbo.CustomerContact (CustomerEmail);
CREATE INDEX IX_CustomerContact_CustomerPhone
ON dbo.CustomerContact (phone);
I then do this to disable one index:
alter index IX_CustomerContact_CustomerPhone on dbo.CustomerContact disable
I see this when I check the index status:Index status for CustomerContactI decide to rebuild all indexes with this command:
ALTER INDEX ALL ON dbo.CustomerContact rebuild
After I do this, what will I see for the index status?

See possible answers