Re: SBS 2003 and Sql Server ~ Client Install

So what were these "client tools"?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-Business-Server-Unleashed/dp/0672329573/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1

------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Boris Merryweather" <xx> wrote in message news:uaC%236NSBJHA.3496@xxxxxxxxxxxxxxxxxxxxxxx
As this is a part of SBS and as my original question concerned the licence number, I think this is the correct forum.

In the meantime, you're wrong! I've found the client tools and have now successfully installed them.

Best wishes
B.


"Cris Hanna [SBS - MVP]" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxx> wrote in message news:ewRX%23ATAJHA.4312@xxxxxxxxxxxxxxxxxxxxxxx
There is no "SQL client" software
There are management tools for managing the database
but as a client, there are many applications that can act as client as already pointed out. Access front end to a SQL database, Excel can be a front end, A word mail merge document could access a SQL database via ODBC.

You might do better in some of the SQL newsgroups

--
Cris Hanna [SBS - MVP]
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.
"Boris Merryweather" <xx> wrote in message news:e8wtbaG%23IHA.5036@xxxxxxxxxxxxxxxxxxxxxxx
Thank you for the reply.

You do not use the SQL Server installation on the clients
We're not (we hope). We are trying to install the client software (apparently it's on the SBS DVD, but the documentation around this area is lacking, to say the least).

Option 2 requires an understanding and purpose.

Installing SQL 'because it's there' is sortta silly.

We want to install to gain an understanding.
We understand that a Northwind training database is available for SQL Server.
We understand that something called "Books Online" is also installed on the client as part of the client install process.

Once we've managed to install the SQL Server Client we can start to use/test/train on it.
We have a project (currently in Access - No, it's not Northwind, but that's how we learnt Access all those years ago) that we want to transfer because currently Access performs all its calculations locally.
Stored procedures look as though they have the power we need without hogging the network (Access does everything locally / SQL Server doesn't).

So, we're back to the beginning.
How do we install the client software for SQL Server?

On the DVD the path is eventually in .....\SQL2005\TOOLS
Running DEFAULT.HTM brings upa screen showing "Run the SQL Native Client Installation Wizard"
During the install this prompts for the 25 character product key, which brings me back to my original question:

The installation asks for the 25 character product key. We've input the key that came with the SBS installation disk but are told that this is the wrong key. Should we have been supplied with another key specifically for a client install? Any help would be appreciated.

Pip pip
Boris


"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message news:%2353fkn$9IHA.3884@xxxxxxxxxxxxxxxxxxxxxxx
You do not use the SQL Server installation on the clients. Windows has native capabilities to act as an SQL client and this is normally configured by whatever application is acting as 'front end' to the database.

I have very little to do with SQL but I believe it is possible to install 'SQL Management' tools on the client(s). If I needed to do so, and the server was configured to allow this, I would probably download 'SQL Server Management Studio Express' (free download, ms) no matter what previous version of SQL was installed on the server. I think though that we a jumping ahead a bit by exploring this idea.

On the server you create an SQL database and configure it to be available across the network (if necessary). You then use ODBC (Control Panel, Administrative Tools, Data Sources (ODBC)) on the client to allow the 'connection' to the database (again, if necessary).

I say (if necessary) because, for example, it is not necessary to install, or configure, anything on the client to browse a web page backended by SQL. IIS on the server handles the connection to SQL. Also, programs like Access, on the client, will create 'ad-hoc' connections to the SQL server purely by options in the program.

There are a couple of reasons to install SQL on SBS.
1) Upgrade the MSDE instances (those that can be) to full SQL.
2) Create a new database.

Option 1 is documented somewhere, google is your friend if this is the aim.
Option 2 requires an understanding and purpose.

Installing SQL 'because it's there' is sortta silly.


"Boris Merryweather" <xx> wrote in message news:u7IZ0G$9IHA.6052@xxxxxxxxxxxxxxxxxxxxxxx
As I understand it, in order to use a SQL Server database you have to have something on the clients in order to use it (some sort of editor?) otherwise you have to do all the work on the server.

Your reply suggests that we're missing something - a few brain cells perhaps ;-)

Regards
B


"Cris Hanna [SBS-MVP]" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxx> wrote in message news:%239Z79L%239IHA.3612@xxxxxxxxxxxxxxxxxxxxxxx
What are you trying to install on the client?

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues

"Boris Merryweather" <xx> wrote in message news:u$bCwe69IHA.5228@xxxxxxxxxxxxxxxxxxxxxxx
We've been using SBS 2003 R2 Premium Edition for a few years.
We've decided to see what benefits Sql Server might offer us.

The server installation seems okay but we keep failing when we try to
install software on a client. The installation asks for the 25 character
product key. We've input the key that came with the SBS installation disk
but are told that this is the wrong key. Should we have been supplied with
another key specifically for a client install? Any help would be
appreciated.

--

TIA
Boris Merryweather








.

Relevant Pages

  • Re: Fax on Terminal Server from SBS2K3
    ... please make sure the Fax service is installed on the TS server. ... you can try the steps below to install Shared Fax Client: ... 248340 Installing and Using Programs in Windows 2000 Terminal Services ...
    (microsoft.public.windows.server.sbs)
  • RE: Fax monitor incoming + outgoing calls?
    ... The detail steps to install share fax client as follows: ... Start server management console, locate Client Computers node, click ... To the folder redirection GPO issue: ... How to stop Folder Redirection in Windows Server 2003 and in Windows 2000 ...
    (microsoft.public.windows.server.sbs)
  • RE: No Client or Server Desktop Access Through RWW SBS 2003 SP2
    ... The SBS server is running SP2. ... However I don't know if the client computers do. ... To successfully install SBS 2003 SP1, ...
    (microsoft.public.windows.server.sbs)
  • Re: Fax on Terminal Server from SBS2K3
    ... activity logging in the shared fax in the server box. ... Microsoft CSS Online Newsgroup Support ... Follow the wizard to install Shared ... you can try the steps below to install Shared Fax Client: ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Fax Sharepoint Routing
    ... Business Server 2003 and click "Change/Remove", ... If the Fax Services component was original installed by using the SBS ... Install fro the Fax Server component. ... And then we should push the shared fax client application from server to ...
    (microsoft.public.windows.server.sbs)