SQL Server 2005 provides some new command line utilities. One such utility is "sqlcmd". The sqlcmd utility is used to run adhoc queries interactively from a command prompt window, or can be used to execute a script containing T-SQL statements. The sqlcmd utility is a great improvement over osql and isql of older releases of SQL Server. In this article, I will explain some of the features this new command line utility brings to administering SQL Server.
Use the relational query engine in SQL Server 2005 to make a single query plan for the SQL and XQuery parts of your queries, and make the implementation of XML queries fast and easy to predict and tune.
A new product has just been released in Beta to help you with source control for your SQL Server development. Beta testers are wanted, so if you're interested, read on.
Continuing with his series, Andy Warren looks at what it means for SQL Server 2000 to run as a service and some of the options you have for starting, stopping, and restarting your server.
Most SQL Server 2000 DBAs have heard of Notification Services, but are they aware of how it works and what it's capabilities are? This is a great platform on which to build any type of messaging/notification/subscription application. New author and PASS board member Joe Webb brings us a look at this add on for SQL Server.
This paper describes the new CLR integration features of SQL Server 2005 and how database application developers and architects can take advantage of them to write user-defined procedures, functions, and triggers, as well as define new types and aggregates
The integration of SQL Server 2000 with version control is basically nonexistent. Managing and keeping track of your changes and files is a cumbersome task, and prone to have mistakes occur. There is a product that can help you with this called dbGhost and Jeremy Brown takes a look at this product and how it works.
Have you ever needed to audit your SQL Server 2000 database for changes to a table? A simple auditing solution is presented here by new author Tiago Silva using an INSTEAD OF trigger.
Are you looking to move your Oracle databases to SQL Server? You should be and when you convince your management to do so, Microsoft has a tool to help. New author Suresh Maganti of Scalability Experts brings us a look at how this works.
A deadlock is an inevitable situation in the RDBMS architecture and very common in high-volume OLTP environments. A deadlock situation is when at least two transactions are waiting for each other to complete. The Common Language Runtime (CLR) of .NET lets SQL Server 2005 provide developers with the latest way to deal with error handling. In case of a deadlock, the TRY/CATCH method is powerful enough to handle the exceptions encountered in your code irrespective of how deeply nested the application is in a stored procedure.
By Steve Jones
AI is a big deal in 2026, and at Redgate, we’re experimenting with how...
By Steve Jones
Another of our values: The facing page has this quote: “We admire people who...
By Ed Elliott
Running tSQLt unit tests is great from Visual Studio but my development workflow...
Comments posted to this topic are about the item No Defaults Passwords Ever
Hi, We have low latency high volume system. I have a table having 3...
Comments posted to this topic are about the item The Long Name
I run this code to create a table:
When I check the length, I get these results:
A table name is limited to 128 characters. How does this work?