According to my knowledge if the same partition and directory path exists on the standby server, this is done automatically (i use custom log-shipping under Std edition). See this article...

Could you collect these two counters for sqlserv process: Private Bytes and Working Set? Since from what you posted I believe that the memory allocated to sql server might be...

You can set up a profiler trace, under Database, there are Data File Autogrow and Log File Autogrow events.

Hope this helps.

Some time ago there was a discussion on this site about effects of clustered index rebuild on non-clustered indexes. If I remember correctly, the bottom line was that if the...

See sp_helpdevice entry in BOL for explanation. When I need info on backup devices I query directly sysdevices system table for records with status 16. It's not recommended but works...

check these articles:

http://support.microsoft.com/kb/902388/

http://support.microsoft.com/kb/301292

hope this helps

EMPTYFILE clause can be used only to migrate data within the same filegroup. So you will have to transfer all data stored in your DATA filegroup to PRIMARY filegroup first....

Your problem might lie in huge backup history tables in msdb (backupfile, backupset etc.). Check the sizes and search this site for sp_delete_backuphistory. There are several discussions on this including...

If you use SQL2000, the recovery model is full and there were no log backups between mon full backup and the point of failure, you might see this article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;253817

these steps should help...

Hi I played a little and this could be of some help to you:

select collationproperty ('Compatibility_52_409_30003','CodePage') 'CodePage'

select collationproperty ('Compatibility_52_409_30003','LCID') 'LCID'

select collationproperty ('Compatibility_52_409_30003','ComparisonStyle') 'ComparisonStyle'

by using collationproperty function I was able to...

For the original problem see this thread

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=116255

Unfortunately this deals with user databases.

I don't know any specific ramifications, but I'm sure this is not something I wanted to have...

I would recommend to you reading the following article. Possible causes of your problems could be Lost Write and Stale Read conditions. This article explains how to detect them (usage of sqliostress utility, trace...

You can try this:

declare @reg_srv varchar(256),

        @reg_agent varchar(256)

if serverproperty('instancename') is null

         begin    --default instance

          set @reg_srv='SYSTEM\CurrentControlSet\SERVICES\MSSQLSERVER'

          set @reg_agent='SYSTEM\CurrentControlSet\SERVICES\SQLSERVERAGENT'

         end

         else

          begin   --named instance

          set @reg_srv='SYSTEM\CurrentControlSet\SERVICES\MSSQL$'+cast (serverproperty('instancename') as sysname)

         ...