SQLServer

SQL Server Extended Procedure- usage of Built-in

Raju — Thu, 09 Sep 2004 20:41:00 GMT

http://www.devarticles.com/c/a/SQL-Server/Extended-Stored-Procedures-Intro-And-10-Cool-Examples/

Authors gives good brief on 10 cool features in SQL Server repository.

xp_fileexist filename [, OUTPUT]
exec master..xp_fileexist 'c:\test.file'

xp_regread root_key, path_key, key_value
master..xp_regread 'HKEY_LOCAL_MACHINE', 'SYSTEM\Setup', 'SystemPartition'

exec master..xp_repl_encrypt @cardNumber1 output

exec master..xp_dirtree 'c:\mydir'

set @xml = ''
exec sp_xml_preparedocument @id output, @xml
select * from OpenXML(@id, '/people/person')

exec master..xp_availablemedia

declare @netname varchar(20)
exec master..xp_getnetname @netname output
print 'The name of my SQL Server is ' + @netname

xp_logevent {error_number, 'message'} [, 'severity']

exec master..xp_terminate_process 3812

exec master..xp_cmdshell @command

echo off
@echo You passed in %1
Now, enter the following code into Query Analyzer and run it:
declare @arg1 varchar(20)
declare @command varchar(50)
set @arg1 = 'Hello'
set @command = 'c:\testbat.bat ' + @arg1
exec master..xp_cmdshell @command

SQL Server Extended Procedure- usage of Built-in

Raju — Thu, 09 Sep 2004 20:40:00 GMT

http://www.devarticles.com/c/a/SQL-Server/Extended-Stored-Procedures-Intro-And-10-Cool-Examples/

Authors gives good brief on 10 cool features in SQL Server repository.

xp_fileexist filename [, <file_exists INT> OUTPUT]
exec master..xp_fileexist 'c:\test.file'

xp_regread root_key, path_key, key_value
master..xp_regread 'HKEY_LOCAL_MACHINE', 'SYSTEM\Setup', 'SystemPartition'

exec master..xp_repl_encrypt @cardNumber1 output

exec master..xp_dirtree 'c:\mydir'

set @xml = '<people><person name="John Doe" age="30"/></people>'
exec sp_xml_preparedocument @id output, @xml
select * from OpenXML(@id, '/people/person')

exec master..xp_availablemedia

A Survey of Microsoft SQL Server 2000 XML Features

Raju — Tue, 23 Mar 2004 19:24:00 GMT

A Survey of Microsoft SQL Server 2000 XML Features from Andrew Conrad

This describes latest features on XML with SQL Server with abstract example - Worth of reading

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnexxml/html/xml03172004.asp

Tips for Trigger and Link for Data Recovery article

Raju — Wed, 19 Nov 2003 18:33:00 GMT

http://www.lumigent.com/go/ud14

Find Data-Recovery and Best Practices white paper from
By Stephen Wynkoop, Microsoft SQL Server MVP
(Founder The SQL Server Worldwide User’s Group)

Tips on Triggers

Encrypting Trigger Definitions
If you want to ensure that other users cannot view the trigger definition, you can use the WITH ENCRYPTION clause. The trigger definition is then stored in an unreadable form.Once encrypted, the definition of the trigger cannot be decrypted and cannot be viewed by anyone, including the owner of the trigger or the system administrator.

-----------------------------------------------------------------------------

Use the INSTEAD OF trigger to replace the standard triggering action
CREATE TRIGGER TableAInsertTrig ON TableA
INSTEAD OF INSERT
AS ...

Use the AFTER trigger to augment the standard triggering action
CREATE TRIGGER TableBDeleteTrig ON TableB
AFTER DELETE
AS ...

Use the FOR trigger to augment the standard triggering action
-- This statement uses the FOR keyword to generate an AFTER trigger.
CREATE TRIGGER TableCUpdateTrig ON TableC
FOR UPDATE
AS ...
-------------------------------------------------------------------------------

Recursive trigger could be turned off and also nested trigger could be turned off.

Overview of 64Bit SQL from Ram Kishore

Raju — Fri, 31 Oct 2003 14:12:00 GMT

Great article on Overview of 64bit SQL by Ram Kishore (ramki120@hotmail.com)

http://www.sqlservercentral.com/columnists/rkishore/overviewof64bitsql.asp

The Publisher says "This is a great article, seems like it covers almost every question you might have about installing and using the 64 bit version of SQL2K"

Pretty work Ram Kishore :)

Queries to check SP,table,trigger exists in database or not

Raju — Thu, 30 Oct 2003 14:32:00 GMT

Simple quries to check whether they are existing in database or not.

1. Checking whether procedure exist in the NORTHWIND database with name 'CustOrdersDetail'

