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.
The CLR in SQL Server 2005 is quite the topic of debate and whether it is a good thing or not. No matter which side you are on, the reality is that you will need to understand how to create, manage, and work with stored procedures based on assemblies in SQL Server 2005. New author Yelena Varshal brings us a basic article and a sample that you can use.
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.
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.
This is the second of a two part series on how triggers work in the two latest versions of MS SQL Server. The first part dealt with what is common between the two versions. This article will detail what's been added to SQL Server 2000.
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.
One of the most popular questions on SQL Server 2000 deals with determining how much space the various tables in your database take up. There are a variety of reasons for this and a few ways to gather the information. Author Amit Lohia takes a look at how sp_spaceused works and how you might customize it to suit your needs.
We've just sent the July issue of the SQL Server Standard to the printer and it should be shipping out to you subscribers next week. The e-version should be in your virtual briefcase and it should be at the PASS and MCP sites soon. Read the editorial and see what's in this issue.
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.
Storage is getting cheaper and cheaper, which means that more and more SQL Server servers will be incorporating SAN storage as an architecture moving forward. It seems that most DBAs, however, have never worked with this technology. New author Hugh Scott brings us a primer on this Storage Area Networks for DBAs new to this technology.
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
WA:08218154393 Jl. Matraman Raya No.14-16, RT.2/RW.1, Kb. Manggis, Kec. Matraman, Kota Jakarta Timur, Daerah...
WA:08218154393 Jl. HOS Cokro Aminoto No.56-58, Muka, Kec. Cianjur, Kabupaten Cianjur, Jawa Barat 43215
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers