You have to set up the synchronization of logins, jobs, operators, alerts etc. yourself. The easiest way is creating SSIS packages and schedule them.

With jobs it might als...

Personally with large tables/indexes I always use a procedure which first determines the fragmentation and when depending on the reuslts either does nothing, Reorganize or Rebuild the index.

BOL contains...

Did you have a look at the FOR EACH LOOP container in SSIS ???

It's pretty easy to use. For an example see here http://www.sqlis.com/55.aspx

At my current customer we have RS on a 32-bit machine and the database on a 64-bit server. So far we never had any problems and to be honest I...

About how to loop though all files in directory you find a good example at http://www.sqlis.com/55.aspx.

About writing the filenames to a database simply load the names into a variable and...

There's a very good Whitepaper avilable which should answer all your questions.

http://www.sqlskills.com/resources/Whitepapers/Partitioning%20in%20SQL%20Server%202005%20Beta%20II.htm

That's strange.

Are you sure you gave the domain account exactly the same permissions in the databases than the group? By default only db_owner and sysadmins can execute stored procedures...

I suppose you want to lockout all users execpt the DBA.

ALTER DATABASE myDB

SET RESTRICTED_USER

WITH ROLBACK IMMEDIATE

The last line will rollback all open connections by non admin users. Only sysadmins...

Do you run a reindexing job at midnight? that would explain the growth of the tlog.

I don't think there's any security risk by adding a login for the domain account. The reason why it's recommended to use groups is purely to reduce administrative efforts.

In...

In SQL Configuration Manager set the SQL Agent Service to start automatically. This should resolve your problem.

Id DBCC CHECKDB reports an error the maintenance plan job will show a status failed. The detailed erro message is written to the maintenance plan logfile, at least if you...

Or maybe even more easy, look in the SSMS Schema Change History report.

http://blogs.msdn.com/buckwoody/archive/2008/02/25/sql-server-management-studio-standard-reports-schema-changes-history-databasename.aspx

I wonder if anyone has solved this issue.

KB 941823 is not the solution in my case.

SQLH2 is run under the SQL Server service account. Same for the SQLH2PerfCollector...

With you're unequal comparison the last 3 options will never be reached.

So it also won't go to the ELSE because any value will either be unequal to 1 or...