Viewing 4 posts - 1 through 5 (of 5 total)
Yes, this is from Symantec. Their script is having all syntax errors, I made them fix to some point and got through those errors.
Finally I have fixed the problem,...
July 21, 2011 at 3:12 pm
SELECT sep5.V_ALERTS.ALERT_IDX, COM.IP_ADDR1_TEXT, COM.COMPUTER_NAME, COM.COMPUTER_DOMAIN_NAME,
ALE.USER_NAME, ALE.SOURCE_COMPUTER_NAME, ALE.SOURCE_COMPUTER_IP_TEXT, ALE.SOURCE, ALE.ALERT_IDX,...
July 21, 2011 at 2:23 pm
Here is the cleaner format of the SQL,
SELECT sep5.V_ALERTS.ALERT_IDX, COM.IP_ADDR1_TEXT, COM.COMPUTER_NAME, COM.COMPUTER_DOMAIN_NAME,
ALE.USER_NAME, ALE.SOURCE_COMPUTER_NAME, ALE.SOURCE_COMPUTER_IP_TEXT, ...
July 21, 2011 at 2:09 pm
I am getting the below error.
The multi-part identifier "sep5.V_ALERTS.VIRUSNAME_IDX" could not be bound.
Msg 4104, Level 16, State 1, Line 8
The multi-part identifier "sep5.V_ALERTS.COMPUTER_IDX" could not be bound.
Msg 207, Level...
July 21, 2011 at 1:42 pm
Viewing 4 posts - 1 through 5 (of 5 total)