Additional Articles


Technical Article

Review of AdventNet SwisSQL Sybase to SQL Server Migration Tool 2.1

Now it's time to review yet another migration related product from AdventNet. It is called "AdventNet SwisSQL Sybase to SQL Server Migration Tool 2.1". As the name suggests, this migration product automates the conversion of Sybase ASE (Adaptive Server Enterprise) T-SQL stored procedures, inbuilt functions, triggers, tables, views, and other database objects to Microsoft SQL Server T-SQL.

2005-11-04

1,103 reads

Technical Article

SQL Server 2000 SP3 and xp_cmdshell Woes

The problems caused by the SQL Sapphire Worm, also know as the SQL Slammer, have caused many sites to do a quick upgrade to SQL Server 2000 Service Pack 3 (SP3). It includes the fix that prevents infection by the worm. While moving to the latest service pack is usually a good thing, to do so without thorough testing risks breaking a working application. That is exactly what happened to one of my clients over the weekend.

2005-11-02

2,068 reads

Technical Article

Loving to Hate the Data Administrator

You can just hear it now: At the table down the hall, there’s a group of people having, (as it seems to you) yet another academic discussion on the merits of third-normal form and the structure of primary keys. You’ve heard many discussions like this before — it all seems so pointless. After all, doesn’t it just boil down to “create table” commands and a bunch of DDL? You mastered all that in your first DBA class. What could be so hard?

2005-10-31

3,688 reads

Technical Article

Accurate Numeric Identifiers: Using Verhoeff's Method for Check Digits

Check digits–not to be confused with checksums–are often added to numeric identifiers such as customer and product numbers to reduce the chance of incorrect entries. Sequences of numbers are notoriously easy to mistype, and constraints alone generally won't do the job. In this excellent article, Lynn Fields shows you how to implement the "Cadillac" of check digit methods–the Verhoeff Dihedral Group.

2005-10-26

2,735 reads

External Article

High Call Volume SQL Server Applications on NUMA Systems

One of the most difficult database operations to scale-up on high-end server systems is the network call. In fact, without special precautions, a high call volume database application can have severe negative scaling on large systems. It is suspected that this problem is more pronounced on NUMA systems than basic SMP systems. A NUMA system with 16 processors can have significantly lower throughput capability than an otherwise comparable 4-way SMP system.

2005-10-25

1,754 reads

Technical Article

VIEWS: The Key to Database Agility

There is an important technique for creating truly agile databases that I haven’t seen in his writings; one which is well-known to DBAs, but little understood in the application development community – the use of database views to create a layer of abstraction between the normalized relational tables and the applications that use the data.

2005-10-21

3,736 reads

Blogs

Building the Team: Roles and Responsibilities in FinOps

By

In my experience, FinOps success has never been just about tools or dashboards. It...

Tooling for Success: The Best FinOps Tools and Technologies

By

As a DevOps person, I know that to make FinOps successful, you need more...

From Planning to Practice: Setting Up Your FinOps Framework

By

As someone who works in DevOps, I’m always focused on creating systems that are...

Read the latest Blogs

Forums

Restoring On Top II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Restoring On Top II

SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)

By Terry Jago

Comments posted to this topic are about the item SQL Art 2: St Patrick’s...

Breaking Down Your Work

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Breaking Down Your Work

Visit the forum

Question of the Day

Restoring On Top II

I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:

-- run yesterday
CREATE DATABASE DNRTest2
GO
USE DNRTest2
GO
CREATE TABLE NewTable (id INT)
GO
Today, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today
USE Master
BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO
RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACE
What happens?

See possible answers