Getting the Most out of SQL Server 2000's Query Analyzer, Part I
So you open up the tool a hundred times a day. In this article by Brian Kelley, he shows you how to get the most out of some of the known and unknown features.
So you open up the tool a hundred times a day. In this article by Brian Kelley, he shows you how to get the most out of some of the known and unknown features.
There is nothing spectacular about using indexes per say. However, on many occasions I have come across a variety of SQL coders that never consider validating that the index they think they are using is efficient or even being used at all. We can all put indexes on the columns that we think will be required to satisfy individual queries, but how do we know if they will ever be used. You see, if the underlying table data is constructed, contains, or is ordered in a particular way, our indexes may never be used. One of the factors around the use of an index is its clustering factor and this is what this article is about.
This article is a member of the series Introduction to MSSQL Server 2000 Analysis Services. The series is designed to provide hands-on application of the fundamentals of MS SQL Server 2000 Analysis Services, with each installment progressively adding features and techniques designed to meet specific real - world needs.
Every once in awhile there is a unique T-SQL solution in SQL Server that solves a rare problem. Not many of us have had to deal with boolean evaluation in our jobs, but a few have. Author Eli Leiba has and brings us a new article that shows how to build a procedure that can take a boolean expression and evaluate it to true or false.
This series of articles will examine the purposes, uses, and optimization of cursors in SQL 2000. SQL languages are designed so groups of records, or sets, can be manipulated easily and quickly. The speed at which groups of data can be altered, updated and deleted, demonstrates why working with sets is the preferred method. However, there are places where cursors are a better choice.
The next version of SQL Server due in 2005 will bring about many changes in how it works, with .NET, the CLR integration, Integration Services, and much more. Many of us are looking to get a jump on the product and see where these changes might affect our scripts and environments. Jon Reade has started the work in decoding the new DBCC commands, which ones work and which don't. Since there's a limited amount of documentation for the Beta product, read about his detective work and send him off an
SQLServerCentral.com is all about learning. Our goal has been to build a community where we all teach each other how to become more proficient with SQL Server. Most of our content to date has been written articles that show you how to do something. Well we have a a better idea, maybe. Check out our new video HOWTO series.
A common complaint of database administrators (DBAs) is that performance bottlenecks are not among those problems that one can fix "by just throwing hardware at it." Thus, database servers must provide tools and techniques to help administrators address this issue. On that aspect, SQL Server 2005 does not disappoint.
SQL Server has this concept of an owner of an object. Similar to the concept of schema, but not quite the same. Best practice dictates that all objects in SQL Server be owned by dbo, but that does not always happen. Tracking those objects down might be a pain, but Santveer Singh brings us an easy way of doing this.
By Steve Jones
I ran across this article recently (https://www.gatesnotes.com/meet-bill/source-code/reader/microsoft-original-source-code) and it has a great opening piece...
By Steve Jones
I’m in the UK today, having arrived this morning in London. Hopefully, by this...
I’m not trying to start up a debate whether you should use tabs or...
I have a script task that tries to execute a HTTP request, which seems...
Comments posted to this topic are about the item SQL Server 2025 Standard Developer...
Comments posted to this topic are about the item URL Safe or Not?
If I use BASE4_ENCODE() in SQL Server 2025, is the output URL Safe by default?
See possible answers