create table #spacedetails (name varchar(100),totrows bigint,reserved varchar(30), data varchar(30),index_size varchar(30), unused varchar(30))

insert into #spacedetails

exec sp_MSForeachtable @command1 = "sp_spaceused '?'"

select name,totrows, replace(data,'KB','') as 'Data in KB',

replace(Index_Size,'KB','') as 'Index Size in KB' ...

Restore the full database backup that was taken before jun 10th. Then if you have any differentials backup restore the same. else restore the log back point in time to...

Your i/o read will be faster moreover placing tables that are joined together in different filegroups will enhance performance of your query.

You can use opedatasource to read from your excel sheet and insert into your sql server.

Change the compatability level. But remember that some TSQL commands are not supported in level 90. check for this site to find the desupported. Then its better that you update...

You can wait for few days. Might be to get updated stats and few more. But this should never be a problem with restoration. Did u change the compatability level.

The maintenance plan would have created a job. Take the syntax of the job step and try running in the query analyzer and let us know if you still face...

you have to give permission for the user account starting sql server services. have you did that?

no way unless you have auditing aenabled and use a profiler to find that data.

Unfortunate you cant resotre a backup from sql 2005 to sql 2000. its not supported.

select databasepropertyex(databasename,recovery)

should be ok for ur req.

Please check this.

1. Type secpol.msc from run prompt

2. Navigate to user rights assignment

3. you will see a list of permissions in the right hand side

4. check for lock pages...

Check if you have enabled remote connections. By the way are you trying to do an edition upgrade. Let me know the reason why u are using an upgrade advisor...

I am not sure if any object already altered can be traced. You can trace current activity in the server using sysprocesses table and manipulating against it. but if someone...

Check if you can use the script in the given in the URL mentioned below.

http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=486