Viewing 9 posts - 1 through 9 (of 9 total)
sorry about that. I've edited the original post to fix the error.
March 20, 2008 at 3:22 pm
It's not pretty, but you might try something like this:
declare @t table(line varchar(8000))
insert @t exec sp_helptext 'myProc'
declare @ddl varchar(8000)
select @ddl = ''
select @ddl = @ddl + line
March 20, 2008 at 3:01 pm
a "trigger" in SQL Server (and other RDBM systems I know) is fired on a database action like insert, update or delete.
I think your problem looks more like a...
March 7, 2008 at 9:44 am
Thanks, that was a good read. I knew that the correlated subquery caused it to be a RBAR approach, just packaged in a single query in case you are...
March 5, 2008 at 12:25 pm
OK, the same technigue of packing aggregate into a string, but using a correlated subquery.
March 5, 2008 at 11:47 am
I just got into work to try it, and it looks like I didn't understand the question. Sorry about that.
March 5, 2008 at 11:13 am
Here's another approach that I use sometimes. Pack all the data you want into a fixed length string, aggregating on your desired ID then unpack if from the string.
March 5, 2008 at 9:45 am
what purpose does this serve?
LEFT OUTER JOIN Tags
INNER JOIN RecordedCallsTags
ON Tags.ID = RecordedCallsTags.TagID
ON RecordedCalls.ID = RecordedCallsTags.CallID
You are not selecting anything from it,...
March 4, 2008 at 10:11 am
His joins all have an ON clause. He has something like join-on-join-join-on-on.
March 4, 2008 at 10:05 am