Actually, I wish it would use more RAM sometimes. Drives me nuts when it has to keep banging on the disk all the time while switching between the same couple of windows with a coupla GB unused RAM...

Bah...at first glance I thought this was unanswered....in any case, drop the '' inside your IN and give it a list of separate values - sounds like that's already fixed ya right up... -Dave

I'll assume you're using VB.NET or something similar... If you don't want to show certain columns, simply don't show them. This may entail turning off auto-generate columns in your grid and adding in your own custom column definitions (lots of examples of grids can be found on Google.) The other alternative is to make your datasource come from a query or view rather than grabbing the whole table. -Dave

OK, so your DB started performing poorly after it ran for awhile....that's a pretty broad problem, but here's a few things you might try: 1) I fully agree with Bob's post - if you want it to work correctly, get someone who knows what they're doing to set things up properly. (Though I understand that doesn't fix your problem today.) 2) Check for any tables that have grown excessively large. It's possible that you have some large logging / history tables and such that can easily be archived and deleted from the working tables. 3) If there's any way to narrow your problem down to a few areas (perhaps the top 2 or 3 stored procedures you're having trouble with?) you can look at modifying indexes specifically to help with those queries - just be sure you don't replace one problem with another. 4) You could always throw more hardware at it for a temporary fix... If you have any more specifics about what the problem is, perhaps we could better help. -Dave

Thanks, Bob...just wish there was a different answer. The more I think about this though, it just seems that there really should be some way to do a sub-query against a stored proc's result set from SQL Server management studio without having to define specific tables, or do anything funky like parsing the SP to auto-create a result table. Perhaps I just need to add this into a feature request for MS. Just in case...anyone else have a suggestion on how to narrow down the results of a stored proc from within Management studio? Something like being able to run a query against the results window sure would be handy. Thanks, Dave

And one other gotcha....OPENROWSET() isn't enabled on some servers I have to work with... -Dave

Here's the short question - how can I make this work? create function callme() returns TABLE AS RETURN(exec MyExistingSP) And the longer question on why I'd want it to... * I've got several stored procs that return table result sets that are fairly large (or larger than I care to scroll through) * Often, I'm doing ad-hoc queries where I only want to see one or two rows returned by the stored proc. * If I need to whip up a function/stored proc to allow this, it would be handy if it would take the stored proc name as a parameter * Would also be nice to take a subset of the column list in a select, or add an order by * I'm most interested in SQL Server 2000+ * Performance is not an issue (within some reason...), as this is only for typed in ad-hoc queries select column1, column2 from callme('MySP') where id > 500 order by LastModified --> would be nice to see the subset... I can do this easily with a multiline function for each stored proc, but it's not worth that much work. I keep hoping there's just a twist of syntax I'm missing, but I'm afraid that's not the case... Any thoughts? Thanks, Dave