SQL Server was designed to make the DBA job easier, distribution of security, automated procedures, etc. But in some areas it either does not go far enough, or a feature is used for an unintended purpose. One of those areas comes into play when allowing many people to create databases. Author Eli Leiba brings us a tecehnique he uses to close the gap and track down those newly created databases.
One of the new tasks in SQL Server 2005 is the For Loop Container. In this article we will demonstrate a few simple examples of how this works. Firstly it is worth mentioning that the For Loop Container follows the same logic as most other loop mechanism you may have come across, in that it will continue to iterate whilst the loop test (EvalExpression) is true. There is a known issue with the EvalExpression description in the task UI being wrong at present. (SQL Server 2005 Beta 2).
SQL Server Analysis Services includes the ability to capture information about every query run against a cube. Author Ramunas Balukonis showed us last time how to query this data. This time he brings us a method of interperting which dimensions are actually be used in satifying Analysis Services queries.
SQL Server 2005 has made it a lot easier for us to loop over a collection and with each iteration do something with the item retrieved. In this article we are going to show you how to iterate over a folder looking at the files within and doing something with those files. In this instance we will be entering the filename into a SQL Server table and we will then load the actual files we have just found into another SQL Server table. You will note here that there is still the need to load the file names into a table as an intermediate step just as we need to do in SQL Server 2000.
Red Gate Software, a leading supplier or SQL Server and .NET tools has updated the classic "A Christmas Carol" to show the importance of stress testing.
SQL Server 7 revamped Enterprise Manager to be an MMC snap in with many more capabilities and functions than it had in SQL Server 6.5. Dale Elizabeth Corey brings us a look at the top ten features in Enterprise Manager that you may not be aware of.
SQL Server 2005 gives us loads of flexibility in our workflow management to decide how and if the following task should be executed. In this article we are going to introduce you to one of those ways and that is putting an expression into the workflow constraint itself.
The heart of an RDBMS is the transaction system that it employs. SQL Server has a great one that can easily be misunderstood or misused by those that haven't spent time delving into the details of how it works. Don Peterson has done that and brings us the start of a new series on the details of how transactions work in SQL Server.
In this article we are going to assume a few things about the reader as we want to concentrate as much as possible on the Script Component itself and not the peripheral stuff
The things we will assume are:
* You are happy with adding a DataFlow task to the designer in Workflow
* You are happy to configure an OLEDB Source adapter
* You are comfortable with configuring mappings in the Destination adapter
To do some of the stuff we wanted in SQL Server 2000 DTS we had put together some serious glue code and to be honest it wasn't pretty. One of the things that we used to have to do this way was if we wanted to implement using workflow constraints a Logical OR. Well that has changed and it is now really simple and this article is going to show you how to implement it.
By gbargsley
Recently, I was in a technical interview where the topic of running PowerShell at...
By alevyinroc
I don’t recall where this came up (probably in SQLSlack), but I had a...
By Steve Jones
One of the parts of getting older that really sucks is I seem to...
Comments posted to this topic are about the item SQL Server, Heaps and Fragmentation
Comments posted to this topic are about the item Stairway to Azure SQL Hyperscale...
Comments posted to this topic are about the item Pushing the Limits of AGs
A table without a clustered index (heap) will NOT suffer from fragmentation during frequent updates or deletes. True or False?
See possible answers