AirWolf
Honorary Master
How important is it to have MSSQL installed on each pc on a network?
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Did you buy your last car with cash or on a finance plan?
MSSQL - how important on a network?
- Thread starter AirWolf
- Start date
It depends on what the users are doing on the network? I mean it would be pointless in a school situation, or in pretty much every situation except, possibly, the situation in which you find yourself.
More details would help.
More details would help.
stoke
Honorary Master
If your network is unstable (Down for 20% of the time), then well .. it may be the better option to store the data locally. But, just trying to backup that stored data will be a nightmare.
I'm confused.... as in Microsoft SQL? If thats the case, and you want to have it on each PC, you must have a fortune to spend on licenses.
AirWolf
Honorary Master
I downloaded the 2005 Express edition from the Microsoft website for free.
AirWolf
Honorary Master
Imminent VIP payroll installation to be used by various pcs on the network off the server.
If the software itself requires MSSQL as a dependency, then yes it is quite likely you will need to install it on each PC. Unless it is possible to have the software access the database over the network, in which case you could just install it on a main server.
diabolus
Executive Member
I'm also confused? My understanding of "MSSQL"- software is that it's a -server- . The only MSSQL client stuff i'm aware of is the Query Tools [i.e. to connect to a -server- and run your own queries..this is primarily a developer thing.] and maybe drivers [which usually comes with Windows anyway, i.e. ODBC/OLEDB]
You usually have an application or website that does the queries on the server , and all you then need is that app/access to the site.
So what exactly is it you want to install on every pc? A SQL database server? What for? If you have a little app that uses a database -locally only- then i would seriously consider a redesign and using a more portable database technology [it's kinda overkill to have to install a SQL Server Instance on your own pc to run an app only you will use personally...this is where MS Access usually shines] . If it's a app many people will use together, then again, you -should- only install it on one server-like pc. If everyone connects to their own little db, then the data will never be in sync/integrated.
You usually have an application or website that does the queries on the server , and all you then need is that app/access to the site.
So what exactly is it you want to install on every pc? A SQL database server? What for? If you have a little app that uses a database -locally only- then i would seriously consider a redesign and using a more portable database technology [it's kinda overkill to have to install a SQL Server Instance on your own pc to run an app only you will use personally...this is where MS Access usually shines] . If it's a app many people will use together, then again, you -should- only install it on one server-like pc. If everyone connects to their own little db, then the data will never be in sync/integrated.
Last edited:
What type of interface
If memory serves me correctly then VIP has a browser interface which means that all database communication is done at the server level. I don't think you would need a database per machine in a worst case scenario you may require a database client per machine although this architecture is seldom implemented today.
Hope that helps
If memory serves me correctly then VIP has a browser interface which means that all database communication is done at the server level. I don't think you would need a database per machine in a worst case scenario you may require a database client per machine although this architecture is seldom implemented today.
Hope that helps
diabolus
Executive Member
Saule said:
That's still a server-client thing. You can only have 1 server [where all the data goes] and lots of clients who inserts/change the data. OBviously VIP is the 'interface" users will use, it's suppose to handle the "MSSQL" stuff itself [no need to install anything else].
You obviously then need a SQL Server [or whatever VIP uses] on one big pc which everyone connects to....
If VIP uses a local db on every client which then sync to a central db..then suck for you for using that payroll system. That can be a real pain to maintain and data disappearing on the local pc....[it's a nice backup/offline mode thing, but sometimes you really don't want people working "offline" on mission critical data for extended periods...that's how you corrupt data].
Last edited:
Yes i think someone is using the incorrect terminology!
Microsoft SQL Server (Yes, even the Express edition) is Server Software... A Network Database.
But you get another little MS Database app, known as MSDE, Microsoft Desktop Engine. now i know that a few Accounting packages need this running locally to work properly?
So maybe thats what you mean? coz if you have SQL Server on each PC... you'll need to set up Replication...(not sure if you can replicate from many-to-one) otherwise reporting/getting the data you need will be a nightmare??
Microsoft SQL Server (Yes, even the Express edition) is Server Software... A Network Database.
But you get another little MS Database app, known as MSDE, Microsoft Desktop Engine. now i know that a few Accounting packages need this running locally to work properly?
So maybe thats what you mean? coz if you have SQL Server on each PC... you'll need to set up Replication...(not sure if you can replicate from many-to-one) otherwise reporting/getting the data you need will be a nightmare??