Hi everyone.
Using C# 2005 EE with SQL 2005 EE
I am really new to SQL, got qns here.
Can my program with SQL database run correctly on another com using win xp home edition, with only C# 2005 EE installed?
Is it compulsory for every table in a database to have a primary key?
Can I extract a data from a specific cell in a database table(click button get data)? How do I go about doing it (the simplest n straight forward method)?
Many Thanks in advance.
Regards,
dragoncells.
Hi !
"Can my program with SQL database run correctly on another com using win xp home edition, with only C# 2005 EE installed?"
YOu compiled application (The actual exe you produce with compiling) will work on every computer which has the requisites installed that you need in your application (at leat the .NET Framework). If you using an installer instead of Xcopy deployment you can also package the prerequisites ensuring that the client will fullfill the requirements.
"Is it compulsory for every table in a database to have a primary key? "
Thats all about database design, primary keys will help you to keep unique integrity throught he database and integrity with the other tables using PK/FK relations. They help you (and behind the scenes the SQL Server) to create and retrieve data by a unique identitifer.
"Can I extract a data from a specific cell in a database table(click button get data)? How do I go about doing it (the simplest n straight forward method)?"
I am not quite sure what you mean, but from my understanding you want to retrieve an specific attribute (your cell) from a row in a table. Therefore you will have to create a SQL query like the following one:
SELECT YourAttributeName_Column FROM YourTable Where <filter the row out by specifying the condition like SOmeCOlumn = 'SomeValue'>
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||
Additionally info about me: I am also Absolute Beginner in C# 2005 EE.
when you wrote "YOu compiled application (The actual exe you produce with compiling) will work on every computer which has the requisites installed that you need in your application (at leat the .NET Framework). If you using an installer instead of Xcopy deployment you can also package the prerequisites ensuring that the client will fullfill the requirements."
I assume you are telling me that if my application has a SQL database than I must have SQL server 2005 EE installed on that computer for it to work.
And what do you mean by Xcopy deployment?
Installer? I thought when I publish the application it comes with the installer?
**Note**
I replied to Jens post(1:27pm) but it does show properly.
Edited: Backed to normal.
|||
 dragoncells wrote: |
|
I assume you are telling me that if my application has a SQL database than I must have SQL server 2005 EE installed on that computer for it to work. |
You don′t need to have a SQL Server on the actual machine if you have another server in the network you want to connect to. Assuming that another server in the network act as a SQL Server you don′t have to install the SQL Server Express on the client machine.
"And what do you mean by Xcopy deployment?"
Xcopy deployment is possible because if the .NET framework is installed on the client machine no other things have to be registered like in the old days. YOu can just copy the application over (and also overwrite it with a newer version and it will work.
"Installer? I thought when I publish the application it comes with the installer?"
I don′t know which project type you are using. You will need an installer if you use components which do not easily install by just copying the files over, or if they have to be "installed" or copied in a different way.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||
That means Xcopy deployment is obsolete nowadays.
Using C# 2005 EE, working on a windows application project. When I publish my application it does come with a installer automatically?
|||No and no as the answer :-)
"That means Xcopy deployment is obsolete nowadays."
Seems that my description was too fuzzy. It is absolutely nice that you can do Xcopy deployment. Assuming that you want to update your application or an assembly within the application you just have to copy it over. Thats often used instead of uninstalling the old version and installing a new one.
A Windows application does not come automatically with a installer project. You will have to add one and will have to add the output files of your project solution to the installer project.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de|||
Than what about the Publish properties, isn't it suppose to add a installer after I publish my application?
Does the forum have a suggestion area or something, so that microsoft can collect useful suggestions and try to improve the forums?
|||As being a moderator you can direct that directly to me. The thing with the quotes was fixed by me as it seems that the syntax I used is not supported by the forum.
-Jens.|||
It slipped my mind that you are the moderator, lol.
Suggestions:
Images: Currently cannot post picture, a picture tells a thousand words.|||
nice suggestions, thanks. as we are currently working on additional features for the forums, we will take these under consideration and prioritize as appropriate. should you have additional suggestions, please be sure to post them in our suggestions forum.
best,
brian -- forums product manager
|||
Ok.
=)
