Select ISNULL(FirstName + ' ', '') + ISNULL(middlename + ' ', '') + ISNULL(lastname + ' ', '') + ISNULL(suffix, '') as FullName from dbo.Contacts

Forgot to mention this... the first query will run faster (once fixed) because AS400 will be filtering out the results using its own indexes instead of sending out a few...

That was my point .

The most likely explanation is that AS400 doesn't understand exactly what you want to filter in the where condition. ...

I just moved the exists to eliminate the @JobsDB variable

IF EXISTS (SELECT * FROM sysobjects WHERE name = 'Configure' AND XType = 'U')

begin

select * from Employees inner join CTJobs.DBO.Jobs Jobs...

I've never used more than 10 parameters in my progs (almost all queries are done by access in adps).. I can't imagine using more than 25-100 parameters in a sp.

This is the way to change collation in a query.

Note that you can also change it in the table definition, but that would obviously change every query that touches the...

this is more a flow job than sql job...

if I got your requirements right I would do this :

if @JobsDB = 1

begin

select * from Employees inner join CTJobs.DBO.Jobs...

I would use this as a last resort as sql server would input the full table before applying the where condition.

The go keyword tells sqlserver to end this batch and start a new one. Even if the return keyword is executed (don't know where it would return to... but...

Actually I redid some test and it turns out that pw's solution is better than mine :

Substring(name, 3, 999) seems to be a tad faster than right(UserField1, len(UserField1) -...

Update d_details

set UserField1 = 'efgh' + right(UserField1, len(UserField1) - 4)

where left(UserField1, 4) = 'abcd'

I'm using len(UserField1) - 4 in case the field can be more than 8 chars (can be...

I don't know if you misunderstood, but the results you are getting are correct. The post is about shorcircuiting the or operator. Like in my previous post, when...

It will exit after the first hit.

Select * from dbo.SysObjects WHERE

1 > 0

OR

--this is shortcircuited

1/0 > 0--should throw an error

Complete article on WindowsItPro

You can't use another table unless you're inside the udf or inside a trigger. Maybe you could send the parameters needed to calculate the first field in the 2nd...

You'll have to run a trace and scan for the alter procedure text in it.