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.

SQLServerCentral Article

Who Needs Change Management?

You have spent thousands of dollars on that cool technology; clustering, redundant controllers, redundant disks, redundant power supplies, redundant NIC cards, multiple network drops, fancy tape backup devices and the latest and greatest tape technology. You are all set. There is no way your going to have downtime. Right?

SQLServerCentral Article

Another Disaster (Almost)

Andy had a semi-disaster similar to the one he wrote about last year. Interesting to see the kinds of problems that happen to other people. This article raises some interesting points that are outside the scope of basic disaster recovery, looking at how/when to move databases to a different server and how to reduce the server load dynamically.

SQLServerCentral Article

A Normalization Primer

For most DBAs, normalization is an understood concept, a bread and butter bit of knowledge. However, it is not at all unusual to review a database design by a development group for an OLTP (OnLine Transaction Processing) environment and find that the schema chosen is anything but properly normalized. This article by Brian Kelley will give you the core knowledge to data model.

SQLServerCentral Article

Case Study: Importing New Data Without Emptying Existing Tables

The challenge for Robert Marda was to devise a way to keep the data available at all times while importing the new data, detect if a full or daily update was received and run appropriate data pumps, put in sufficient fail safes to ensure bad data would not get imported, and to make the process automatic including notification to pagers upon failure. Robert shows you how he did it here.

Blogs

No Shortcuts for the SQLCMD Batch Terminator: #SQLNewBlogger

By

I was messing around with SQLCMD and I realized something I hadn’t known. I’ve...

Where Is My SQL Agent? Running Scheduled Jobs Against Azure SQL Database

By

One of the first things I review when I inherit a new SQL Server...

AgentDBA vs Critical SQL Server

By

It’s 07:43. Someone’s already left a message. “Something’s wrong with the DB server.” You...

Read the latest Blogs

Forums

ALAMAT BCA KCU HR MUHAMMAD TLP/WA 0817839777

By R4nt4u

Bantuan Cs 0817839777 Jl. Mayjen HR. Muhammad No.17, Putat Gede, Kec. Sukomanunggal, Surabaya, Jawa...

BCA KCU BUKIT DARMO BOULEVARD Tlp:0817839777

By layanan_Bca88

Telp / Wa 0817839777 Jl. Mayjend. Jonosewojo No.14, Pradahkalikendal, Kec. Dukuhpakis, Surabaya, Jawa Timur...

ALAMAT KANTOR BCA KCU SIDOARJO TLP/WA 0817839777

By m4rt1n4

Cs: 0817839777 Jl. Ahmad Yani No.39 A, Rw1, Sidokumpul, Kec. Sidoarjo, Kabupaten Sidoarjo, Jawa...

Visit the forum

Question of the Day

Detecting Characters

I have a SQL Server 2022 English default installation on a server. I want to detect if there are any upper case characters in rows and I have this code: 

SELECT CustomerNameID,
       CustomerName
 FROM dbo.CustomerName
 WHERE CustomerName = LOWER(CustomerName)
Here is the sample data I am testing with: 
CustomerNameID CustomerName
1              John Smith
2              Sarah Johnson
3              MICHAEL WILLIAMS
4              JENNIFER BROWN
5              david jones
6              emily davis
7              Robert Miller
8              LISA WILSON
9              christopher moore
10             Amanda Taylor
How many rows are returned?

See possible answers