Vivek,

That was pretty rude to someone who is trying to help you.

I have never heard of Stored Function Tables and I'm sure sushila has never heard of them either. ...

The issue here is the 'active' and 'inactive' parts of the transaction log. The active portion are those transactions that have not been committed to the database. You...

I just use DEFRAG. Basic ifference - DEFRAG is an online operation. REINDEX locks the tables and your users can't access them.

-SQLBill

We need more information from you.

1. As Steve asked, did you first restore the FULL backup using WITH NORECOVERY?

2. Are you trying to restore the DIFFERENTIAL right after you already...

Not with SQL Server (yet), but had a most embarrassing moment on Oracle.

We were having a database system built and I was supposed to be the DBA (I had programming...

Also, yes you are correct that Amit's directions are for a database that is attached and in suspect mode. So it won't work for you until you get your database...

At this point, I think you are going to have to restore from your backups. (You DO have backups, don't you?) It looks like one or more of your...

You can have 32,767 databases. So, 1075 isn't maxed out. However, it's still a lot of databases and if all of them are being used at the same time, or...

There IS a transaction log...SQL Server doesn't work without one per database. That's what the .ldf file is. You apparently aren't doing transacation log BACKUPs. And yes, you...

As Balmukund asked, are you doing log backups?

Also, what are your users doing on the database? Some transactions use TEMPDB and will cause it to grow. Are they creating...

Are you sure it's backing up what you expect it to be backing up? Maybe it's missing something.

-SQLBill

Another possible problem....#tablename creates a LOCAL temporary table. ##tablename creates a GLOBAL temporary table. You could be having a problem with your temporary table being out of 'scope'.

Try changing it...

It looks like the frog that I accidentally ran over one day.

-SQLBill

One thing to look into is permissions. When you run a command manually, it is running using your login. When you run it as a job, it is running with...

I believe the issue is:

The code really isn't running on your machine. It runs on the server and returns the result to your machine. So, debugger can't step through it...