Remember, the trace is recycled based on the transaction level of you SQL Server. So you might end up filling up the trace in 1/2 a day or even 2...

Having Roles is a good Primary Choice.

consider Blocking Incoming Applications at FIREWALL. (Firewall Rules)

Create a TRIGGER to check for username and Program_name from sysprocesses and immideatly Kill the Process inside...

Does the application have any APPLICATION / DATABASE Roles.

Are the users even able to login using their windows ID's apart form the SQL ID

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=338537&SiteID=1

and

http://blogs.msdn.com/sql_protocols/archive/2005/09/28/474698.aspx

about Database uptime: as far as i know there is nothing to prove database uptime. Except when it was last used.(lookup db objects)

yes you can create the job to send...

Does this happen Frequently or Rarely.

If it is a RARE kind of Deal, you can ignore this messages in the LOG.

As per Microsoft:

You may receive this error message when you...

The TRACE files are under the SQL Server LOG Folder by default.

That is kind a challenging and if anybody will provide you a script might be Half baked or someting..

Try to Google around.

But here is a list of countries to start...

check your default SQL Trace and check to see for any such activity...

Are you trying to O/P the result of a Query or something else.

What does this job do..

Try to get the DB in SIMPLE Recovery Mode and then

use DatabaseName

DBCC SHRINKFILE(transactionlogname,10).This will Shrink your Log to 10MB in size etc...

Try this also in FULL Mode.

can you do a sp_helpdb [database name]

Check your translog Growth.

Check your Growth % if changed.

Maybe it is the transaction Log.

Describe your Recovery mode.(Full/SIMPLE/BULK)??

how many users are connecting to the Database.

Was...

Ok, Just try a RESTORE with REPLACE like this:

RESTORE DATABASE [your database name] from disk = 'Backup file name and path'

WITH REPLACE, RECOVERY

Yes Client Licenses are not a good choice, if you are planning a website with good # of users. Try diggning into the per processor Licensing strategy, that could simplify...

Try to drop the database with 'drop database' statement then restore from backup. If you have a valid BAckup.