SQL Server

FindTextInDatabase - stored procedure to find text in SQL Server

Ram Shankar Yadav — Tue, 22 May 2007 15:22:49 GMT

 =========================================================================
 Author: Ram Shankar Yadav
 Create date: May 22, 2007
 Description: Used for  administrative purpose to find a particular text 
              in the database for example columnName,   Table name etc etc
 =========================================================================

CREATE PROCEDURE [dbo].[FindTextInDatabase]
    -- Add the parameters for the stored procedure here
@text varchar(200)

AS
BEGIN
    -- SET NOCOUNT ON added to prevent extra result sets from
    -- interfering with SELECT statements.
    SET NOCOUNT ON;
declare @newString varchar(205)
Set @newString = '%' + @text + '%'
    -- Insert statements for procedure here
    select name from sysobjects where id in 
(select id from syscomments where text like @newString)
order by name
END

Happy Coding

Microsoft SQL Server 2005 empty dialog box bug

Ram Shankar Yadav — Mon, 11 Dec 2006 09:58:00 GMT

I've no ideas what it is, but I'm sure that it's a bug ;)

Anybody have any clues on this .... @#$##$@#$@#

Happy Bugging

SQL Server 2005: ISNULL with DateTime

Ram Shankar Yadav — Mon, 04 Dec 2006 11:44:00 GMT

ISNULL is a convenient default setter for a string column usually to empty string ''.

With a DateTime column you have to pick a characteristic date like the following:

SELECT ISNULL(<ColumnName>, '1900-01-01') from <TableName>

Happy Coding

MSDN Wiki

Ram Shankar Yadav — Thu, 09 Nov 2006 04:03:00 GMT

MSDN Wiki

What is MSDN Wiki?

MSDN Wiki provides an infrastructure for users to comment, edit, and add content to the Visual Studio 2005 and .NET Framework 2.0 online documentation.

What Microsoft content is included on the MSDN Wiki beta site?

The site includes the English version of the Visual Studio 2005 and .NET Framework 2.0 documentation. In addition, it includes versions of these topics that are machine translated into Brazilian Portuguese.

How is this different from the content on msdn2.microsoft.com?

MSDN Wiki pulls its Microsoft content from the same database used by MSDN, so the Microsoft content you see on the MSDN Wiki site is the same as what is available on MSDN2. With the MSDN Wiki site we are experimenting with ways we can integrate community contributions into the Microsoft content.

Will other languages be included in the future?

Within the next year we plan to add MSDN Wiki functionality to the Japanese, French, German, Italian, Spanish, Korean, and Simplified and Traditional Chinese documentation.

Will content I add during the beta period be carried over to the RTW version of the site?

Yes!

MSDN Wiki Home

MSDN Wiki FAQ's

Happy Wiking

Choosing Between Transact-SQL and Managed Code

Ram Shankar Yadav — Fri, 13 Oct 2006 11:38:00 GMT

I got this from my friend Shally, and it really worth reading ...........

When you write stored procedures, triggers, and user-defined functions, one decision you will now have to make is whether to use traditional Transact-SQL or a programming language that is compatible with the .NET Framework, such as Visual Basic .NET or C#. The answer to this question will depend on the particular situation that is involved; in some situations you'll want to use Transact-SQL, while in other situations you will want to use managed code.

Transact-SQL is best for situations in which the code will primarily perform data access with little or no procedural logic. Programming languages that are compatible with the .NET Framework are best suited for computationally intensive functions and procedures that feature complex logic, or for situations in which you want to take advantage of the .NET Framework class library.

Code placement is also important. Both Transact-SQL and managed code run on the server. This places functionality and data close together, and allows you to take full advantage of a server's processing power. This is beneficial because it decreases traffic between the data and middle-tier. By simply performing the computation next to the data, a system that is I/O-bound may find this method significantly beneficial. CLR functions also can take advantage of the SQL Server query processor, which can parallelize and optimize execution. On the other hand, you may wish to avoid placing processor intensive tasks on your database server. Most client computers today are very powerful, and you may wish to take advantage of this processing power by placing as much code as possible on the client. There is no "one size fits all" answer.

Happy Coding

SQL Server 2005 (T-SQL) Exception handling using Try ... Catch

Ram Shankar Yadav — Thu, 12 Oct 2006 02:42:00 GMT

Hey guys now the days of tedious error handing are gone atleast with new SQL Server 2005. My colleague Sugandh sent this nice link to me which show how we can implement Try..... Catch in our Transact SQL code, or better to say in our database queries and stored procedures.

TRY...CATCH (Transact-SQL)

"Implements error handling for Transact-SQL that is similar to the exception handling in the Microsoft Visual C# and Microsoft Visual C++ languages. A group of Transact-SQL statements can be enclosed in a TRY block. If an error occurs in the TRY block, control is passed to another group of statements that is enclosed in a CATCH block."

Syntax

BEGIN TRY
     { sql_statement | statement_block }
END TRY
BEGIN CATCH
     { sql_statement | statement_block }
END CATCH
[ ; ]

Arguments

sql_statement: Is any Transact-SQL statement.

statement_block: Any group of Transact-SQL statements in a batch or enclosed in a BEGIN…END block.

Examples

A. Using TRY…CATCH

The following example shows a SELECT statement that will generate a divide-by-zero error. The error causes execution to jump to the associated CATCH block.

USE AdventureWorks;
GO

BEGIN TRY
    -- Generate a divide-by-zero error.
    SELECT 1/0;
END TRY
BEGIN CATCH
    SELECT
        ERROR_NUMBER() AS ErrorNumber,
        ERROR_SEVERITY() AS ErrorSeverity,
        ERROR_STATE() AS ErrorState,
        ERROR_PROCEDURE() AS ErrorProcedure,
        ERROR_LINE() AS ErrorLine,
        ERROR_MESSAGE() AS ErrorMessage;
END CATCH;
GO

Links:

TRY...CATCH (Transact-SQL)

Using TRY...CATCH in Transact-SQL

No more @@ERROR required.........

Happy Coding

ADO.NET 2.0 Bulk Copy Option

Ram Shankar Yadav — Thu, 09 Mar 2006 08:26:00 GMT

A friend of mine today asked me "Can we Insert more than one row in the database without iterating for each row ?". Indeed the question asked by her is really a good one ! So I tried to find out the solution, I have heard that ADO.NET 2.0 Bulk Copy Option can copy bulk of data from one datasource to another with less round trips, but I was not sure that this option will work with my friends' problem.

So I googled and got a very good article by Mahesh Chand on C# Corner. The article is simple, precise and very comprehensible.

Link:

http://www.c-sharpcorner.com/Code/2004/June/BulkCopy.asp

I hope this might be helpful to you.

Problem while inserting X.00 in a float column in SQL Server

Ram Shankar Yadav — Wed, 25 Jan 2006 02:10:00 GMT

I recently faced this problem, when I tried to enter a value 2.00 in a float column in SQL Server 2000. I repeatedly tried to insert this value but I failed every time, then I tried with some work arounds by casting that value to numeric/decimal. It worked but......., there's still one thing that was missing was that when we tried with the following SQL statement:

Select Cast(fieldname as numeric(9,2)) From tablename

Although we got the desired result in that column but column name was missing this time so we tried this:

Select Cast(fieldname as numeric(9,2)) alias From tablename
or
Select Cast(fieldname as numeric(9,2)) as alias From tablename

Yo ho ! It finally worked !