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.
Are you up for a quick game of who's the best DBA? A little humerous diversion on one of the big holidays in the US.
A view is a virtual table that consists of columns from one or more tables. Though it is similar to a table, it is stored in the database. It is a query stored as an object. Hence, a view is an object that derives its data from one or more tables. These tables are referred to as base or underlying tables.
SQL Server 2000 error handling isn't the most mature system for dealing with unexpected events. It has been much enhanced in SQL Server 2005, but many people will be using SQL Server 2000 for a long time. RAISERROR is one of those functions that can really aid in troubleshooting, but is often underutilized. David Poole brings us some hints on how this can help you out in your code.
The Checksum Transformation computes a hash value, the checksum, across one or more columns, returning the result in the Checksum output column. The transformation provides functionality similar to the T-SQL CHECKSUM function, but is encapsulated within SQL Server Integration Services, for use within the pipeline without code or a SQL Server connection.
DTS is a fantastic ETL tool and it is often used to import Excel documents. However this can be a manual process in many cases in setting up the package. New author Sloan Holliday brings us a way that you can leverage Office XP's automation facilities and XML to import data into SQL Server.
Usually developers like having full control over their reports but what happens if you have someone designated to build reports who does not quite know the backend schema. A good way to separate the building of the data for the report and the report design could be stored procedures. Now I consume stored procedures using Oracle which is not much different consuming stored procedures with SQL Server, however building the procedures is much different between the two. Even though I mention and show examples of stored procedures this is not an article for building them, just a guide for consuming a stored procedure within a Reporting Services Report.
SQL Server 2000 brought us DTS, a new way of working with data movement for SQL Server DBAs. However, unlike Integration Services and Project REAL, there weren't any great standards for working with this tool and building portable solutions was hard. Jonathan Stokes brings us a great article on how you can create a standard structure for your packages and make them more portable.
This is the forth article in the transaction and lock series. Up to now, the locks and hints discussed have applied to both SQL 2000 and SQL 20005. However, this article will introduce Snapshots, new in Microsoft SQL 2005.
By John
Recently, the world was reminded of just how fragile the internet can be. Two...
By Brian Kelley
In Parts 1-3, I covered how I prepare for a certification exam. In this...
By Steve Jones
I was chatting with the product managers at Flyway and one asked me whether...
I have a view where I am casting a datetimeoffset(7) field to smalldatetime or...
hi for the 2 years i've been here I believe we've had "encryption" turned...
Hi I have an overnight process that moves allot of claims records Been working...
In SQL Server 2025, what does this return?
DECLARE @player varchar(20) = 'Bo Nix', @num VARCHAR = '10' SELECT @player || @numSee possible answers