Current SQL Server Logs

I am not able to open the current sql server log file from
enterprise manager in one of my servers. I can open the
archive logs below the current one in enterprise server.
When I double click the current log to open it hangs
everything. What is going on on this server, any help
please.Aboki,
Try recycling the error log using sp_cycle_errorlog
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Aboki" <waco361@.hotmail.com> wrote in message
news:0bda01c36b22$517e07e0$a501280a@.phx.gbl...
> I am not able to open the current sql server log file from
> enterprise manager in one of my servers. I can open the
> archive logs below the current one in enterprise server.
> When I double click the current log to open it hangs
> everything. What is going on on this server, any help
> please.

Cumulative log

Is it possible to create a cumulative log using SSIS? basiclly I have 5 logs which hold failed records. I would like to create a cumulative log and send it via email using SSIS.

thoughts?

thanks

What do you mean "cumulative"? If you use a table to store your error records, you can pull in that table and send the records in an e-mail.

Though, if the records are going to be high, you may want to pull the records out to a text file and then attach that file in the Send Mail task. A better approach would be to house everything in a table and write a report against it.|||

how do you pull in different tables? via sql task? and what if you have more 1 table? you would only want to send one email with all the bad records from different tables.

|||Just create one error table. Log all of the bad records to that table and then later select from that table.|||

well all tables have different structures so a single table would not work. any other ideas?

|||If you want to combine them, you are going to have to make the structures similar at some point, right? You could use a dataflow with multiple sources to combine the tables into a flat file, then email that as an attachment.|||

I don't see an straight forward way to get all those rows into a single file/email. Perhaps, it may be easier to include just the key column(s); in such way the structure is the same for all the tables.