Client Tools for Backup

Hi all,
I hope this hasn't been answered already...
I have developed a .NET WinForms app which runs on client PCs which talk to
SQL Server2000 on a server. I have coded a backup screen which uses
SQLDMO. This runs fine when I run the app on the server, but it crashes
when I try it on the client PCs. Looks like something to do with an
unregistered
SQLDMO dll.
There's only one client PC which actually requires this functionality. I'm
thinking that installing Client Tools on this PC should take care of things.
I'm wondering if there are any licensing issues.
The company in question is running Small Business Server 2000 and has
the relevant licenses for SQL Server 2000.
Thanks!
John
See if this helps:
http://support.microsoft.com/default...b;EN-US;248241
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"jonsie" <jonsie@.discussions.microsoft.com> wrote in message
news:0F7A3DB9-C07E-4595-9D1A-B19300024332@.microsoft.com...
Hi all,
I hope this hasn't been answered already...
I have developed a .NET WinForms app which runs on client PCs which talk to
SQL Server2000 on a server. I have coded a backup screen which uses
SQLDMO. This runs fine when I run the app on the server, but it crashes
when I try it on the client PCs. Looks like something to do with an
unregistered
SQLDMO dll.
There's only one client PC which actually requires this functionality. I'm
thinking that installing Client Tools on this PC should take care of things.
I'm wondering if there are any licensing issues.
The company in question is running Small Business Server 2000 and has
the relevant licenses for SQL Server 2000.
Thanks!
John
|||hi John,
"jonsie" <jonsie@.discussions.microsoft.com> ha scritto nel messaggio
news:0F7A3DB9-C07E-4595-9D1A-B19300024332@.microsoft.com...
> Hi all,
> I hope this hasn't been answered already...
> I have developed a .NET WinForms app which runs on client PCs which talk
to
> SQL Server2000 on a server. I have coded a backup screen which uses
> SQLDMO. This runs fine when I run the app on the server, but it crashes
> when I try it on the client PCs. Looks like something to do with an
> unregistered
> SQLDMO dll.
> There's only one client PC which actually requires this functionality. I'm
> thinking that installing Client Tools on this PC should take care of
things.
> I'm wondering if there are any licensing issues.
> The company in question is running Small Business Server 2000 and has
> the relevant licenses for SQL Server 2000.
the SQL Server Client Tools are limited and related to SQL Server license...
regarding SQL-DMO component, you can distribute it as it is freely
redistributable..
the related dependencies are:
; not licensed by redist.txt but available after installation of MDAC2.6
...\WINDOWS\SYSTEM\odbcbcp.dll; DestDir: WinSys ; sharedfile
; not licensed by redist.txt but available after installation of MDAC2.6
...\WINDOWS\SYSTEM\sqlwoa.dll ; DestDir: WinSys
; not licensed by redist.txt but available after installation of MDAC2.6
...\WINDOWS\SYSTEM\sqlwid.dll ; DestDir: WinSys
...\Programmi\Microsoft SQL Server\80\Tools\Binn\w95scm.dll; DestDir:
DestinationFolder\Binn
...\WINDOWS\SYSTEM\sqlunirl.dll ; DestDir: WinSys
...\Programmi\Microsoft SQL Server\80\Tools\Binn\sqlresld.dll; DestDir:
DestinationFolder\Binn
...\Programmi\Microsoft SQL Server\80\Tools\Binn\sqlsvc.dll; DestDir:
DestinationFolder\Binn
; not licensed by redist.txt but available after installation of MDAC2.6
...\Programmi\Microsoft SQL Server\80\Tools\Binn\Resources\1033\sqlsvc.RLL;
DestDir: DestinationFolder\Binn\Resources\1033
; not licensed by redist.txt but available after installation of MDAC2.6
...\Programmi\Microsoft SQL Server\80\Tools\Binn\Resources\1033\Sqldmo.rll;
DestDir: DestinationFolder\Binn\Resources\1033
...\Programmi\Microsoft SQL Server\80\Tools\Binn\sqldmo.dll; DestDir:
DestinationFolder\Binn ; file to be registered via regserver
DestinationFolder can either be the installation directory of one instance
of Microsoft SqlServer 2000, like ..\Program Files\Microsoft SQL
Server\80\Tools, even if no istance of SQL Server has been installed, or the
installation directory of your application, but the first one is preferred.
Please do respect the hierarchy \Binn\Resources\1033 (where 1033 specifies
the language), where needed, in order to grant correct functionality of
Ole-Automation objects.
In order to install SQL-DMO components for MSDE 2000, Microsoft Internet
Explorer 5.5 or higher is required.
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

client setup

Can anyone tell me how to setup a client connection to
SQL server 2000?
All you need is an ODBC driver or OLE DB Provider for SQL Server. Once one
of them is in place, you need a tool like Query Analyzer or Enterprise
Manager to connect to SQL Server. All of them (client tools) can be
installed using the SQL Server setup CD.
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"brbaskets" <anonymous@.discussions.microsoft.com> wrote in message
news:944a01c4337c$8f2dc800$a501280a@.phx.gbl...
Can anyone tell me how to setup a client connection to
SQL server 2000?
|||Hi,
Install SQL Server client software coming along with SQL Server Installation CD. While installation select the "client only".
After the installation use any of the below tools to connect to SQL Server
1. Query Analyzer
2. Enterprise manager
3. OSQL / ISQL command line utilities
Note:
If you are not able to connect to servers or if the SQL server name is not automatically displayed in the server list then create a Alias name using "CLIENT NETWORK Utility" by providing the Protocol, IP ADDRESS and PORT number. Then using the Alias name
created you can connect to SQL Server.
Thanks
Hari
MCDBA
-- brbaskets wrote: --
Can anyone tell me how to setup a client connection to
SQL server 2000?
|||If you are asking about client connectivity via an application; you have
everything you need already installed. MDAC contains all necessary
components to connect to SQL Server, except the application to connect. You
can use Query Analyzer or Enterprise Manager or any other application that
connects to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||simply run the connectivity tools which is avalable in sql server cdrom.
"brbaskets" <anonymous@.discussions.microsoft.com> wrote in message
news:944a01c4337c$8f2dc800$a501280a@.phx.gbl...
> Can anyone tell me how to setup a client connection to
> SQL server 2000?