Prev: SQL Server 2008 32-bit on Windows 2008 64-bit
Next: Multi-Server jobs do not run on master server MSX
From: Uri Dimant on 3 Jan 2010 07:16
You change the server name in the .ini file and use regular connection
http://www.connectionstrings.com/


Make sure that you connect to the named isnatance to change the string



"Mody82" <u57214(a)uwe> wrote in message news:a18e36ae5ec37(a)uwe...
> Dear Dimant ,
>
> My application will be used for Inventory ( Stocks ),Sales &
> Purchases of Items, and it will be working locally as well as On server
> ( it
> depends if there is branches or not , if branches available it should work
> on
> Server ) , Upto date I didn't setup the application , i'm confuseing about
> the connection , So plz give me a solution for this case .
> The main case is I don't want to waste much time to install SQL server
> on
> each machine or PC , I just want to sell the CD including the exe files ,
> I
> hope it's clear .
>
> Thx with Best Wishes & Happy New year
>
> Regarding the version I'm using " Microsoft SQL Server Management Studio
> 9.
> 00.3042.00 "
>
>
> Uri Dimant wrote:
>>Hi
>>It is not clear how your application works I mean , does it work locally
>>or
>>connect to the server?
>>
>>I think I should start with a question what are the verison of SQL Server?
>>
>>If it is EXPRESS Edition then probably you need to install it on every
>>machine that application runs on ....
>>
>>> Hi for all
>>>
>>[quoted text clipped - 5 lines]
>>> application
>>> or is there any other solution ? ?
>


From: Erland Sommarskog on 3 Jan 2010 11:48
Mody82 (u57214(a)uwe) writes:
> Assume that each Machine has it's own Database , and he can do
> modification on the Databse through the Application only , So It's
> compulsory ( mandatory ) to install the SQL Server on his machine ?

No, you could still run SQL Server on a central server, even if each
user has his own database. Whether this is a good idea is another
matter, that depends a lot on the IT infrastructure in your organisation.

In another post it seems like you intended to sell your software as a
product. Obviously, customers will have to get a database as well. Unless,
you opt to host the databases for them. I would expect the latter to be
a much bigger undertaking.

--
Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

From: Mody82 via SQLMonster.com on 4 Jan 2010 07:05
Dear Erland ,
You said run SQL server on Central Server , that's mean I
have to install the SQL any way.
that's waht you mean in your last reply. ?

Erland Sommarskog wrote:
>> Assume that each Machine has it's own Database , and he can do
>> modification on the Databse through the Application only , So It's
>> compulsory ( mandatory ) to install the SQL Server on his machine ?
>
>No, you could still run SQL Server on a central server, even if each
>user has his own database. Whether this is a good idea is another
>matter, that depends a lot on the IT infrastructure in your organisation.
>
>In another post it seems like you intended to sell your software as a
>product. Obviously, customers will have to get a database as well. Unless,
>you opt to host the databases for them. I would expect the latter to be
>a much bigger undertaking.
>

--
Message posted via http://www.sqlmonster.com

From: Steen Schl�ter Persson on 4 Jan 2010 07:42

You'll have to have a SQL server instance available in one way or the other.
If that's on a central SQL server or if it's on a local PC is up to your.
That depends on how your application is meant to be used, and is not
something we can decide for you. If it's going to be a multi user
application, the database is best placed on a server. If it's only going to
be used by a "local" user on his own PC, it can be placed on the PC. No
matter what, you'll have to determine if there is a SQL instance that can be
used for your application, and if not it will have to be installed - either
by your application or by the user.


--
Regards
Steen Schl�ter Persson (DK)





"Mody82 via SQLMonster.com" <u57214(a)uwe> wrote in message
news:a19b07e32487b(a)uwe...
> Dear Erland ,
> You said run SQL server on Central Server , that's mean I
> have to install the SQL any way.
> that's waht you mean in your last reply. ?
>
> Erland Sommarskog wrote:
>>> Assume that each Machine has it's own Database , and he can do
>>> modification on the Databse through the Application only , So It's
>>> compulsory ( mandatory ) to install the SQL Server on his machine ?
>>
>>No, you could still run SQL Server on a central server, even if each
>>user has his own database. Whether this is a good idea is another
>>matter, that depends a lot on the IT infrastructure in your organisation.
>>
>>In another post it seems like you intended to sell your software as a
>>product. Obviously, customers will have to get a database as well. Unless,
>>you opt to host the databases for them. I would expect the latter to be
>>a much bigger undertaking.
>>
>
> --
> Message posted via http://www.sqlmonster.com
>


From: Erland Sommarskog on 4 Jan 2010 17:22
Mody82 via SQLMonster.com (u57214(a)uwe) writes:
> You said run SQL server on Central Server , that's mean I
> have to install the SQL any way.
> that's waht you mean in your last reply. ?

Well, for one thing I know very little of what you are doing. What
worries me more is that you nor do you seem to.

One of your posts hint that you intend to sell a product. I can't tell
how you should package your product or how it should be install. The one
thing I can tell you is that you must TEST a user scenario before you
install. That is, build a setup, install on a clean machine, verify that
it works. If you decide to ship SQL Server with your product, you must also
test what happens if there is an SQL Server instance on the machine.
Should you piggyback on that one? Always install your own?

The options I can see from the little information you have provided is:
1) Install SQL Server on each user machine.
2) Make a server-side installation of your package for installation on a
common server.
3) Host all databases on your own server.

My GUESS is that the first option is what you should go for, but it's
only possible for single-user scenarios.

And whatever I am not saying that you should do this or that. I'm just
making wild shots in the dark. And again: If you don't know what you are
doing, we will not know either.

All I can say is whatever you do: TEST!

--
Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: SQL Server 2008 32-bit on Windows 2008 64-bit
Next: Multi-Server jobs do not run on master server MSX