Use this to see if the server can see the file on the network :

Declare @out int

EXEC master.dbo.xp_fileexist 'C:\demo.notexists', @out output

SELECT @out

EXEC master.dbo.xp_fileexist 'C:\AUTOEXEC.BAT', @out output

SELECT @out

replace the autoexec...

Current salary : 1800$ / week (40 Hours)

Current living expenses 2500$ - 3000$ / month

Do you (and the server) and read access to that file on the remote server?

Well I'm only 1600 $ short on my end.  I could settle for 1000 US / day for the moment .

What's that in US dollars?

I'm not sure of the conversion but it seems like a salary I would enjoy .

Good, keep it that way.  Now you also know that there are a few exceptions to that rule (very few).

I'm sure you can provide quite a few exemples of useless tools or consultants without knowing or getting there rates...  How about you send us a few?

Ya but then they come back ehre and ask a question where all we can say is here use this 600 line query or redesign the system and use this...

Next time you go to walmart, imagine trying to find anything if everything was put in a single pile of stuff in the middle of the store.

That's what's going on...

The more important point is that the correct design calls for at least 4-5 tables with 2-3 columns each.  Not 1 table with 125 columns.

Well where I'm stuck at is where have they decided that they can't have more than x scans per sec??

Anyways I've always approached and seen approached performaace tuning by finding...

GROUP BY ALL is being depreciated.  The left join from a calendar table is the safest solution.

May I ask why you think you need to change this one metric?

Do you really need to change the base table data?

You can simply select the data and present it in a different way.

If you were to choose to update the data...

Basically what you have to do is use the system tables to list all of the columns from each table.  Then dynamically build a string that will list all search...