File Watcher Task

The File Watcher Task does what it says really, it watches a folder waiting for files. When an available file is found the task completes, returning the name of the file for later use.

The task will detect changes to existing files as well as new files, both actions will cause the file to be found when available. A file is available when the task can open it exclusively. This is important for files that take a long time to be written, such as large files, or those that are just written slowly or delivered via a slow network link.

"TOP" Clause in SQL Server 2005

We all know the "TOP" clause returns the first n number of rows or percentage of rows thereby limiting the number of resulting rows displayed when we are selecting rows in a table.

SQL Server 2005 is packed with new features and enhancements. One of the enhancements in SQL 2005 that we are going to see is the clause, "TOP." The "TOP" clause will now allow us to do Data Manipulation and also allow similar criteria results to be displayed by using the TIES option.

A Call to Arms

Long anticipated, the arrival of radically restructured database architectures is now finally at hand.

Database Geek of the Week - Richard Hundhausen

Richard Hundhausen is the author of Building Web Applications with ADO.NET and XML Web Services and Programming ADO.NET, both from Wiley, as well as the upcoming Working with Microsoft Visual Studio 2005 Team System from Microsoft Press. He is also a trainer, teaching numerous courses and speaking at conferences such as VSLive and Tech Ed.

Asynchronous client script callbacks

There has been a lot of interest in the web-facing community lately about a new useability feature that goes by a number of different names—XMLHTTP, AJAX, out-of-band requests, and asynchronous client script callbacks, to name a few.

Regardless of the name, this feature provides a way for a standard web page to make calls back to the server, without a traditional page refresh. The user is oblivious to the fact that a server call has occurred, and is not interrupted by it.

MDX Essentials: String Functions: The .UniqueName Function

n this lesson, we will examine another function / property in the MDX toolset, the .UniqueName function. The general purpose of the .UniqueName function is to return the Unique Name of the object to which it is appended. .UniqueName can be used in conjunction with hierarchies, dimensions, levels, and members, in a manner similar to the .Name function that we examined in String Functions: The .Name Function, and, also like .Name, .UniqueName can be useful in a host of different applications.

Controlling Transactions and Locks in SQL 2000 and 2005 - Part 2

In order for a transaction to meet the requirements of ACID, locks are employed to insure data integrity and multi-user access. The scope, or number of rows held by a lock, is referred to as Lock Granularity. This month, we will begin by introducing several different types of lock modes employed by MS SQL.

Regular Expression Transformation

The regular expression transformation exposes the power of regular expression matching within the pipeline. One or more columns can be selected, and for each column an individual expression can be applied. If all columns selected pass their tests then rows are passed down the successful match output. Rows that fail to pass all tests are directed down the alternate output.

Software patents: stupid or insane?

Lest the headline mislead you as to my biases, I consider software patents to be both stupid and insane. I raise this issue because it is currently rearing its ugly mug in the world of open source software, but it has affected much development in the proprietary worlds of Windows as well.

First of all, patent laws were created long ago, which is not to say the thinking was correct then either, but we have to recognize the intellectual and technological climate back then.

Living the "Least Privilege" Lifestyle: Don't Run Every Day Logged In

Don Kiely contends that exercising administrative rights over our computers is a major cause of insecure systems. In the first of five articles, he explains the concept of "least privilege" and shows why software developers should be happy to operate as "mere users."