Prithi

  • Interests: SQL Server, Christian Faith, Sri Lankan Politics, Tamil Literature

Technical Article

Trigger Generator for data audit

This Procedure generates 3 triggers (for Insert, Update & delete). The purpose of these triggers is to keep a SIMPLE audit trail. Create the table and the procedure in the database to which you want to have the auditing facility. To include a table for auditing run the procedure with Table Name as the parameter.

You rated this post out of 5. Change rating

2002-10-09

1,193 reads

Technical Article

Compare the data of 2 Tables (Updated)

The SP compares the data in 2 tables and reports the different data. Tables could be from different servers, different databases or different schemas. This accepts 7 parameters 1, 2: Name of the 2 tables 3 : List only the differences 4. : Compare only the structure 5. : Check timestamp fields too 6. : […]

5 (1)

You rated this post out of 5. Change rating

2002-08-17

1,382 reads

Technical Article

Change the User Defined Data type

User Defined Data Types (UDF) is one of the useful concepts in SQL Server. However UDF can't be modified after they are being used. You would have to remove your User Defined Data Type from each table before you can change it. This will be a big job under certain circumstances.This procedure changes all tables […]

You rated this post out of 5. Change rating

2002-04-19

1,008 reads

Technical Article

Script Generator for Triggers

This Stored Procedure creates the script of all existing triggersOptionally it creates the script to drop the triggers too.Triggers may belong to different owners. This procedure takes care of it.In SQLServer Enterprise Manager there is a facility to generate scripts forTables, Views, Stored Procedures etc.But it won't generate script for triggers unless we include the […]

5 (6)

You rated this post out of 5. Change rating

2002-03-27

2,713 reads

Technical Article

Compare the structure & code of 2 databases

We often make changes in the test databases. But failure in making even the smallest change in the production database may lead to unwanted situations.This utility compares 2 databases.Parameters to be passed   @DB1  Database 1 (SysName)  @DB2  Databse 2 (SysName)  @ShowDifferentOnly see later (Bit)       Parameters 1, 2 may include server name as  well. […]

You rated this post out of 5. Change rating

2002-03-22

510 reads

Blogs

Prepping for Certification, Part 1 of ?

By

I thought it would be good to put my thoughts down on how to...

How to Avoid Knowledge Stagnation

By

You want the short answer? Well, the only antidote to knowledge stagnation is probably...

Demystifying Fabric Workspaces: The Nerve Center of Your Data Universe

By

It always starts the same way. You open your laptop on a Monday morning,...

Read the latest Blogs

Forums

A laboratory called FARE LABS Pvt. Ltd. does environmental and pollution testing

By farelabs

At the Fare facility, a NABL-approved environment pollution testing facility in India, our highly...

Guidelines and Requirements

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Guidelines and Requirements

Copying Production Schema

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Copying Production Schema

Visit the forum

Question of the Day

Copying Production Schema

If I use DBCC CLONEDATABASE, can I remove some of the information from the copy?

See possible answers