It is weird.

But if you have a trouble to uninstall CU1 from SQL Server Tools and Workstation Components, you may want to uninstall SQL Server Tools and Workstation Components completely,...

You may also want to change :

1. Number and size your Tempdb data files

2. Default location of User databases

3. Enabled network protocols

4. TCP/IP default port number

Marcin Gol [SQL Server MVP] (10/4/2009)

---

after Kimberly Trip:

1) SQL 2000 - #tempdb files = #logical cpus

2) SQL2005+ - #tempdb files = 1/4 ~ 1/2 #logical cpus (typically not more then...

There is not enough information to help you.

You may want to do some modifications in your job to provide more info.

Click on edit your job step, click the advance tab......

As was mentioned you can use ApexSQL Recover tool, which was specifically designed to recover a lost data due to DELETE, TRUNCATE, DROP operations.

http://www.apexsql.com/sql_tools_recover.asp

Marcin Gol [SQL Server MVP] (10/4/2009)

---

Sergey Vavinskiy (10/2/2009)

---

Tables and their related indexes should be separated onto separate files and physical disks for optimum performance running queries, but not separate filegroups....

I forgot to say you have to grab this script and run it on a new server, and all of your scripted SPs will be transferred to the new server.:-)

The Grant's way it the right way.

But as a fast an durty solution you can just...

Tables and their related indexes should be separated onto separate files and physical disks for optimum performance running queries, but not separate filegroups. If they are in separate filegroups, then...

SQLAgentOperatorRole members can enable or disable schedules they do not own by using the stored procedure sp_update_schedule and specifying values for the @enabled and the @schedule_id (or @name) parameters.

There is no the Enterprise Manager in SS2008 since SS2005.

There is a SQL Server Management Studio (SSMS) instead.

Here is how to use it:

http://msdn.microsoft.com/en-us/library/ms174173.aspx

Put a database in a ReadOnly mode.:-)

You may also want to check syntax of your view definition and see if it still compatible with SS2005 - there were several syntax discontinuation there.

As I said use a SQLAgentOperatorRole (msdb fixed database role) if you need your user working on all jobs, created by any user.

Look at this:

http://msdn.microsoft.com/en-us/library/ms188283(SQL.90).aspx

You need also to script and transfer all database related jobs, SSIS packages, operators, and alerts.

All of this things are server level objects and will not transfer with database backup/restore.