Perect timing - I hit exactly this yesterday and was hunting round for a solution. It is in fact fully documented in BOL and it describes several options:

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

It...

On the face of it this seems an odd thing to want to do.

No simple way I can think of apart I suppose from creating a string of SQl by...

You are almost there - it should be Set Nocount ON rather than off.

Mike

That is a very big question!

There could be many reasons, but restarting SQL Server is not necessary. My guess would be a combination of poor index choices, or badly written...

Assuming by "odd data" you mean "rows where the value of contactid is an odd number" then something like

select ...

where contactid % 2 = 1

Should do the trick. This...

For that data volume it seems far too slow either way.

Can you post the DDL of both tables, specifically what data type is/are the join columns? What constraints are...

After a machine is renamed you need to get the name SQL server uses consistent.

this can be done with

exec sp_dropserver 'old name'

exec sp_addserver, 'new_name', local

GO

Mike

As far as I know you will need to drop and re-crete the view. I would argue that having the view definition change just because an underlying table has an...

I would reconsider the database design. Storing multiple values comma separated in one column will always give you complexities and goes against one of the basic principles of database design....

I suspect that a trigger has been added to that table, and the trigger either includes a subquery or does not not allow for multiple rows being updated in some...

The simplest would be to remove all the dynamic SQL and just use a simple insert possibly with NULLIFs in ths values clause if the app passes blanks that you...

It is important to realise that apart from a few special cases (such as in a group by) NULL is never considered equal to anything (including another null).

One way round...

Something like

update table

set varcharcolumname = rtrim(varcharcolumname)

where varcharcolumname like '% '

would remove the trailing spaces that are already stored, then repeat for each column you converted. I would then rebuild...

I think the first line of the where clause should probably be using >= rather than = as the conditions as posted are mutually exclusive...

Mike

If possible I would rethink the database design - specifically why have a separate table for each months points?

With the separate table you will need to change the query each...