waiting for another Avatar – discussion
Kedar
Are we waiting for another “Avatar”?? As per Hindu mythology, lord Vishnu took 10 different avatars to save our world. As per mythology, lord Vishnu will take avatar when Rakshasas…
Petition – Help saving MySQL – II
And I looked back and thought of updating this post… Recently Monty has posted again and I completely convinced with whatever Monty has conveyed now or earlier. The explainations he has provided under self-interview,…
MySQL Memory Usage Limits on 32 bit Linux
I’m having RHEL 5 (32-bit) and MySQL-5. I was trying to check how much is the Memory Utilization limits for MySQL 5 on 32bit OS. We can easily calculate the…
MySQL Certification Free Retake: Get TWO chances to get MySQL Certified
Recently MySQL has offered MySQL Certification Free Retake on both DBA or Developer Certifications for a limited time. For MySQL Certifications: 1. MySQL 5.0 Data Base Administrator Certification (SCMDBA) –…
Monty: Help Saving MySQL – The Oracle & EC
And I looked back and thought of updating this post… We all are aware about the acquisition happened to MySQL; Sun and now Oracle. A common understanding tells me that…
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