General discussion

Locked

SQL server questions

By IT Support Services Manager ·
We are considering purchasing SQL Server to run an SQL version of a program over a long distance. We need this program to be available on our campus and to people in our town and in the town 40 miles away. This program will be accesses in each town in the high schools and so they will not be members of our domain or our network. Unfortunatly, the program is not Internet ready. Has anyone done this before? What types of problems do we need to look out for? What is the easiest way to setup this type of situation?

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

SQL server questions

by MtnSqs In reply to SQL server questions

SQL server can be connected to over a WAN or dail up access in many ways - it really depends on what the program has been set up to support.
If you use Named Pipes, then the current user logon can be used (SQl server has to be setup to use NT logon) and you will have little maintenance work but less security - i.e. anybody logged onto the system will get access and you ahve to do a lot of work to limit their access to the specific tables in the database.

You can set SQL server upt o use aspecific logon - the only probelm here is taht you have to setup every user in the SQL serve and maintin them.

I prefer the latter for security purposes escpecially if only some users are to have access to the the Db. You can consider generic tpye users - eg one for read only type access which would hoperfully support most of your users.

Collapse -

SQL server questions

by IT Support Services Manager In reply to SQL server questions

Poster rated this answer

Collapse -

SQL server questions

by allan In reply to SQL server questions

Install the SQL client software (run server setup on a workstation and will tell you that it will only install client) Then setup ODBC Connection to the DB.
You can set up the connection to use a single generic login like User: Guest
Password: Guest and everyone will access using this account (works great if the application has it's own security)or you can
set user IDs and passwords for each person individually.

Collapse -

SQL server questions

by IT Support Services Manager In reply to SQL server questions

Poster rated this answer

Collapse -

SQL server questions

by IT Support Services Manager In reply to SQL server questions

This question was closed by the author

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums