E
er slansky
I have no experience w/TS except for occasional connections at my main
workplace. As a side job, I inherited an Access 2k app used by a
small lab that I am converting to SQL Server 2k - it is just getting
too big with patient history and will only continue to grow. The new
front-end will be VB.net.
This lab uses XP boxes but connect to the Access app on Windows 2k via
Terminal Services; they say the performance is much faster because
they are directly on the server vs. passing data back and forth over
the network if they used individual copies of the Access program on
their desktops.
When moved to SQL Server, they want the same type of set-up. I'm
trying to convince them that SQL Server and Terminal Services should
be on different boxes. I can see maybe using Terminal Services to
connect to the front-end app, avoiding having to push it to the
individual XP boxes. But I'm thinking that just by going to SQL
Server, performance is going to improve anyway without having to use
Terminal Services.
Can anyone point me to something that would back me up on keeping SQL
Server and Terminal Services separate? And does anyone know how their
using Terminal Services would affect my VB.Net code? Design of the
database??
My experience is only with large employers who have several thousand
employees - I haven't really had to worry about how things are set up
as those decisions were already made.
Thanks for any advice or pointers,
ER Slansky
workplace. As a side job, I inherited an Access 2k app used by a
small lab that I am converting to SQL Server 2k - it is just getting
too big with patient history and will only continue to grow. The new
front-end will be VB.net.
This lab uses XP boxes but connect to the Access app on Windows 2k via
Terminal Services; they say the performance is much faster because
they are directly on the server vs. passing data back and forth over
the network if they used individual copies of the Access program on
their desktops.
When moved to SQL Server, they want the same type of set-up. I'm
trying to convince them that SQL Server and Terminal Services should
be on different boxes. I can see maybe using Terminal Services to
connect to the front-end app, avoiding having to push it to the
individual XP boxes. But I'm thinking that just by going to SQL
Server, performance is going to improve anyway without having to use
Terminal Services.
Can anyone point me to something that would back me up on keeping SQL
Server and Terminal Services separate? And does anyone know how their
using Terminal Services would affect my VB.Net code? Design of the
database??
My experience is only with large employers who have several thousand
employees - I haven't really had to worry about how things are set up
as those decisions were already made.
Thanks for any advice or pointers,
ER Slansky