MSDE 2000
-
Maybe this is a dumb question. If I have MS SQL Server Desktop Edition, can I access the database from a seperate computer? Or do I need SQL Server for that? 'Cause I sure can't afford to get SQL Server, and my database application is only going to be deployed on 3-5 computers. Thanks for the help. The ends can never justify the means. It is the means that determine the ends.
-
Maybe this is a dumb question. If I have MS SQL Server Desktop Edition, can I access the database from a seperate computer? Or do I need SQL Server for that? 'Cause I sure can't afford to get SQL Server, and my database application is only going to be deployed on 3-5 computers. Thanks for the help. The ends can never justify the means. It is the means that determine the ends.
theStorminMormon wrote: Maybe this is a dumb question. If I have MS SQL Server Desktop Edition, can I access the database from a seperate computer? Or do I need SQL Server for that? 'Cause I sure can't afford to get SQL Server, and my database application is only going to be deployed on 3-5 computers. You can use MSDE 2000 from other computers on the network. I do this all the time. Providing the correct permissions are set then you should have no problems. Michael CP Blog [^] Development Blog [^]
-
theStorminMormon wrote: Maybe this is a dumb question. If I have MS SQL Server Desktop Edition, can I access the database from a seperate computer? Or do I need SQL Server for that? 'Cause I sure can't afford to get SQL Server, and my database application is only going to be deployed on 3-5 computers. You can use MSDE 2000 from other computers on the network. I do this all the time. Providing the correct permissions are set then you should have no problems. Michael CP Blog [^] Development Blog [^]
OK - so just to be absolutely clear, if I run MSDE 2000 on a "server" (it's actually just my desktop running win xp pro) and I deploy an application to my client (my laptop) that accesses a database on my server via MSDE 2000 - that should work? Right now my application runs fine on the server, but it can't find the database from the client. This is connection string: private string strConn = @"Integrated Security=SSPI; Packet Size=4096 ;Data Source=""EC-BJACOBS""; Initial Catalog=BenefitSelectDBSQL; Provider=""SQLOLEDB""; Workstation ID=""EC-BJACOBS""; Use Encryption for Data=False"; Next question - how do I set the correct permissions? The ends can never justify the means. It is the means that determine the ends.
-
OK - so just to be absolutely clear, if I run MSDE 2000 on a "server" (it's actually just my desktop running win xp pro) and I deploy an application to my client (my laptop) that accesses a database on my server via MSDE 2000 - that should work? Right now my application runs fine on the server, but it can't find the database from the client. This is connection string: private string strConn = @"Integrated Security=SSPI; Packet Size=4096 ;Data Source=""EC-BJACOBS""; Initial Catalog=BenefitSelectDBSQL; Provider=""SQLOLEDB""; Workstation ID=""EC-BJACOBS""; Use Encryption for Data=False"; Next question - how do I set the correct permissions? The ends can never justify the means. It is the means that determine the ends.
theStorminMormon wrote: private string strConn = @"Integrated Security=SSPI; Packet Size=4096 ;Data Source=""EC-BJACOBS""; Initial Catalog=BenefitSelectDBSQL; Provider=""SQLOLEDB""; Workstation ID=""EC-BJACOBS""; Use Encryption for Data=False"; Next question - how do I set the correct permissions? You are currently using Windows Authentication? Do you have a domain controller that manages your user security? If so, just add the domain users as users in your database and give them the required permissions. If you don't have a domain controller, then it becomes a bit of a pain to use Windows Authentication. It is easier to create SQL users and change the connection string to use SQL authentication. Michael CP Blog [^] Development Blog [^]
-
theStorminMormon wrote: private string strConn = @"Integrated Security=SSPI; Packet Size=4096 ;Data Source=""EC-BJACOBS""; Initial Catalog=BenefitSelectDBSQL; Provider=""SQLOLEDB""; Workstation ID=""EC-BJACOBS""; Use Encryption for Data=False"; Next question - how do I set the correct permissions? You are currently using Windows Authentication? Do you have a domain controller that manages your user security? If so, just add the domain users as users in your database and give them the required permissions. If you don't have a domain controller, then it becomes a bit of a pain to use Windows Authentication. It is easier to create SQL users and change the connection string to use SQL authentication. Michael CP Blog [^] Development Blog [^]
When I originally installed and set up MSDE 2000 and my database, I had no clue what I was doing. The directions were unclear (to me) and I considered myself extraordinarily lucky when my program actually connected to the database at all (I still don't understand the connection between the database that I designed in Access, MSDE 2000, the SQL Server, and my C# application). What I'm trying to convey with all of this is that it's purely accidental that I ended up using Windows Authentication, and I would prefer to create SQL users and change the connection string to use SQL authentication if only I knew how. Can you give some pointers on how to do this? The only access I have to MSDE 2000 on my own machine is too click on the little icon in the system tray - which brings up the SQL Service Manager (which doesn't let me do anything useful). I just downloaded DbaMgr2k to try and get better access to the server (to add users, change authentication type) but I'm not sure how this works. Any help you could offer would be great. I have books on C#, ADO.NET, and MS Access, but running MSDE 2000 seems to fall between the cracks and each book only offers tidbits on how to use it. Thanks. The ends can never justify the means. It is the means that determine the ends.
-
When I originally installed and set up MSDE 2000 and my database, I had no clue what I was doing. The directions were unclear (to me) and I considered myself extraordinarily lucky when my program actually connected to the database at all (I still don't understand the connection between the database that I designed in Access, MSDE 2000, the SQL Server, and my C# application). What I'm trying to convey with all of this is that it's purely accidental that I ended up using Windows Authentication, and I would prefer to create SQL users and change the connection string to use SQL authentication if only I knew how. Can you give some pointers on how to do this? The only access I have to MSDE 2000 on my own machine is too click on the little icon in the system tray - which brings up the SQL Service Manager (which doesn't let me do anything useful). I just downloaded DbaMgr2k to try and get better access to the server (to add users, change authentication type) but I'm not sure how this works. Any help you could offer would be great. I have books on C#, ADO.NET, and MS Access, but running MSDE 2000 seems to fall between the cracks and each book only offers tidbits on how to use it. Thanks. The ends can never justify the means. It is the means that determine the ends.
Hehe, that's about the way I felt when installing MSDE for the first time. Having access to the EnterpriseManager of a "full" SQLServer helps alot, though. MSDE basically is a full SQLServer with only performance-related restrictions, so you can use all the built-in stored procedures, for example, to manage database access, users and so on. Try opening a command shell and type "osql -E" to open up an SQL-"shell" you can use to query your databases. Some time ago I found the online documentation for SQLServer2000 on microsoft.com. Pretty complete, helped me a lot. For example, it lists the stored procedures available and how to execute them. You can download it here[^] Regards, mav
-
Hehe, that's about the way I felt when installing MSDE for the first time. Having access to the EnterpriseManager of a "full" SQLServer helps alot, though. MSDE basically is a full SQLServer with only performance-related restrictions, so you can use all the built-in stored procedures, for example, to manage database access, users and so on. Try opening a command shell and type "osql -E" to open up an SQL-"shell" you can use to query your databases. Some time ago I found the online documentation for SQLServer2000 on microsoft.com. Pretty complete, helped me a lot. For example, it lists the stored procedures available and how to execute them. You can download it here[^] Regards, mav
Thanks, I'm downloading it now. Hopefully it will help. The ends can never justify the means. It is the means that determine the ends.