First shrink the database to release the space for Operating System at free work hours and truncate the size of log ,then this process will release the unallocated space

Shrink Database...

have you defined AWE in SQL server ?

Check this query for the missing Indexes on the primary Server as well as secondary Server on the specific database

Select * from sys.dm_db_missing_index_details

How much RAM have you allocated for the...

First will tell you about the missing indexes on the database and the other one will tell you about resources usage of queries,locks,wait etc,these queries are not harmfull just execute...

Go to SQL Server Configuration Manager then check all protocol are enabled on the instance side as well as native client side as mention in the figure

Create all non-clustered index scripts and then drop it all then create clustered index then create non-clustered index after clustered index

Note It when we create clustered index then non-clustered automatically...

Data Type of ID column is ?

If you dont want to require an audit and specific user actions then create SQL server role for the specific group as SALES and create sales user and assign this...

Did you define the PAD_INDEX option ON and fillfactor same as before ? what is the Server default fillfactor configurations ?

check the default configurations of the Server or fillfactor by...

Note it when you create the Cluster index then non-clustered index on the same table will be drop and then recreate autmatically

It depends on the query you have provide if...

When your logshipping fail and you want to up the secondary node then you will pass this statement on the secondary node

Restore database [your database name] with recovery;

If database have...

check with

SP_WHO2

check with also

Select st.text,sp.* from sys.sysprocesses sp

cross apply sys.dm_exec_sql_text(sp.sql_handle) st

where sp.status != 'sleeping'

order by sp.cpu desc

paste your sp on the query analyzer on SSMS and then click on...

Install Express Edition of SQL Server 2008 instead of SQL Server 2000 and test replication on it if problem still there then we can provide solution

because your SP is using multiple queries in it,it tells you statistic for every query

sys.databases is a new catalogview and sys.sysdatabases is for backward compatibility for SQL Server 2000 and this will be remove in the future release