Whats New-Google Buzz in Gmail Inbox, Mobile
Kedar
This morn one more way of e-socializing introduced by google – Google Buzz. It’s a one of the trending topic on twitter… How to get Google buzz: Well it’s being…
Browsing Tag
Technical
22 posts
How to bulk rename table MySQL
Are you tired of manually renaming MySQL tables, one by one, especially when dealing with a large number of them? In this guide, we’ll introduce you to a MySQL stored…
Oracle query-eliminate duplicate but one using rowid
Yesterday a friend came across an oracle query problem: Consider below table: cid cname…. cdata 1 x xxxx 1 x xxxx .. 2 xzzz fjnd 3 a evddd Now the…
My Google Exploitation – Web History Graphs 2009
Well no doubt I’m a google freak. I’ve learnt a lot through it and I have searched a lot. But I wasn’t much aware about my intencity of googling stuffs.…
crontab not working with dynamic date filename – rhel linux
I have done it for so many times, setting a cronjob. Today I was tring to set a simple cronjob which will output the log file with timestamp attached filename.…
Stored procedure to Find database objects
This procedure lists available database objects under passed database name. It lists present Tables, Views, Stored Procedures, Functions and Triggers under particular database. It also lists storage engine of tables.…
One response to “Stored procedure to Find database objects”
Visual Studio and SQL Server management Studio are two different entities. So it takes a lot of time when we try an interaction with the database from Visual Studio then it takes a lot of time.
When we are using desktop applications then we do not realize this time delay, but while using web applications the time delay becomes an important factor because the database is on the remote server so a huge time delay is observed.
Normally, the query that we write in Visual Studio is first compiled and then executed in Sql Server which then returns the results. So, this is why a time delay is observed.
The answer to this is Stored Procedure usage. The Stored Procedure is stored in compiled format in SQL server so when we call it from Visual Studio application then it is just executed. Thus saving a lot of time.
An illustration of proper usage of STORED PROCEDURE has been displayed in the following video. You may see it:
http://www.visiontechno.net/studymats/storeprocedure.html