June 19, 2009 at 1:38 pm
Hi I'm new to database development and am currently building a database for college using MS SQL I then plan to build an interface for it using visual basic. At home my PC is acting as the server. However, I recently got my work place to purchase MS Visual Studio pro with SQL server 2005,so that I could continue working on the system during working hours. I was told that they currently don't have space on a server running SQL and that while I develop the database I should just connect to my own desktop PC which of course also has SQL server running on it. However, I wanted to test out how my queries and stored procedure run across the network during development instead of waiting until I finish. I guess my lack of knowledge also has be concerned that moving the database will cause problems later. What I mean is if I build the GUI using Visual basic (dataBinding and Dataset) will this not cause problems when I move the database from my PC to a server. Having said that, I cant help but think that this must happen to lots of people and that it should not cause any great issues. Is it fare to say that if all running well on my own PC I cant be sure that it also will across a network. Should I just chill out about this develop my database and GUI and worry about servers and networks later. After all if I was developing it for an customer instead of the company I work for I would not have access to the server it will sit on at the developing stage.
Thanks for your help
A
June 20, 2009 at 6:54 am
to connect to database server from across network from a diff machine, you mention the server name, user id and password in the connectionstring. obviously if there is enough network bandwidth you wont face any issues.
June 20, 2009 at 10:58 am
Keil.asta
I then plan to build an interface for it using visual basic
Using VB6 or VB dot net -either way. Using VB6 here is an extract form my code which allows you to chose where the database is located ... on a server or local machine without any problems.
'In project references you MUST select
Microsoft OLE DB Service Component 1.0 Type Library
This in turn loads oledb32.dll into your project
then'
Dim objMSDAC As MSDASC.DataLinks
'
In project reference you MUST select
Microsof ActiveX Data Objects 2.8 Library
This in turn loads Msado15.dll into your project
Note if invoking the approle then pay attention to:
http://www.sqlservercentral.com/Forums/Topic533262-146-5.aspx#bm568983
For SQLOLEDB provider
strConnect = "Provider=SQLOLEDB;server=SQL7Web;OLE DB Services = -2;
uid=AppUser;pwd=AppUser;initial catalog=northwind"
For MSDASQL provider
strConnect = "DSN=SQLNWind;UID=Test;PWD=Test; OLE DB Services= -2'
Set objMSDAC = New MSDASC.DataLinks
Cnn_String = objMSDAC.PromptNew
Cnn.ConnectionString = Cnn_String
'
At this point you can use the debugger to display the connection string and apply it to your connection object and away you go'
June 20, 2009 at 11:12 am
Well it a big company over 300 people so I imaging it must be OK. I guess I should just develop my project on my own PC and not worry about this until the time comes. Thanks for you help and I guess then I can ask more specific question if I get suck :-).
thanks
A
June 20, 2009 at 11:23 am
Obviously you can come here anytime to ask questions and ppl out here will be more than willing to assist.:-)
June 20, 2009 at 11:27 am
Thank you :-). I'd be lost without places like this and it does make me wonder how did people manage with tech problems before we had the internet.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply