No matter what you do the time factor is too large.

Sorry, but I don't know of any job scheduler that is capable of starting at the nano second level.

Given the...

And one reason that it might appear to be phantom is the schema. If it is owned by something other than dbo, it might not show up if just...

This will check all databases

EXEC sp_MSforeachdb 'USE ?;SELECT ''?'' as dbname,* FROM sys.all_objects WHERE NAME LIKE ''%cycle%'''

DECLARE @bob-2 VARCHAR(200)

SELECT @bob-2 = 'robert'

SELECT UPPER(SUBSTRING(@bob,1,1)) + LOWER(SUBSTRING(@bob,2,LEN(@bob)))

SELECT @bob-2 = 'ROBERT'

SELECT UPPER(SUBSTRING(@bob,1,1)) + LOWER(SUBSTRING(@bob,2,LEN(@bob)))

What fun.

I have worked with both pretty extensively now, but for the past year, it has been almost exclusively SQL Server. Before that it was about 15 years of...

Got the message about there being 39 possible deductions. FYI, I don't mind you sending me stuff that you don't want to post, but I do want to keep...

Here is the same example using a CASE/Group by rather than the pivot.

SELECT t1_id,

MAX(CASE WHEN RN = 1 THEN deduction END) AS Deduction1,

...

You sent me 4 queries which all could be represented by a view/table where the PK is Empl_ID (Except Deductions)

From your comments You didn't appear to have issue with the...

Trying to figure out why I wasn't seeing the dups. Not the pivot, the test table

IF(OBJECT_ID('tempdb..#t1') IS NOT NULL) DROP TABLE #t1

IF(OBJECT_ID('tempdb..#t2') IS NOT NULL) DROP TABLE #t2

CREATE...

This can also be done with a series of case/group by statements. The pivot however is designed for this situation.

It's not that I don't want to help you with...

Based upon what you sent me, I think this is now what you are looking for.

IF(OBJECT_ID('tempdb..#t1') IS NOT NULL) DROP TABLE #t1

IF(OBJECT_ID('tempdb..#t2') IS NOT NULL) DROP TABLE #t2

CREATE...

SELECT col1,col2,col3,col4,col5,col6

FROM table1

inner join table2 on table1.personnel_id = table2.personnel_id

Is this what your talking about?

Steve Jones - Editor (11/28/2007)

---

I won't recommend this, but I have worked in places where we've turned off servers to see if we got complaints.

I'd recommend auto close before...

Oh forgot to add.

DO NOT SHRINK YOUR TEMPDB!!!!! this really screws up the whole thing.

There are no good techniques for preliminary sizing of the tempdb. This is because it's usage has almost no correlation with anything else.

The short answer is this....