Viewing 8 posts - 1 through 9 (of 9 total)
Oh heck yeah! That's it!
I tried "[*]" but actually needed "*[*]*". Thanks wolfkillj!
March 18, 2011 at 1:30 pm
Your solution worked. In my expression, I did a replace() on the field and searched for the new character.
I'd like to keep this post open to see if...
March 16, 2011 at 12:39 pm
Yes, I have tried both: [*] and "**".
I also tried preceding the asterisk with the following characters:
~`!@#$%^&*-_+=<>?/\|
So for example:
blah, blah, blah... Fields!MESSAGE_TEXT.Value like "\*"
No success.
March 15, 2011 at 10:48 am
I found this solution online:
Basically, I needed to use the Oracle Provider for OLE DB instead of the Oracle Provider.
My query fails in Query Designer with...
March 15, 2011 at 10:41 am
I think you're getting closer to my problem. Oracle doesn't like the format (or data type) of the parameter when passed to the SQL statement. I'm not writing...
March 14, 2011 at 11:17 am
Thanks for your reply but I don't think that's the problem.
My query runs fine in Reporting Services' Query Designer. Here's the statement:
select distinct
originating_timestamp,
message_text
from
...
March 14, 2011 at 8:59 am
We had windows updates go in last night so all servers rebooted and flushed all traces as you said they would. Spotlight then created one new trace for all...
December 15, 2010 at 7:59 am
That's it! I had a start up procedure that enabled xp_cmdshell, ran some scripts, and then disabled it. I removed the disable statement.
Thank you!
October 15, 2010 at 11:47 am
Viewing 8 posts - 1 through 9 (of 9 total)