As Chris already wrote it would help a lot if you posted the schema.

But one thing I noticed is you write, you want to update records, but you execute...

It depends a bit on the size and number of your tables which are out of...

yellow (3/31/2009)

---

I have manually start snapshot agent, and then merger agent. Well, the row numbers are not change at all. It seems the replicating does not working, but no...

Sounds like the dependencies between the cluster resources is not configured correctly.

In the Windows Cluster Admin tool make sure that the SQL Server service depends on both disks. This...

Assuming there's only one occurance of a white space you can use something like this:

SELECT LEFT(Part_ID, CHARINDEX(CHAR(32), Part_ID))

Yes of course.

DB Mirroring is something completly different to clustering and while it's possible to combine them, there's no dependcy between them.

http://technet.microsoft.com/en-us/library/ms189852.aspx

You can add this button (or any other button) by going Tools>Customize. Go to the commands tab, in the categories llst select Window and there you can find the button....

Simply use sp_dropsrvrolemember to remove any login from a serverrole like sysadmin.

EXEC sp_dropsrvrolemember 'yourLogin', 'sysadmin'

With sp_update_Job you can change the owner of a job.

There is no official doumentation from MS.

See here http://sqlblog.com/blogs/andy_leonard/archive/2009/03/11/xp-delete-file.aspx for some unofficial info.

xp_sqlmaint was used by the SQL 2000 maintenance plans.

In 2005 maintenance plans are created as SSIS packages. So instead of using the EXEC T-SQL task use an Integration services...

If you have not auditing triggers or tracefiles, the only option to get all the detailed info would be using some third-party tools to read out your transaction log files...

You can use SELECT in combination with an INSERT only you don't use the VALUES part.

This should work for you:

INSERT INTO [dbo].[b1] ([b1],[b12])

SELECT b2.b1ref, b2.b22

FROM dbo.b2 WHERE dbo.b2.b1ref...

This one is not pretty and there might be some other option is SSIS, but when converting the run_date from SQL server jobs in the msdb..sysjobhistory table, this is...

In SQL2005 or later sysadmins and anyone whith ALTER TRACE permission can use profiler.

In SQL2000 or earlier only sysadmins can run a trace in profiler.

Keep in mind that Indexed views are only supported in the Enterprise Edition of SQL 2000