koteswara kishore K. (3/11/2008)

---

but my staements "create table ...." and "Select ...." are in same procedure.

in 1st procedure sends 'Create table....' script to 2nd procedure.

these 2 staments are executing...

As an aside, this is the T-SQL 2005 forum. Your question might fit better in either the SQL 2000 DTS forum (since you say it's DTS), or the SQL...

You can query the spreadsheet as if it were a table and use a Where statement in that. "Where [col 1] is not null" should do the trick for...

Unless query 1 calls query 2 directly, temp tables created in query 1 are not accessible to query 2. Look up temp tables in Books Online and it will...

ScottPletcher (3/10/2008)

---

Wouldn't L.A. fall under CA...

Vivien Xing (3/10/2008)

---

A good question.

What is the difference between 8 and 9?

8 Password mismatch

9 ...

Lynn Pettis (3/10/2008)

---

The people you know who celebrate their birthdays on Feb 28 on non-leap years, doesn't mean the state or country they live in says they are another year...

ScottPletcher (3/10/2008)

---

But even your own "timeanddate.com" link makes it clear that the official birthdate is Mar 1 in non-leap years:

while others celebrate their birthday on March 1 because they...

Lynn and Hugo:

I took Leap Years into account, and even (to be totally anal retentive about it), the hour, minute, second, and number of milliseconds, on each time.

Maybe I'm operating...

molecule_kaab (3/10/2008)

---

Thanks, all

Actually I want to keep track for security and navigation

I want the admin can tell who do what transaction and

he can find that it's possible that the...

I just tested all three proposed functions, using my own date of birth, and it got the answer wrong in all three cases. I copied and pasted them into...

paulhunter (3/5/2008)

---

I...

I don't think I've ever used this syntax:

@StepDescription = upper(coalesce(@StepDescription, StepDescription)),

@PrevailingWage = coalesce(@PrevailingWage, PrevailingWage),

@StepStandard = coalesce(@StepStandard, StepStandard),

@GuaranteedStepWage = coalesce(@GuaranteedStepWage, GuaranteedStepWage),

@MinimumWageCap = coalesce(@MinimumWageCap, MinimumWageCap)

I would use:

StepDescription = upper(coalesce(@StepDescription, StepDescription)),

PrevailingWage = coalesce(@PrevailingWage,...

A table-value UDF (not an inline scalar UDF) would probably be a good way to go on that.

In the tests I did, the XML method was slightly faster, but required less scans and reads from disk/cache. Speed differences, in many cases, were as few as 1...