Ruchika,

Hav you gone thru this link:-

http://www.developersdex.com/sql/message.asp?p=1870&r=4699024&page=2

Manu

Try running DBCC CHECKDB ('CLICK_ETL', repair_rebuild) in query analyzer and check for errors or if it is scheduled as an job then specify job log file and check that file...

Have you tried Deepak's suggestion?

Manu

Can you please specify the sql server edition. Also, the complete error message.

Manu

You will have to take the downtime. I don't think there is any other way of doing it.

The one available is the same what is done in background by sql...

That might had happened step by step. Is autoshrink ON for this database?

Manu

Did you go thru the following link:-

http://msdn.microsoft.com/en-us/library/ms189307.aspx

Alos, check it once(http://sqladvice.com/blogs/repeatableread/archive/2005/03/04/4262.aspx)

To force a connection to use Named-Pipes, just append np: before the name of your server. Examples...

Jeff is right you need to execute DBCC UPDATEUSAGE('Database Name') with count_rows so that you can rely on sysindexes results.

Manu

Is there only one sql server instance running on this machine? If there are more than one instances then you need to find the instance consuming most of the memory....

Do you have any other windows account having sysadmin privileges on this installation?

Manu

dbcc sqlperf(logspace)--Log file size

select object_name(id) as Table_name, rowcnt [RowCount] from sysindexes where indid in (0,1)--Rowcount

You can use sp_helpfile for listing the database file size specifications.

Manu

Hope you find this useful:

http://www.sqlservercentral.com/Forums/Topic187917-5-1.aspx#bm200951

Manu

I think thts only possible with 2005.

In 2000 as per books online:

ALTER PROCEDURE permissions default to members of the sysadmin fixed server role, and the db_owner and db_ddladmin fixed...

Hope this helps:

http://www.sqlmag.com/Article/ArticleID/95728/sql_server_95728.html

Manu

No worries if msdb database size is under control. I think somebody didn't check the deleting backup and history option while dropping

database from enterprise manager.

Manu Jaidka