The Current Server Time is: 10:17:58 AM.  There must be a relationship with Microsoft.  Always late releasing.

Anytime....  I am waiting in suspense here.  I hope this is good news.

I couldn't figure out a way to do this without an identity, but here are my results

create table #t (ids int identity(1,1), value int)

insert into #t

select 1

union all

select 1

union all

select...

One more question, are there different indexing strategies with Replication?  I have done replication long ago, and I don't remember needing to care about the indexing strategies. 

Greg

For Transactional Replication, does a Clustered Index need to be on a Unique Column or can I choose any column for the Clustered Index?  I am trying to find anything...

Thanks Remi for your position criticism.  Kinda remind of Celko.

First of all, you are correct with the temp table.  I use a similar method to auto create a table so...

What about something like this?

declare @STR varchar(2000)

set @STR = ''

select @STR = @STR + '''' + c.name + ''' as ' +...

You can also use the convert with a style.  If you want to store this as a YYYYMMDD, the column needs to be varchar.  This shows the type of column...

My two cents.  Earlier in the thread I noticed that someone said something in regards to upgrading the server.  Make sure that your server can be expanded.  The L2 Cache...

One thing that can be done is a "SELECT... INTO..."  You would need to make sure that you dropped the table when finished as you cannot create a table with...

I think I read that a little too quick.  I must have read that as 100%, 0 Sec. as 0% 100 Sec.  I know that the time MS produces is...

It is Microsoft!  Can you ever rely on anything they produce that determines length of time?  I would say, NO.  You can't follow the seconds for the Kill.  Have you...

I don't know your environment and haven't seen this before.  But here are my two cents.  If you run, check SYSPROCESSES for spid 60, do you see multiple rows returned. ...

It is an exclusive (X) table (TAB) lock.  This means, that a transaction has occured; INSERT, UPDATE, DELETE on a table the the stored procedure is referencing.  If you run kill...

You data probably has multiple rows that have the same counts of "OP."  change the "=" sign to "IN".

Thanks

Greg