Can I edit or update the content of a stored procedure in iron speed or not? If I would update it through sql server management studio and i would rebuild my application in iron speed, will my updated stored procedure deleted or not? Please do help me with this. Badly need your ideas. Thank you
As long as the stored proc name stays the same it has to work. I've done this before with custom stored procedures where I edit the content of the stored proc in sql server management studio and then resync the database with ISD. Just keep the stored proc name the same.
Related
I wrote a stored procedure in firebird server. The procedure is used on several different servers and databases. On one of them, the procedure is carried out very slowly (a few hours) where in the other servers in 3-5 seconds.Indices in each database are the same.
Do any of you encountered such a problem? We made a backup and restored a database but it did not help.
When I had such a problems, it was always either corrupted database (SELECT at table with 10 records lasted few minutes) or just needed recalculation of index statistics. Try to check and fix database with gfix. If recalculating of index statistic helped, consider adding plan to your SQL statement
I've got this message when I'm editing a procedure in Oracle 11g
Actually I'm the only one who is editing the procedure. Sometimes when I'm coding, it prompts, I accidentally press space bar and it loads the last saved codes. This happened a few times. I got mad.
Why does this message prompt even I'm the only one who edits this procedure? Is this related to the setting of my SQL developer? The version I'm using is 4.0.3.
Looks like this is caused by the client and db server time being off.
"We're checking the time in the db to see when the last time it was modified and comparing it to your local time. Can you confirm your db and local times are correct?"
That Jeff Smith (SQL Developer Team Lead or something)
https://community.oracle.com/thread/3513778?tstart=0
I am developing with Microsoft SQL Server 2008 R2 Express.
I have a stored procedure that uses temp tables and outputs some processed data usually within 1 second.
Over a few months, my DB has gathered a lot of data almost reaching the 10 GB limit. At this point, this particular stored procedure started taking as much as 5 mins for the same input parameters. After I emptied some of the huge tables in DB, it got back to normal.
After this incident, I am worried if my stored procedure needs more than necessary space in DB. How can I be sure? Any leads?
Thanks already
Jyotsna
Follow this article
Other old school way is run spwho2 check your spid related to the database see CPU and IO usage.
To validate run DBCC INPUTBUFFER(spid)
Also check STATISTICS of SP in original scenario without purging data from tables.
SET STATISTICS IO ON
EXEC [YourSPName]
see the logical reads , also refer article
Currently, if I want to make a backup of a stored procedure, using Mircosoft SQL Server Management Studio 2008 R2, I right click on my stored procedure, choose modify and then in the stored procedure change alter proc part to create proc, and add the word "backup" to the end of the name of the stored procedure. Is there a better way to do this? In a perfect world, I would like to be able to backup all the stored procedures in a database and keep them maybe somewhere locally. I don't like how my list of stored procedures is getting sloppy (for lack of a better word) with all these backups I have made. If you can't tell, I am exteremly new to writing stored procedures and want to be able to have this to safeguard the existing stored procedures from any mistakes I might make.
Thanks in advance for all your help!
There are multiple ways to keep backups of your stored procedures apart from your live database. Here are just a few:
When you backup your database, all the stored procedures are included in that backup. If you need to revert to an older version, you can restore to another database and script the procedure to a new editor tab or file or whatever. Hopefully, you have a live and test database anyway, so you could just go to your live database and script the stored procedure there rather than having to restore from backup.
You can script each version of your stored procedure to separate files as you create them and name and append a date to the name of the file. You can script all existing stored procedures by looking at the answer to this question.
You can use a version control product. I'm not sure if I'm allowed to point you to one here, but just do a search on "SQL source control" and you will find a very good one in the search results.
I would like to see all the input values passed into a particular user-defined stored procedure to SQL Server. I am using SQL Server 2008 Management Studio. Sometimes I don’t have access to the client code that calls this procedure, and the bug is likely inside the procedure, therefore, I want to know when and what the input values my procedure executes with. If this information, I can debug the procedure without running the whole complicated process.
SQL Profiler will give you this information. You need ALTER TRACE permissions on the database to run Profiler.
http://msdn.microsoft.com/en-us/library/ms181091%28v=sql.105%29.aspx
In addition to the Start Menu link, you can run it from the "Tools" menu in SQL Server Management Studio.