If I understand correctly, you need to get the locale information from the local user (ie on the client computer) and pass it to SQL Server for it to be...

Nigel

I think I understand what is required - the data is grouped according to common headers such as "2...

I think your requirement would best be fulfilled in your presentation layer rather than in the data layer. I would recommend Reporting Services for presenting data in this format.

John

The easiest way to improve performance would be not to insert Inserted and Deleted into a temp table. There doesn't appear to be any value in doing that, so...

If the job has never run then there won't be an entry for it in sysjob history. You will need to change your logic so that it looks through...

http://www.lmgtfy.com/?q=CREATE+FILEGROUP

Denesh

There isn't any way of knowing, unless the update statement was king enough to include a GETDATE() value! You could trace all activity using a server-side trace in case...

Lior

Try this, then. Looks like it might be a good idea to reconsider your database design, as well.

SELECT

A.ID

, COALESCE(B1.ActualName,A.FakeName1) AS Name1...

Lior

Something like this? (Not tested because you haven't supplied any DDL or sample data.)

SELECT

A.ID

, COALESCE(b.ActualName,A.FakeName1) AS Name1

, COALESCE(b.ActualName,A.FakeName2) AS Name2

, ...

Kit G (8/25/2010)

---

5 pages of discussion, but no answer to the question asked a few times. Does SQL 2008 handle NULLs differently from SQL 2005 or SQL 2000? ...

Francisco

I'm not sure I agree with you on that - if you have an operation that can be done on 100 rows at once then that's going to be more...

Ah yes, the OLE DB Command transformation. I don't use this for the very reason you mentioned - it acts on each row individually and therefore isn't very efficient....

Francisco

I'm not aware of an Execute OLEDB task. Are you referring to the OLE DB Source? If so, what happens if you choose the SQL command data access...

You don't need to convert at all. Just datefield BETWEEN date1 AND date2 will do. That alone will probably speed up your query a bit. I'm afraid...

Why are you converting datefield into varchar and then back into smalldatetime? What are date1 and date2 and what data type are they? This is why we need...