Kimberly L. Tripp talks about indexing best practices and what developers should know about SQL Server management. She also discusses stored procedure and parameterized queries caching, the new availability features in SQL Server 2005, and the SQL Server CLR.
2005-07-06
2,440 reads
In the beginning, there was the recordset, a central feature of classic ADO. Like a Swiss army knife, it wasn’t the perfect tool for every job, but given the correct configuration, it could do whatever you needed it to do.
The recordset wasn’t always pretty to watch, however, and it came into prominence at a time when client/server applications for which it was optimized were being replaced by web applications. Its dark side included an amazing level of complexity and the number of special cases when it was used with particular providers.
2005-07-05
4,419 reads
Bob Beauchemin is a developer who not only writes code and develops databases, but also teaches other developers to create applications and databases, often using the latest Microsoft technologies.
Bob has more than 25 years of experience working with IBM mainframes and Unix boxes, as well as Windows-based PCs. He has taught a number of database courses for DevelopMentor, a hands-on training company for experienced developers, and has given instruction on writing .NET web services and creating applications and components using C#.
2005-07-04
2,069 reads
You can monitor the system performance by using the Performance monitor console and its related counters in Windows 2000. These counters allow you to view or save information about the overall performance of your server. When you install Microsoft SQL Server, additional Performance monitor objects and counters are automatically installed. While you must have administrative access to your SQL Server to use these objects, SQL Server admins should find them invaluable in monitoring and tuning the database server. Furthermore, the Performance monitor can be used either locally or remotely, which allows admins greater control in monitoring SQL Server.
2005-07-01
3,715 reads
In Part 1 I covered a simple stored procedure that printed the current date. In this article I'll cover writing a stored procedure to return a recordset back to the client. In the process we'll learn a little bit more about .NET and C# including the SqlConnection, SqlCommand and SqlDataReader classes.
2005-06-29
3,601 reads
See an example of using the Many-to-Many dimension in SQL Server 2005 Analysis Services to analyze sales data, and get ideas for other uses such as treating medical conditions, software testing, and more.
2005-06-28
2,289 reads
Getting started with SQL Server 2005 Reporting Services or the new report controls in Visual Studio 2005? Brian Welcker demonstrates some tips and tricks that you can use to add interactive features to your own reports.
2005-06-27
2,173 reads
An important consideration, when designing a Business Intelligence system within any environment, is a consideration for "where to put the intelligence" among the various "layers" within the system. I have stated many times in the past, in both articles and presentations, that "multi-layered reporting solutions require multi-layered architects," and nowhere is this truer than within the design and implementation of the Microsoft integrated business intelligence solution. This article provides an excellent example of such considerations: the option for placing a needed calculation at either the Analysis Services level (within the cube structure) or the Reporting Services level.
2005-06-24
2,539 reads
This white paper provides an introduction to various features of XQuery implemented in SQL Server 2005 such as the FLWOR statement, operators in XQuery, if-then-else construct, XML constructors, built-in XQuery functions, type casting operators, and examples of how to use each of these features. Non-supported features of XQuery in SQL Server 2005 and workarounds are described in this article. It also presents three scenarios where XQuery is useful.
2005-06-23
2,686 reads
Shredding a recordset in this instance means that we are going to show you how to take a recordset produced in your SSIS package, loop over the rows in that recordset, break apart the columns and do something with them. This is really useful when you want to preform an action on a row of data for every row of data just like we are going to do here. Sure we could use an ExecuteSQL task to get the recordset as well but that does limit our choices of source data whereas doing it in the pipeline does not. Something useful we hope.
2005-06-21
2,103 reads
By alevyinroc
Ten years (and a couple jobs) ago, I wrote about naming default constraints to...
By Steve Jones
We have multiple teams (8) working on Redgate Monitor. Some work on the Standard...
By HeyMo0sh
Learning any kind of theory is easy, but adapting FinOps and watching it rescue...
Comments posted to this topic are about the item The day-to-day pressures of a...
Comments posted to this topic are about the item The Problem Isn't Always Your...
Comments posted to this topic are about the item Identity Defaults
What happens when I run this code?
CREATE TABLE dbo.IdentityTest
(
id int IDENTITY(10) PRIMARY KEY,
somevalue VARCHAR(20)
)
GO
See possible answers