Hello,

There are some commands you cannot run from an SQL Server job because there is no console, for the example write-host cmdlet.

http://blogs.msdn.com/b/mwories/archive/2009/09/30/the-use-of-write-host-and-sql-server-agent-powershell-job-steps.aspx

Hope this helps.

Regards.

Victor.

Hello Gail,

Sorry if I didn't write properly in my post. I understood your idea, and I agree with you.

Thanks for the backups information, I will check those counters to see...

Hi Jeff, thanks for replies.

I understood what Gail recommend about rebuilding indexes followed by a shrink. But I wanted to you know your

opinion about running them separately.

Summing: Never run shrink,...

Thanks Gail and Perry for your postings

Gail: I think that I have a problem with the full backups because the backup process used to take between 45 and 60 minutes.Now,...

Hi, Thanks again for post.

I have a transaction log backup every one hour.

I have the following idea, please let me know if I'm wrong:

The transaction log backup backups the...

Hi, thanks for your quick response.

I agree with you regarding fragmentation generated, also with that transactions will be slower while the file is growing.

I am shrinking the files, because I...

Hi,

http://www.microsoft.com/sql/solutions/upgrade/default.mspx

You can download the Upgrade Advisor and some useful documents from this link.

Hope this helps

hello,

There are two migration strategies:

In-place Upgrade: where the SQL Server 2005 installation overwrites the old instance of SQL Server.

Side-by-side Upgrade: the migration takes place in the different SQL Server instances.

Visit...

Now, I have a maintenance plan that rebuild the indexes, so if the rebuild process update the stats with full scan, there is no need to run the sp_updatestats

Thanks

Hi, thanks for your reply.

I have many tables with auto stats activated

Maybe I should do the following:

1)Disable autostats.

2)rebuild indexes once time

3)Schedule a weekly job that update statistics with full scan.

What...