Articles

SQLServerCentral Article

Freeware: Terminator Opens Gigabyte Files Easily

Ever tried to open 1 Gig ASCII file with Notepad? WordPad? Do you remember ASCII codes of Tab and Carriage Return? Enter Terminator; huge ASCII file viewer and BCP helper. Terminator reads top 10 (and more if asked) records of ASCII file of any size. It detects record terminators and calculates current cursor position (field offset) and length of selected area (field length). Best of all, it's free!

You rated this post out of 5. Change rating

2003-01-29

109 reads

Technical Article

How to move SQL Server from one computer to another?

Moving SQL Server from one computer to another is not a very difficult thing to do, but it often stumps newbie DBAs. Of course, it needs careful planning to ensure that the SQL Server is moved completely and properly to the new machine, and with a minimal downtime and no data loss. This article introduces you to a couple of methods you can employ to move/migrate SQL Server from one computer to another.

2003-01-24

107 reads

SQLServerCentral Article

Worst Practice - Bad Comments

This one is pretty interesting, Andy discusses a few things he sees in comments that not only fail to add value, they end up costing extra time. There's room for discussion here, but definitely a discussion worth having - comments can make you or break you, here's a chance to think about what you think is important in commenting and pass that on to your development team.

4 (2)

You rated this post out of 5. Change rating

2003-01-23

10,789 reads

SQLServerCentral Article

How to Search for Date and Time Values

Because of the way date and time values are stored in SQL Server, searching for a particular date or time is not as straightforward as you might think it would be. This article describes how date/time values are stored, how the database design can simplify (or complicate) data retrieval, and how to query date/time data to get the right results every time.

5 (1)

You rated this post out of 5. Change rating

2003-01-21

35,051 reads

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

Blogs

Unlock the Power of Your Data: From Basic to Advanced Data Analysis

By

Data isn't just about numbers and spreadsheets. It holds stories, patterns, and the answers...

Attacking the Weakest Link

By

When I look at a system and think about its security model, the first...

Webinar – Microsoft Fabric for Dummies

By

On Wednesday May 15th 2024 I will give a free webinar on MSSQLTips.com about...

Read the latest Blogs

Forums

What is Carisol 350mg ?

By fafawec116

Carisol 350mg is the main ingredient. Its powerful formulation, which includes the active ingredient...

The "ORDER BY" clause behavior

By Alessandro Mortola

Comments posted to this topic are about the item The "ORDER BY" clause behavior

Are IT Certifications Still Relevant?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Are IT Certifications Still Relevant?

Visit the forum

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