Monitoring

Hi ,
Is there a way/tool in Sql Server 2000 SP3 to
monitor all activities going on in the Database ?
For example, I first create an empty database.
Then I have an ERWIN generated DDL to create
all views and tables. After that, I have INSERT
scripts that populate all the base tables. What I
want to monitor is success or failure for each
script.

Thanks,
N.N (N@.N.COM) writes:
> Is there a way/tool in Sql Server 2000 SP3 to
> monitor all activities going on in the Database ?
> For example, I first create an empty database.
> Then I have an ERWIN generated DDL to create
> all views and tables. After that, I have INSERT
> scripts that populate all the base tables. What I
> want to monitor is success or failure for each
> script.

The tool you are looking for is the Profiler. Look in the SQL Server
program group.

However, to check the output from build scripts, I think it's best to
save the log, and then search the output for the string "Msg".

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||"N" <N@.N.COM> wrote in message news:<17xUb.21778$_f.2385@.newssvr25.news.prodigy.com>...
> Hi ,
> Is there a way/tool in Sql Server 2000 SP3 to
> monitor all activities going on in the Database ?
> For example, I first create an empty database.
> Then I have an ERWIN generated DDL to create
> all views and tables. After that, I have INSERT
> scripts that populate all the base tables. What I
> want to monitor is success or failure for each
> script.
> Thanks,
> N.

You can use Profiler to view all SQL being sent to the database, but
it sounds like you want to add error handling to your scripts? How to
do that would depend how you run the scripts - eg. if you're using
osql, then -r might be useful. Perhaps if you can give some extra
information about how you call the scripts, and an example of the
code, then someone may be able to suggest something specific.

Simon