Combining a Line Graph and Scatter Graph

I have to make a report of a combination of salary trends of
employees. The idea is to show the salary of a employee for a certain
period of time, also showing where he stands when he compared to
salaries of other employees.
I will show the salary of the employee in a line Graph, thats fine I
have already done it. X axis -> Employment Time, Y-axis Salary The
qquery will be like
userid, date, salary
72, 01/01/2001, 1000
72, 06/01/2001, 1600
72, 01/01/2002, 6000
72, 06/01/2002, 7080
72, 01/01/2003, 8010
72, 06/01/2003, 10000
72, 01/01/2004, 10050
72, 06/01/2004, 15500
salary in the Values section
date in the Category Section
The Line Graph is done.
Assuming I have the same query with more userid values (For other
employees also). I have to plot scatter points around the Line Graph
showing the salaries of each other employee as against the employee
72.
So the Graph will have 1 line for userid 72, scatter points around
that line.
How can I do it. Working Ideas please.
Thanks !
Anand Sagar
Now I have to show scatter pointsanybody there !?

Column name with period

I heard a rumour that column names with a period "." in
the name had a negative affect on performance.
I haven't yet managed to find proof of this but was told
that someone found an article suggesting that it does.
If anyone knows of this could they please post a link or
explain?I couldn't find any collation with a period in the name:
select * from ::fn_helpcollations() where name like '%.%'
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Willem" <anonymous@.discussions.microsoft.com> wrote in message
news:1575001c41631$2c2d2060$a501280a@.phx
.gbl...
> I heard a rumour that column names with a period "." in
> the name had a negative affect on performance.
> I haven't yet managed to find proof of this but was told
> that someone found an article suggesting that it does.
> If anyone knows of this could they please post a link or
> explain?
>|||Tibor,
Go and visit your optician! ;-) The OP said column, not collation!
Mark Allison, SQL Server MVP
http://www.markallison.co.uk|||Willem,
I don't know whether it would affect performance or not but it is not "best
practise" to have non alphanumeric characters in column names. You are expos
ing yourself to bugs by doing this. I know that you can use square brackets
but in some situations you
may find yourself hitting a bug or two. I would rename the column in the nex
t release of your application, if possible.
There may be a performance hit, but I doubt you would notice it.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk|||> Go and visit your optician! ;-) The OP said column, not collation!
LOL... Thanks Mark :-)
Willem,
I have not heard anything to the effect that SQL Server should treat columns
differently in any way based on
the name of the column. Of course, using a period makes the name a non-stand
ard identifier and you will have
to handle that in every query you issue against that column. I never divert
from standard identifiers myself.
I have written code against databases which required me to use delimited ide
ntifiers, no fun...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:71883438-B332-4E1D-92B7-E0F8B6AA8962@.microsoft.com...
> Tibor,
> Go and visit your optician! ;-) The OP said column, not collation!
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk|||Thanks for the feedback.

>--Original Message--
>Willem,
>I don't know whether it would affect performance or not
but it is not "best practise" to have non alphanumeric
characters in column names. You are exposing yourself to
bugs by doing this. I know that you can use square
brackets but in some situations you may find yourself
hitting a bug or two. I would rename the column in the
next release of your application, if possible.
>There may be a performance hit, but I doubt you would
notice it.
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>.
>|||Great, thanks.

>--Original Message--
not collation!
>LOL... Thanks Mark :-)
>
>Willem,
>I have not heard anything to the effect that SQL Server
should treat columns differently in any way based on
>the name of the column. Of course, using a period makes
the name a non-standard identifier and you will have
>to handle that in every query you issue against that
column. I never divert from standard identifiers myself.
>I have written code against databases which required me
to use delimited identifiers, no fun...
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>
>"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in
message
>news:71883438-B332-4E1D-92B7-
E0F8B6AA8962@.microsoft.com...
not collation!
>
>.
>