![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Why does the Security Log in the Event Viewer go nuts with entries when a DTS pacakge runs? There will literally be thousands of entries together averaging about 20 identical messages in the very same second. Aside from changing logging from "Full" to something else, is there a way to get DTS packages not to log so wildly? It seems as though a security entry is logged for each row transformed -- I can't think what else could cause this type of logging. Thanks for any input anyone can provide. Chuck |
#3
| |||
| |||
|
|
In article <eEEUbD4WDHA.1512 (AT) TK2MSFTNGP11 (DOT) phx.gbl>, CR jilesjilesjse (AT) jilesjsilessef (DOT) ?.invalid> writes I should mention that the package is being run interactively by a user connecting via registered server. The two repeating entries look like this: Here's the 1st one: Successful Network Logon: User Name: XXXXXX Domain: XXXXXX Logon ID: (0x0,0xXXXXXX) Logon Type: 3 Logon process: NtLmSsp Authentication package: NTLM Workstation Name: XXXXXX Here's the 2nd one: User Logoff: User Name: XXXXXX Domain: XXXXXX Logon ID: (0x0,0xXXXXXX) Logon Type: 3 So, it's a continuous series of logon and logoffs only fractions of seconds apart with several logons and logoffs occurring in a single second and lasting for several minutes (or as long as the package takes to complete). It's as though each single row being transformed results in a logon and a logoff. "CR" <jilesjilesjse@jilesjsilessef> wrote in message news:uRtgHi3WDHA.2312 (AT) TK2MSFTNGP10 (DOT) phx.gbl... Why does the Security Log in the Event Viewer go nuts with entries when a DTS pacakge runs? There will literally be thousands of entries together averaging about 20 identical messages in the very same second. Aside from changing logging from "Full" to something else, is there a way to get DTS packages not to log so wildly? It seems as though a security entry is logged for each row transformed -- I can't think what else could cause this type of logging. Thanks for any input anyone can provide. Chuck I cannot imagine you are seeing a login for every row, the performance hit would be stupid. Just an idea, but have you got log to SQL Server set on the package properties? Does this use a trusted connection? I believe logging makes multiple connections, as you can query the log tables part way through a package and get real-time progress information in this way. -- Darren Green (SQL Server MVP) DTS - http://www.sqldts.com |
![]() |
| Thread Tools | |
| Display Modes | |
| |