Viewing 8 posts - 1 through 8 (of 8 total)
That's just some sample script. I believe someone put the DROP statement in there just to clean up.
I did add a UDF called DelimitedSplit, but can't figure out how...
May 3, 2010 at 1:03 pm
Sorry...got pulled into some other projects.
I found that the code is working as it should when using a "real" table with thousands of rows. The output looks good,...
May 3, 2010 at 11:02 am
I still don't know if it's practical to move around that much data, but at least we have some fat WAN pipes. One environment generates over 300MB/day in CAS...
April 20, 2010 at 11:24 am
The data is imported from a flat file. Nothing tricky here - just mapped the fields. I still haven't finalized the process of getting the logs copied from...
April 19, 2010 at 2:15 pm
This is looking very promising. Thank you.
As for the output, I'd prefer that it not include the name of the delimiter, only the value. i.e. "Ping" instead of...
April 14, 2010 at 12:20 pm
Yes. The parameters to parse are:
Cmd=
User=
DeviceId=
DeviceType=
Log=
Ampersands are placed before each, except for the first one. Here is a condensed example:
Cmd=Ping,&User=Me&DeviceId=MyDeviceID&DeviceType=MyDeviceType&Log=MyLogEntry
Another from a different device may look like this:
User=Me&DeviceId=MyDeviceID_with_more_characters&DeviceType=MyDeviceType&Cmd=Ping,&Log=MyLogEntry
For...
April 13, 2010 at 2:36 pm
Just tried the suggestion using the REVERSE commands and it returned too much data. I need it to stop when it gets to the next delimiter (which were @1:...
April 13, 2010 at 2:10 pm
To be honest, I haven't checked the 2nd suggestion offered to see if it works. I did read the article about the best way to post code on the...
April 13, 2010 at 9:54 am
Viewing 8 posts - 1 through 8 (of 8 total)