Help connecting to SQL Server 2005 on DASP from a desktop application

Discussion in 'Databases' started by grgrosso, Dec 13, 2008.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. I would like to create a desktop application (in C# and that will reside on my local machine)that I can use tomanage my DASP SQL Server 2005 database. I have read that WinForm applications are routinely used to do this, and was hoping that someone could please tell me how toconnect a desktop applicationto my DASP SQL Server 2005 database so I can use it to manage the database as required?

    To help explain my intention further, let'sassume thatI have 3 warehouses locatedin different parts of the country (warehouses A, B, and C), and thatall of them need to access and work with the DASP SQL Server 2005 database using a desktop application that would be installed at each of those locations. How wouldthese desktop applications connect to the DASP database?

    Any help would be greatly appreciated - Thanks!

    - George
     
  2. Bruce

    Bruce DiscountASP.NET Staff

    You can technically connect to our SQL server from a remote location. However, remote connection is intended for administrative use only and we cannot guarantee performance nor security.

    Bruce

    DiscountASP.NET
    www.DiscountASP.NET
     
  3. I am sorry I don't really understand your advice. When you say administrative purposes, do you mean altering records,or something else? Also, I really don't understand the security risks of connecting remotely. Could you please explain? Thanks.
     
  4. Bruce

    Bruce DiscountASP.NET Staff

    Remote connection is intended for database administration like creating database objects, indexes.. etc. It is NOT designed for multiple clients to connect to it.

    Security: traffic between your client & database is NOT highly encrypted.

    Bruce

    DiscountASP.NET
    www.DiscountASP.NET
     
  5. I see, and thanks. In my case, I don't foresee the need to transfer any sensitive information from my client (desktop) apps to my DASP database, I just wantto be able toupdate existing records (like client addresses, telephone numbers, etc.,) and such. Therefore, if the risk is limited to the data being transferred (publicly available addresses, telephone numbers, etc.,) then it may still be a good idea to set up a remote connection between myclient apps and a centralized data store like my DASP database. If on the other hand, a hacker could somehow drop tables, or alter records, then I would have to reconsider this whole scenario.

    So I must ask, does the fact that data being transferred between client apps and the database not being highly encrypted mean that someone could access only that data, or could they access and alter the database items like my tables and stored procedures? Please let me know, and thanks again for your help.

    - George
     
  6. Thank you for all of your help, I do appreciated it.

    Mark, I was excited about your idea of usingDTS packagesto do this, however,I've been reading up on how to use DTS packagesandit seems that Microsoft has deprecated this in favor of something called SQL Server Integration Services (SSIS). Since I am not familiar with any of this, I am not sure how to proceed.

    So perhaps it may help if I reword my original question.

    Please consider this scenario: Let's say you have a DASP SQL Server 2005 database that is being used as the central data store for all of the records that you need to keep for your business. These records are created by customers (new and existing) who are usingyour company Web site.Let's also say you have 3 warehouses, warehouse A, warehouse B, and warehouseC. At each of thesewarehouse locations, there is computer with a desktop (Windows Forms) application thatyou would like touse to managethe DASP database. In this way, you have a single centralized database, with 3 client machines, one at each ofthe warehouse locations, that can connect,over the Internet, to the centralized DASP database and update records, insert new records etc..

    This is essentially what I want to do. Therefore, multiple users (3 users in this case) must be able to access the DASP database simultaneously.Given this scenario, what would be the best way for the Windows Forms application to connect, over the Internet, to the centralized DASP database, keeping in mind that the connection must be secureso that no data can be stolen by hackers, and alsoto prevent anyhacker from going in and trashing the DASP database (dropping tables etc.).

    Thanks in advance! [​IMG]

    - George
     
  7. Bruce

    Bruce DiscountASP.NET Staff

    Your best option is to connect directly to our server but that is not entirely secure. Even when you use SSIS, you're moving data insecurely.

    Bruce

    DiscountASP.NET
    www.DiscountASP.NET
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page