Is Windows 2003 really faster for a SQL Server/IIS environment? Let us do all the leg work for you! We are about to upgrade the SQLServerCentral.com web and SQL Server from Windows 2000 to Windows 2003. As part of the case study, we are going to capture a baseline of the server's overall performance before the upgrade and then again after the upgrade. We will then document the experience and benchmark numbers.
2003-06-10
12,894 reads
Have you ever had the problem where a user ran a query against your SQL Serer and crashed it or made the server unusable since the CPU was spiked at 100%? A SQL Server black box is the equivalent of a flight data record. The black box records all queries being passed to your SQL Server and other useful information like errors.
2003-04-11
16,955 reads
Join SQLServerCentral.com co-founder Brian Knight for this free webcast on SQL Server security best practices. In this session on Technet, we will look at how to protect your system from internal and external security factors. We will look at the types of permissions in your database objects, implementing column and row-level security, and protecting yourself from SQL Injection attacks. We'll also cover best practices for basic and advanced protection for your SQL Server system.
2003-04-02
1,994 reads
Brian Knight recently had the basic need to retrieve a record from the database at random. What seemed to be an easy task quickly became a complex one. This case showed an interesting quirk with T-SQL that was resolved in an equally quirky way. This quick article shows you a method to retrieve random data or randomize the display of data.
2003-03-26
9,456 reads
Last week the SQL Sapphire (or SQL Slammer) virus hit corporate networks throughout the Internet. Although damage has not been estimated yet, it is sure to be in the tens of millions of dollars. So who is to blame when a virus like this manhandles a corporate environment?
2003-02-03
5,886 reads
On Friday the 24th, a virus that preys on a SQL Server vulnerability began to attack networks, taking down many networks. This brief network describes the virus and how to protect yourself from it.
2003-01-27
10,845 reads
Recently, the SQLServerCentral.com labs had the chance to get a sneak peak at Lumigents latest creation, Entegra, which is scheduled to ship in the second week in December. Entegra monitors database activity and provides a complete record of access to the data and changes to database structure and permissions.
2002-11-13
3,316 reads
If you're still on SQL Server 2000 SP2, beware! Microsoft has released a number of fixes that have now been rolled up into this cumulative patch to fix major security flaws in SQL Server.
2002-10-07
4,647 reads
Oops, a developer just forgot a WHERE clause when he ran his delete statement. Lumigent Log Explorer 3.0 can peer into the transaction log and find the culprit and roll it back. Read the review here of Lumigent's latest version.
2002-07-23
4,034 reads
Brian Knight recently had the opportunity to look at a very unique product in the industry. MYdbPAL automates many of the tasks that database professionals perform on a day-to-day basis. Read his review here.
2002-07-16
4,356 reads
By Steve Jones
I caught this interesting item over on Pinal Dave’s blog: Eleven Interview Questions that...
By Hemantgiri
I use color-coded connections in SSMS to distinguish Production, Pre-Production, UAT, and Development. But...
Comments posted to this topic are about the item Split Large Queries in Athena...
Comments posted to this topic are about the item Finding Trailing Spaces
I have some data in a SQL Server 2025 database. It looks like this for the dbo.Customer table:
CustomerID CustomerName PreferredName 1 Steve Steve 2 Andy Andy 3 Brian Brian 4 Allan Allan 5 Devin Devin 6 Steve Steve 7 Sally SallyI want to detect which names have a single trailing space. The CustomerName is a varchar() and the PreferredName is a CHAR(). Does this query detect the problem rows?
SELECT
CustomerID,
CustomerName,
PreferredName
FROM Customer
WHERE CustomerName <> RTRIM(CustomerName)
OR PreferredName <> RTRIM(PreferredName); See possible answers