![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Initially I had created a Perf Counter Log job that would save it to a text (csv) file. Recently I decided to start saving the information to SQL tables and since then SQL Perf Counters Log keeps stopping at random hours; I set up the Stop log After Option to 300 day Units and the When a log file closes to Start a new log file. I have had to start the Log file manually everytime; is there anything I can do about it or should I go back to saving it to csv files? Thanks, |
#3
| |||
| |||
|
|
Initially I had created a Perf Counter Log job that would save it to a text (csv) file. Recently I decided to start saving the information to SQL tables and since then SQL Perf Counters Log keeps stopping at random hours; I set up the Stop log After Option to 300 day Units and the When a log file closes to Start a new log file. I have had to start the Log file manually everytime; is there anything I can do about it or should I go back to saving it to csv files? Thanks, |
#4
| |||
| |||
|
|
Initially I had created a Perf Counter Log job that would save it to a text (csv) file. Recently I decided to start saving the information to SQL tables and since then SQL Perf Counters Log keeps stopping at random hours; I set up the Stop log After Option to 300 day Units and the When a log file closes to Start a new log file. I have had to start the Log file manually everytime; is there anything I can do about it or should I go back to saving it to csv files? Thanks, |
#5
| |||
| |||
|
|
Initially I had created a Perf Counter Log job that would save it to a text (csv) file. Recently I decided to start saving the information to SQL tables and since then SQL Perf Counters Log keeps stopping at random hours; I set up the Stop log After Option to 300 day Units and the When a log file closes to Start a new log file. I have had to start the Log file manually everytime; is there anything I can do about it or should I go back to saving it to csv files? Thanks, |
#6
| |||
| |||
|
|
Initially I had created a Perf Counter Log job that would save it to a text (csv) file. Recently I decided to start saving the information to SQL tables and since then SQL Perf Counters Log keeps stopping at random hours; I set up the Stop log After Option to 300 day Units and the When a log file closes to Start a new log file. I have had to start the Log file manually everytime; is there anything I can do about it or should I go back to saving it to csv files? Thanks, |
#7
| |||
| |||
|
|
Initially I had created a Perf Counter Log job that would save it to a text (csv) file. Recently I decided to start saving the information to SQL tables and since then SQL Perf Counters Log keeps stopping at random hours; I set up the Stop log After Option to 300 day Units and the When a log file closes to Start a new log file. I have had to start the Log file manually everytime; is there anything I can do about it or should I go back to saving it to csv files? Thanks, |
#8
| |||
| |||
|
|
Initially I had created a Perf Counter Log job that would save it to a text (csv) file. Recently I decided to start saving the information to SQL tables and since then SQL Perf Counters Log keeps stopping at random hours; I set up the Stop log After Option to 300 day Units and the When a log file closes to Start a new log file. I have had to start the Log file manually everytime; is there anything I can do about it or should I go back to saving it to csv files? Thanks, |
#9
| |||
| |||
|
|
Initially I had created a Perf Counter Log job that would save it to a text (csv) file. Recently I decided to start saving the information to SQL tables and since then SQL Perf Counters Log keeps stopping at random hours; I set up the Stop log After Option to 300 day Units and the When a log file closes to Start a new log file. I have had to start the Log file manually everytime; is there anything I can do about it or should I go back to saving it to csv files? Thanks, |
#10
| |||
| |||
|
|
Initially I had created a Perf Counter Log job that would save it to a text (csv) file. Recently I decided to start saving the information to SQL tables and since then SQL Perf Counters Log keeps stopping at random hours; I set up the Stop log After Option to 300 day Units and the When a log file closes to Start a new log file. I have had to start the Log file manually everytime; is there anything I can do about it or should I go back to saving it to csv files? Thanks, |
![]() |
| Thread Tools | |
| Display Modes | |
| |