String Concatenating on SQL server vs front end

rudeboymcc

Registered User.
Local time
Today, 11:17
Joined
Sep 9, 2008
Messages
69
Hi. I have an Access 2007 database with lots of passthrough queries that go to SQL server, such as Views etc .

One View set up on the server for example, returns a list of house addresses in two formats, one for a mail address:
1 The avenue
London

and one for a list of properties:
The Avenue, 1, London

At the moment both of these strings are being created on the sql server and being passed ot access as separate columns.

Ive just realised that i've effectively doubled the amount of traffic going over the network.

Is it good practise to pass all the separate columns (Address, Number, and City) to Access, and let the front end do the stirng concatenations? This is working over VPN so network bandwidth is limited.
 
Is it good practise to pass all the separate columns (Address, Number, and City) to Access, and let the front end do the stirng concatenations? This is working over VPN so network bandwidth is limited.
It makes more sense to do so. There might be times where you need to do more with the raw fields so passing the raw data is more beneficial.
 

Users who are viewing this thread

Back
Top Bottom