Yes, DBCC FREESESSIONCACHE can be used in case of distributed environment.Agree, not to use in Production environment unless you have a maintenance window.

It will.I witnessed it.See my post..I said after clearing cache, perform shrink operation.:smooooth:

Who said to run it production server? I am giving an alternative to shrink tempdb without restarting server as asked in the very first post.This will help I guess:cool:

Run this before performing shrink operation.

Use tempdb

go

DBCC FREESYSTEMCACHE(ALL);

DBCC FREESESSIONCACHE;

then perform your shrink operation.

Thanks

Vivek

DB is not visible. How can we proceed now?

Its getting messy. Let simplify the point. Can we recover a database to its maximum with a full backup and valid ldf file available? Truncation logs were not performed on...

My recovery model is full. This is a UAT database. I know if there were t-log backups, the database could have been recovered to its maximum. I am repeatedly saying...

Can you elaborate your point?

As GilaMonster said to use emptyfile option, can it be done on the file which has some used extents.I am asking because I had performed DBCC FILESTATS and I saw...

No response yet:ermm:.Any clue might help.

Vivek

Use DBCC SHOWFILESTATS to check if your database file still has some used extents.

Generally there are two reasons if a file cannot be removed from a filegroup after being used...

I was not distinguishing view and an indexed view.I know very well that they are two different things:cool:.I guess the above posts are not confusing for Vyas bcoz some posts...

I was asking have you tried restoring on the server with same version.:laugh:If yes,do you get the same error message.

And, in case of different versions, I guess George is right.

Vivek

You said that you are trying to restore it to a different location.Does the destination server has same version of SQL Server as of the the source server?Can you try...

Ok..then my previous post might help you.

Vivek