Approach -1:

use NORTHWIND

if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[CustOrdersDetail]') and OBJECTPROPERTY(id, N'IsProcedure') = 1)

print 'CustOrdersDetail Exists in the NORTHWIND database'

else

print 'CustOrdersDetail *does not exist* in the NORTHWIND database'

Approach -2:

Use NORTHWIND

if exists(select * from dbo.sysobjects where type = 'p' and name = 'CustOrdersDetail’ )

print ''CustOrdersDetail Exists in the NORTHWIND database'

else

print ''CustOrdersDetail *DOES not exist* in the NORTHWIND database'

2. Checking whether table exist in the database with name 'EmployeeTerritories'

Approach -1:

use NORTHWIND

if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[EmployeeTerritories]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)

print 'EmployeeTerritories Exists in the NORTHWIND database'

else

print 'EmployeeTerritories *DOES not exist* in the NORTHWIND database'

Approach -2:

use NORTHWIND

if exists(select * from dbo.sysobjects where type = 'U' and name = 'EmployeeTerritories' )

print 'EmployeeTerritories Exists in the NORTHWIND database'

else

print 'EmployeeTerritories *DOES not exist* in the NORTHWIND database'

3. Checking whether trigger exist in the database with name 'TempTrigger'

Approach -1:

use Northwind

if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[TempTrigger]') and OBJECTPROPERTY(id, N'IsTrigger') = 1)

print 'TempTrigger Exists in the NORTHWIND database'

else

print 'TempTrigger *DOES not exist* in the NORTHWIND database'

Approach -2:

use Northwind

if exists (select * from dbo.sysobjects where name ='TempTrigger' and type ='TR')

print 'TempTrigger Exists in the NORTHWIND database'

else

print 'TempTrigger *DOES not exist* in the NORTHWIND database'

SQL Server's Coolest Features

Raju — Thu, 23 Oct 2003 15:48:00 GMT

SQL Server 2000's Coolest Features

Just when you think you have a handle on SQL Server 7.0, Microsoft ships a new SQL Server release. SQL Server 2000 might skip 1,993 release numbers, but you won't find the same degree of difference between SQL Server 2000 and 7.0 as you found between SQL Server 7.0 and 6.5. Even so, this latest release is full of new functionality. Here are seven of my favorite new SQL Server 2000 features.

7. Integrated XML Support
XML support is key to Microsoft's push to Web-enable SQL Server 2000. The new release supports T-SQL extensions that let SQL Server produce a result set as an XML document. In addition, you can use XML documents to directly insert and update SQL Server tables.

6. INSTEAD OF Triggers
SQL Server 2000's new INSTEAD OF triggers aren't exactly like BEFORE triggers, but you can use them in a similar way. Unlike AFTER triggers, which the system executes after a transaction changes the database, INSTEAD OF triggers execute instead of the triggering action.

5. Table Data Type
The new table data type lets an application store temporary results as a table that you can manipulate by using a select statement or even action queries—just as you can manipulate any standard user table.

4. User-Defined Functions
User-defined functions enhance T-SQL's programmability by letting you create and use your own functions in T-SQL stored procedures and batches. SQL Server 2000 executes user-defined functions in the same way that it executes T-SQL's built-in functions, and user-defined functions can return either scalar variables or table data types.

3. Indexed Views
Unlike standard views, in which SQL Server resolves the data-access path dynamically at execution time, the new indexed views feature lets you store views in the database just as you store tables. Indexed views, which are persistent, can significantly improve application performance by eliminating the work that the query processor must perform to resolve the views.

2. Federated Database Support
Federated database support, which lets you use SQL Server 2000's distributed partitioned views to horizontally partition tables across multiple servers, enabled SQL Server 2000 to set its new Transaction Processing Performance Council (TPC) TPC-C benchmark of 262,243 transactions per minute (tpmC) with 12 clustered Compaq systems.

1. Cascading DRI
Cascading Declarative Referential Integrity (DRI) might not be SQL Server's sexiest new feature, but it's the feature you'll most likely use. With cascading DRI, you specify a relationship between a parent and a dependent table so that a deletion or update of a row in the parent table automatically cascades to corresponding rows in the dependent table.

Removing Duplicates

Raju — Thu, 23 Oct 2003 15:47:00 GMT

Simple way to Remove Duplicate Rows from an Existing Table in SQL

SELECT DISTINCT *
INTO duplicate_table
FROM original_table
GROUP BY key_value
HAVING COUNT(key_value) > 1

DELETE original_table
WHERE key_value
IN (SELECT key_value
FROM duplicate_table)

INSERT original_table
SELECT *
FROM duplicate_table

DROP TABLE duplicate_table