 |
|
^ click above ^ |
05.11.04
Microsoft
Adds ActiveViews to Free SQL Reporting Services Add-On
Microsoft gave users another reason to download its free SQL Server
Reporting Services add-on when it acquired small, privately held
ActiveViews.
Actually, "small" in this context is something of a misnomer: With
five employees, ActiveViews is downright tiny. Nevertheless, it
does offer a Web-based report authoring and end-user query tool
based on Microsoft’s .NET framework—and designed to exploit SQL
Server 2000 Reporting Services.
Read
The Whole Article
Too
Many Indexes with SQL Server? Also, troubleshooting performance
monitor...
Today's web seminar on SQL Server performance was interesting in
many regards. Perhaps one of the most intriguing and telling parts
was a quick poll we took during the presentation. In it, we asked
what people did to tune their SQL Servers. The vast array of answers
centered around "I use profiler when I see a problem" and "performance
tuning?" While I think the second answer may be in jest, I believe
the first indicates just how lost we all get when it comes time
to determine where a problem is performance-wise in SQL Server.
The first thing people do is look to the indexes. You fire up Profiler,
let it read through your database while things are happening, then
you use the Index Tuning Wizard to suggest new indexes for your
tables. All is good to here, but what most people don't realize
is that, without some precautions, the Tuning Wizard can actually
become detrimental to the performance of your system. There are
a couple of things you need to keep in mind:
Read
The Whole Article |
OLE
DB (Microsoft SQL Server) Part 2 - DataWindows and OLE DB
Part 1 of this article (PBDJ, Vol. 11, issue 3) defined an OLE DB,
discussed the OLE DB interfaces provided with PowerBuilder, and
connecting to and accessing MS SQL Server. In Part 2 I'll discuss
DataWindows and BLOBs, and answer some frequently asked questions
about PowerBuilder and OLE DB.
DataWindows and OLE DB
The primary means of interaction with a database is through DataWindows,
which should be used whenever possible. The DataWindow provides
significant features, such as easy result set handling, lots of
formatting options, and automatic generation of update statements.
Read
The Whole Article
| Easily
create structured documents and syndicate information to multiple
Web sites and device >>try
CMS300 V4 today |
Understanding
Error Handling
This is an interesting to talk. I've not been a big supporter of
what happens in our error handling in SQL. And there are quite a
lot of void spaces that needs to be addressed in the SQL documentation
for the same. Here are some of the tips you can use in your application
code. I know this is not an exhaustive analyssis of Error Handling
in SQL. But here I do have something learn't the hard way.
Syntax
A typical syntax will look like :
RAISERROR ( { msg_id | msg_str } { , severity, state }
[ , argument [ ,...n ] ] )
[ WITH option [ ,...n ] ]
I would spend rest of my article on the red areas from the above
syntax. I would also illustrate using some common examples I've
faced.
Read
The Whole Article
Building
Wiki Web Sites with ASP.NET and SQL Server
This article describes some of the advantages that Wiki Web sites
provide and how you can use ASP.NET and SQL Server to create your
own Wiki. You'll learn how to write powerful parsers using the .NET
regular expressions class and you'll discover how to add sophisticated
search functionality to your Web sites by using SQL Server's Full-Text
Search service.
Imagine you visit a Web site that offers information about .NET.
You start reading one of the pages about the String class and then
realize that the syntax of one of the methods is incorrect. You
click the Edit button, update the syntax of the method, update the
example that describes how to use the method, and save your changes
so that future readers benefit from your contribution. You've just
used a Wiki Web site.
Read
The Whole Article
| Get
POWERFUL one-way links without participating in a link exchange
program learn
More |
What
is the difference between SET and SELECT when assigning values to
variables, in T-SQL?
Traditionally, SQL Server database developers are accustomed to
using SELECT for assigning values to variables. This was fine and
a perfectly valid practice right until SQL Server 6.5. Microsoft
released SQL Server 7.0 in 1999. SQL Server 7.0 introduced the new
SET statement for initializing and assigning values to variables.
SQL Server 7.0 Books Online also stated: "It is recommended that
SET @local_variable be used for variable assignment rather than
SELECT @local_variable."
This caused some confusion in the database developer community,
as Microsoft never mentioned, why SET is recommended over SELECT
for assigning values to variables. In this article, I will highlight
all the major differences between SET and SELECT, and things you
should be aware of, when using either SET or SELECT.
Read
The Whole Article
Read this newsletter at:
http://www.sqlpronews.com/2004/0511.html |
|
|
|
