if there is still something to drop, even if not 'visible',

running sp_removedbreplication on both the publisher and subscriber

should clean.

Else I don't have any suggestion more...

the thing I would try is to drop the subscriptions and stop all agents of distribution. or better, drop the whole replication. Time ago I had a similar problem and...

if the replication is merge or transactional, you will have to stop the agents.

Have you tried dropping the database using the script:

Alter DATABASE yourdb SET OFFLINE

DROP Database yourdb

sb

I've just found this script in the 'Scripts' section, it can be very useful!

SELECTt.name as [DB Name],

t.user_access_desc as [Access State],

t.state_desc as [Online/Offline],

((SELECT (CASE t.is_in_standby WHEN 0 THEN 'No' WHEN 1...

running the query

SELECT database_name, MAX(backup_finish_date) backup_date

FROM msdb.dbo.backupset

GROUP BY database_name

you can get the most recent backup date of the databases, you can rerun the script for those with backup date older...

Perfect, thanks, it worked using

backup log database_name with truncate_only

go

DBCC SHRINKDATABASE (database_name, 10, TRUNCATEONLY)

go

alter database database_name

remove file logicalfilename

This is what I thought, but I wasn't sure.

Many thanks, sb

I have a problem in adding a linked server from sql 2005x64 to oracle.

I have created the linked server

EXEC sp_addlinkedserver

@server = 'job',

@srvproduct...

Many, many thanks for your accurate reply!

sb

Our cluster is active-active, so in the same time there are system database running on separate instances.

The reason for datatyped in model is that the application creates temporary tables containing...

Hello,

I had the same problem, msg 8992. Some views and stored procedures of a database were trying to reference to a no more existing field of a table. After finding...

Thanks a lot, Tom, it worked!

sb

half knowledge and half luck...

he knew that there is an index in sysfiles1,

sp_spaceused 'sys.sysfiles1' told that index_size=0, it means it had not been possible to allocate...

After a few tryes, our consulent has solved the problem: the first datafile, which run out of space, contains the data of sysfiles1 and there were problems in adding its...

Thanks for your new ideas, I've tried to backup model's transaction logs, but I still get the same error.

I've tried also dump transaction with no_log with no success.

Checkdb found 0...