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.

Current log - too much entries?

Hello,

does anyone know what could be wrong? There's a lot of similar entries
in the SQL Server current log:

2004-01-21 17:54:00.01 spid57 Starting up database 'DB_NAME'
2004-01-21 17:54:06.45 spid57 Starting up database 'DB_NAME'
2004-01-21 17:54:59.13 spid56 Starting up database 'DB_NAME'

There are hundreds of similar entries that repeat every few seconds. The
database works quite slowly and the users get 'Connection timeout'
message very often.

Thanks for any advice.

...:: fabio"Fabio" <fabio@.anti-spam.inet.alpha.pl> wrote in message
news:bumbod$d6c$1@.nemesis.news.tpi.pl...
> Hello,
> does anyone know what could be wrong? There's a lot of similar entries
> in the SQL Server current log:
> 2004-01-21 17:54:00.01 spid57 Starting up database 'DB_NAME'
> 2004-01-21 17:54:06.45 spid57 Starting up database 'DB_NAME'
> 2004-01-21 17:54:59.13 spid56 Starting up database 'DB_NAME'
> There are hundreds of similar entries that repeat every few seconds. The
> database works quite slowly and the users get 'Connection timeout'
> message very often.
> Thanks for any advice.
> ..:: fabio

Probably the database is set to autoclose - if there are no active
connections, then it is closed. That means when a connection is made, the
database is opened again, which takes time. You can check like this:

select databasepropertyex('DB_NAME', 'IsAutoClose')

1 means it's on, so you can turn it off like this:

alter database DB_NAME set auto_close off

Simon

Current Log - Too Much Entries

Hello,
does anyone know what could be wrong? There's a lot of similar entries
in the SQL Server current log:
2004-01-21 17:54:00.01 spid57 Starting up database 'DB_NAME'
2004-01-21 17:54:06.45 spid57 Starting up database 'DB_NAME'
2004-01-21 17:54:59.13 spid56 Starting up database 'DB_NAME'
There are hundreds of similar entries that repeat every few seconds. The
database works quite slowly and the users get 'Connection timeout'
message very often.
Thanks for any advice.
..:: fabioCheck if the database option "Autoclose" is turned on and turn it off.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Fabio" <fabio@.anti-spam.inet.alpha.pl> wrote in message
news:bumc1f$2hu$1@.atlantis.news.tpi.pl...

quote:

---

> Hello,
> does anyone know what could be wrong? There's a lot of similar entries
> in the SQL Server current log:
> 2004-01-21 17:54:00.01 spid57 Starting up database 'DB_NAME'
> 2004-01-21 17:54:06.45 spid57 Starting up database 'DB_NAME'
> 2004-01-21 17:54:59.13 spid56 Starting up database 'DB_NAME'
> There are hundreds of similar entries that repeat every few seconds. The
> database works quite slowly and the users get 'Connection timeout'
> message very often.
> Thanks for any advice.
> ..:: fabio
>

---

