nairsanthu1977,

What you're seeing are the tasks available for a maintenance plan package. You have to use BIDS to create any other SSIS package.

http://technet.microsoft.com/en-us/library/ms139805(SQL.90).aspx

http://www.mssqltips.com/tip.asp?tip=1180

You could also describe the problem you had previously and maybe someone will be able to help.

This is one of the reasons we decided not to store packages in msdb anymore like we did with DTS packages.

day, I don't think you'd have to recreate the job....

SQL Server 2005 editions that include SSIS are Enterprise, Standard, and Workgroup.

This works. It's in the script section SSC - http://www.sqlservercentral.com/scripts/Miscellaneous/30755/

If you have any database that still has the default database roles, you can script them in SQL Server Management Studio and run the script in the database in question....

If you want to rename the existing default instance, you must run these stored procedures then restart the instance:

sp_dropserver

GO

sp_addserver , local

GO

See BOL: ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/bbaf1445-b8a2-4ebf-babe-17d8cf20b037.htm

I don't know of a built-in way to do that but I've watched a demo of a product that Brian Knight has developed that claims to migrate all the packages...

From BOL:

How to save row values into global variables (Enterprise Manager)

To save row values into global variables

From the Connection toolbar, drag a Microsoft® OLE DB Provider for SQL...

This lists permissions in every database in an instance.

--Lists a user's object permissions in every database. Specify the user name.

sp_MSforeachdb 'use ? Print DB_Name() select cast(o.name as...

Are you specifying the correct value for the TextData column in the WHERE clause?

Try adding a global variable to the package then setting it to @@ROWCOUNT in the Execute SQL task. You could then write that out to a table or file.

Master uses the simple recovery model by default and, even if you change the recovery model, you can't take or restore log backkups. See this in KB:

http://support.microsoft.com/kb/285288/en-us?FR=1

I'm not sure why you posted this in the Backups forum, but there is not limit on the number of rows in a table. It's only limited by the...

FYI: There's a new version of Upgrade Advisor that works with SQL 2000 and SQL 2005. Maybe it would work on version 80 databases in a SQL 2005 instance....