No entries show up in SQL Server Profiler trace

Hi,
I have inherited a SQL Server 2000 machine with 59 databases on it,
several of which I suspect are no longer used.
I am setting up a SQL Profiler trace to show me which databases are
still being accessed, and by which machine/user.
There are 4 other SQL Servers in use here, too, running SQL Server 6.5,
7, 2000 and 2005.
The problem I'm encountering is this:
I start the Profiler trace on SQL Server machine A
>From my local machine's Query Analyzer, I then query a table in one of
the suspect databases on machine A, via a linked server entry in my
local SQL Server instance
None of this query activity against the database is logged in Profiler
on machine A
What am I missing?
Thanks in advance-
Jason
I figured it out. I am now monitoring the event class "Security
Audit->Audit Object Persmission Event", and bringing back the data
columns ObjectName, LoginName, and Hostname to know what's being looked
at, by whom, and from what machine.
JasonReber@.gmail.com wrote:
> Hi,
> I have inherited a SQL Server 2000 machine with 59 databases on it,
> several of which I suspect are no longer used.
> I am setting up a SQL Profiler trace to show me which databases are
> still being accessed, and by which machine/user.
> There are 4 other SQL Servers in use here, too, running SQL Server 6.5,
> 7, 2000 and 2005.
> The problem I'm encountering is this:
> I start the Profiler trace on SQL Server machine A
> the suspect databases on machine A, via a linked server entry in my
> local SQL Server instance
> None of this query activity against the database is logged in Profiler
> on machine A
> What am I missing?
> Thanks in advance-
> Jason

No entries show up in SQL Server Profiler trace

Hi,
I have inherited a SQL Server 2000 machine with 59 databases on it,
several of which I suspect are no longer used.
I am setting up a SQL Profiler trace to show me which databases are
still being accessed, and by which machine/user.
There are 4 other SQL Servers in use here, too, running SQL Server 6.5,
7, 2000 and 2005.
The problem I'm encountering is this:
I start the Profiler trace on SQL Server machine A
>From my local machine's Query Analyzer, I then query a table in one of
the suspect databases on machine A, via a linked server entry in my
local SQL Server instance
None of this query activity against the database is logged in Profiler
on machine A
What am I missing?
Thanks in advance-
JasonI figured it out. I am now monitoring the event class "Security
Audit->Audit Object Persmission Event", and bringing back the data
columns ObjectName, LoginName, and Hostname to know what's being looked
at, by whom, and from what machine.
JasonReber@.gmail.com wrote:
> Hi,
> I have inherited a SQL Server 2000 machine with 59 databases on it,
> several of which I suspect are no longer used.
> I am setting up a SQL Profiler trace to show me which databases are
> still being accessed, and by which machine/user.
> There are 4 other SQL Servers in use here, too, running SQL Server 6.5,
> 7, 2000 and 2005.
> The problem I'm encountering is this:
> I start the Profiler trace on SQL Server machine A
> the suspect databases on machine A, via a linked server entry in my
> local SQL Server instance
> None of this query activity against the database is logged in Profiler
> on machine A
> What am I missing?
> Thanks in advance-
> Jason

No entries show up in SQL Server Profiler trace

Hi,
I have inherited a SQL Server 2000 machine with 59 databases on it,
several of which I suspect are no longer used.
I am setting up a SQL Profiler trace to show me which databases are
still being accessed, and by which machine/user.
There are 4 other SQL Servers in use here, too, running SQL Server 6.5,
7, 2000 and 2005.
The problem I'm encountering is this:
I start the Profiler trace on SQL Server machine A
>From my local machine's Query Analyzer, I then query a table in one of
the suspect databases on machine A, via a linked server entry in my
local SQL Server instance
None of this query activity against the database is logged in Profiler
on machine A
What am I missing?
Thanks in advance-
JasonI figured it out. I am now monitoring the event class "Security
Audit->Audit Object Persmission Event", and bringing back the data
columns ObjectName, LoginName, and Hostname to know what's being looked
at, by whom, and from what machine.
JasonReber@.gmail.com wrote:
> Hi,
> I have inherited a SQL Server 2000 machine with 59 databases on it,
> several of which I suspect are no longer used.
> I am setting up a SQL Profiler trace to show me which databases are
> still being accessed, and by which machine/user.
> There are 4 other SQL Servers in use here, too, running SQL Server 6.5,
> 7, 2000 and 2005.
> The problem I'm encountering is this:
> I start the Profiler trace on SQL Server machine A
> >From my local machine's Query Analyzer, I then query a table in one of
> the suspect databases on machine A, via a linked server entry in my
> local SQL Server instance
> None of this query activity against the database is logged in Profiler
> on machine A
> What am I missing?
> Thanks in advance-
> Jason

Nightly Maintenance Backup Plan fails -- no trace of why

We have been running a backup plan (created using the sql 2005 Maintenance wizard) for some time. It failed last night but all databases seemed to be backed up.

I looked at the ERRORLOG in <mssql2005>\mssql.1\log as well as

"Servname DB Backup Plan_20070118184358.txt"

but found no errors. Where else can I look to see what went wrong?

TIA,

barkingdog

You can also check the logs of the Sql Server Agent job corresponding to the maintenance plan.

Thanks,

Kuntal

|||

>>> check the logs of the Sql Server Agent job

Where are these located? (Are you referring to SQLAgent.OUT? It had nothing of interest.)

Barkingdog

|||

In Sql 2005, for every maintenance plan an Sql Agent job is created by the same name. You can view its logs as Sql Server Agent -> Jobs -> select the job & right click to View History.

Hope that helps

Kuntal

|||

What was the error under the scheduled job for this maintenance plan?

Also try to run thsi manually from SSMS to see the execution, also ensure the SQLAgent account has required privileges to run this job. ALso check what changes have been since last time when this job was running succesfsully.