Viewing 10 posts - 16 through 25 (of 25 total)
First of all, there is an sp_helptext command. What you could do is to dump the contents of this to a text file for each of the stored procedures.
You could...
September 1, 2004 at 7:54 am
My first bit of advise is to put as much of the query in SQL server as possible to limit the amount of code that you have to write in...
August 31, 2004 at 6:51 am
I had a discussion with some folks who were needing this as well. I believe to solve their problem, they ran the output through another program to look for the...
August 31, 2004 at 6:36 am
I agree that formatting is the job of the presentation layer, but aggregating data may not be. While the original question did not say, the data may be used in...
August 27, 2004 at 10:44 pm
Indexes and statistics are definitely worth checking. However, I would also consider rewriting the code for the text file processing into a stored procedure as well. Even if you keep...
August 27, 2004 at 6:01 am
I think that one option is to make use of temp tables, and if you reuse the result, persist the data in a global temp table rather than a local...
August 26, 2004 at 7:03 am
I think that one option is to make use of temp tables, and if you reuse the result, persist the data in a global temp table rather than a local...
August 26, 2004 at 6:59 am
Look for Lock problems.
Check statistics, update as necessary.
Reindex.
Use SPs over ad hoc T-SQL.
Limit joins - opt for temp tables where large, relatively static intermediate results are reused.
Break the problem down...
August 20, 2004 at 10:59 am
try doing datediff for number of days instead.
Beer is the answer to all the world's woes.
August 20, 2004 at 10:53 am
I like Lumigent's log reader. but allow me to warn you, I believe it may interfere with standby server functionality because of its interaction with the logfile
August 20, 2004 at 10:48 am
Viewing 10 posts - 16 through 25 (of 25 total)