Just be careful with possible duplicates that can come from "user_role_job"

Hehe ... GetNextID again

Yes it does require careful programing practices.

In other set of things you should also try to keep access to...

Check out the "new" 2005 roles on msdb:

SQLAgentOperatorRole

SQLAgentUserRole

SQLAgentReaderRole

Assign the user on the one you need!

Cheers,

so you:

1. backed up the log

2. executed DBCC SHRINKFILE ('transaction log logical file name', 10000)

and still does not do it ?

what is the output of:

USE [dbname]

go

DBCC SQLPERF(LOGSPACE)

Glad I could help!

I did spent *some* time on this and at least it saved you some grief

I am not sure what ASPNETDB is but you can definitely call an stored procedure in the DBO schema without being db_owner just make sure that the account (role) used...

Ok lets try this:

Show me the output of:

USE CBR_DATA

GO

DBCC SQLPERF(LOGSPACE)

and

DBCC OPENTRAN ( CBR_DATA )

Is the DB Replicated ?

That depends on how much data are you willing to lose

you should create "roles" and then add users to roles as appropriate.

Are you sure you want that ?

If the answer is "yes" the just remove the truncateonly part!

DBCC SHRINKDATABASE (CBR_DATA)

dbcc checkconstratints ??

1. Is the database replicated ?

2. What's the recovery Mode

3. Are there any opened transactions ?

If you use sp_repldone you should be aware of the consequeces !!!!

That is a 2005 syntax but can use sort_in_temp in SQL Server 2000 !