|||Uncheck 'AUTO CLOSE' on the database properties options page. (Right click
database name in Enterprise Mangler, select Properties, click on Options
tab.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"Fabio" <fabio@.anti-spam.inet.alpha.pl> wrote in message
news:bumc1f$2hu$1@.atlantis.news.tpi.pl...

quote:

---

> Hello,
> does anyone know what could be wrong? There's a lot of similar entries
> in the SQL Server current log:
> 2004-01-21 17:54:00.01 spid57 Starting up database 'DB_NAME'
> 2004-01-21 17:54:06.45 spid57 Starting up database 'DB_NAME'
> 2004-01-21 17:54:59.13 spid56 Starting up database 'DB_NAME'
> There are hundreds of similar entries that repeat every few seconds. The
> database works quite slowly and the users get 'Connection timeout'
> message very often.
> Thanks for any advice.
> ..:: fabio
>

---

|||Fabio wrote:
Thanks a lot, Dejan and Geoff.
After turning the 'auto close' option the database works much faster and
the messages about database starting don't appear in the error log.
..:: fabio

Current Log - Too Much Entries

Hello,
does anyone know what could be wrong? There's a lot of similar entries
in the SQL Server current log:
2004-01-21 17:54:00.01 spid57 Starting up database 'DB_NAME'
2004-01-21 17:54:06.45 spid57 Starting up database 'DB_NAME'
2004-01-21 17:54:59.13 spid56 Starting up database 'DB_NAME'
There are hundreds of similar entries that repeat every few seconds. The
database works quite slowly and the users get 'Connection timeout'
message very often.
Thanks for any advice.
..:: fabioCheck if the database option "Autoclose" is turned on and turn it off.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Fabio" <fabio@.anti-spam.inet.alpha.pl> wrote in message
news:bumc1f$2hu$1@.atlantis.news.tpi.pl...
> Hello,
> does anyone know what could be wrong? There's a lot of similar entries
> in the SQL Server current log:
> 2004-01-21 17:54:00.01 spid57 Starting up database 'DB_NAME'
> 2004-01-21 17:54:06.45 spid57 Starting up database 'DB_NAME'
> 2004-01-21 17:54:59.13 spid56 Starting up database 'DB_NAME'
> There are hundreds of similar entries that repeat every few seconds. The
> database works quite slowly and the users get 'Connection timeout'
> message very often.
> Thanks for any advice.
> ..:: fabio
>|||Uncheck 'AUTO CLOSE' on the database properties options page. (Right click
database name in Enterprise Mangler, select Properties, click on Options
tab.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"Fabio" <fabio@.anti-spam.inet.alpha.pl> wrote in message
news:bumc1f$2hu$1@.atlantis.news.tpi.pl...
> Hello,
> does anyone know what could be wrong? There's a lot of similar entries
> in the SQL Server current log:
> 2004-01-21 17:54:00.01 spid57 Starting up database 'DB_NAME'
> 2004-01-21 17:54:06.45 spid57 Starting up database 'DB_NAME'
> 2004-01-21 17:54:59.13 spid56 Starting up database 'DB_NAME'
> There are hundreds of similar entries that repeat every few seconds. The
> database works quite slowly and the users get 'Connection timeout'
> message very often.
> Thanks for any advice.
> ..:: fabio
>|||Fabio wrote:
Thanks a lot, Dejan and Geoff.
After turning the 'auto close' option the database works much faster and
the messages about database starting don't appear in the error log.
..:: fabiosql

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.

Cube usage by users

Hi,

What would be the correct way to generate some kind of log or report that will tell me which user used which cube in which database along with the number of times the user connected to each cube each day? The number of queries sent by each user to each cube by day would be ok. I am not interested by the query content for this exercise. I just want Userid, DB name, Cube name and Hits.

Then I can take it from there and create a report for our security/sox guy with User name, Cube name, Week of year and number of hits by week, meaning if the users send 36 queries to Cube A on Monday and 2 queries on Friday, it counts for 2 cube accesses for that week.

This assume that I use only TCP/IP access but if the same mechanism would work for HTTP access that would be fine. I try not to use HTTP but I may be forced to do it.

Regardless of network transport, the only logins allowed are though Windows Domain Global Group Membership.

Seems simple but I do not find where to start.

Thanks,

Philippe

Hello,

I have found a solution to this issue.

In the Server property box, you will enable query loging to a table and set the interval to 1 instead of 10.

Stop and Start the AS Server

Create some query or cube to access your log data, you are done.

I cannot really provide a query example since it depends on your situation. Mine is linked to a Calendar and to a Users tables. I convert the query time to keep only the day and the username to keep only the userid, then I build some Cube and/or Report that joins all that stuff and do some DistinctCount on the daily access by Cube by User and voila. I keep my infosec guy happy and I know what are the cubes I can retire for cause of no use.

You know, sometimes they ask you to build a cube real quick, they use it once and then they forget about it (and do not tell you). So I am not maintaining useless cubes :-)

Regards,

Philippe

CSV file..

I do have a csv file and I want to save the file into log table but I
wondernig that datatype would be text or image ? and after that I want to
fetch the data from that file and save it into different table.. can any let
me know what would be the best way to do this ?
Thanks in advance
Hi,
Do this activity using some programing language.. Visual studio . Net will
be a best option.
Thanks
hari
SQL Server MVP
"Noor" <noor@.istcl.com> wrote in message
news:ew0hil6tFHA.256@.tk2msftngp13.phx.gbl...
>I do have a csv file and I want to save the file into log table but I
>wondernig that datatype would be text or image ? and after that I want to
>fetch the data from that file and save it into different table.. can any
>let me know what would be the best way to do this ?
> Thanks in advance
>
|||Thanks HARI...
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:u0I$TGAuFHA.3752@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Do this activity using some programing language.. Visual studio . Net will
> be a best option.
> Thanks
> hari
> SQL Server MVP
> "Noor" <noor@.istcl.com> wrote in message
> news:ew0hil6tFHA.256@.tk2msftngp13.phx.gbl...
>
|||Thanks HARI......
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:u0I$TGAuFHA.3752@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Do this activity using some programing language.. Visual studio . Net will
> be a best option.
> Thanks
> hari
> SQL Server MVP
> "Noor" <noor@.istcl.com> wrote in message
> news:ew0hil6tFHA.256@.tk2msftngp13.phx.gbl...
>