Re: Installing SQLSvr2K Evaluation Version on SQL Client
Next message: newbie: "How to assign values to a TEXT datatype in SQL"
Date: Tue, 2 Mar 2004 12:00:46 -0500
If by "SQL Client" you mean the tools, then you won't have any problem as
the tools are the same.
--
--Brian
(Please reply to the newsgroups only.)
"John" <anonymous@discussions.microsoft.com> wrote in message
news:281c01c3fc8c$cfe072c0$a401280a@phx.gbl...
>I need to evaluate SQL Server 2000 for a new application.
> This new application must be the primary instance.
>
> Can I install SQL Server 2000 Evaluation Version onto a
> machine that is already an SQL Client for another
> application without adversely affecting the Client
> Operation?
>
> Thanks in advance to all who respond.
>
> John
Next message: newbie: "How to assign values to a TEXT datatype in SQL"
Relevant Pages
- RE: Trouble with parameterized INSERT
... You should use parameter names with SQL Server. ... You should be able to use desktop samples with SQL Client. ... > Thread-Topic: Trouble with parameterized INSERT ... Microsoft CDO for Windows 2000 ... (microsoft.public.dotnet.framework.compactframework) - Database Create fails from a client via eroom installation wizard
... I have already posted on their forum with no help. ... is configured as the sql client. ... information for the username I created on the sql server and when I ... CERCreateSitePropSheet::OnCreateSite - Failed to create site snt on ... (microsoft.public.sqlserver.clients) - Re: Class library problem
... I have created a class library for connecting mobile devices to SQL Server ... the system installs not only SQL Server 2005 ... but also SQL Client for SQL Server 2000. ... (microsoft.public.dotnet.framework.compactframework) - Re: An error about "[dbnmpntw]ConnectionOpen(CreateFile())".
... Use the Client Configuration button. ... >But if I don't installed SQL Client on the machine I am ... >> to create alias server name for the sql server using ... >> And use this Alias name to connect to SQL server using ... (microsoft.public.sqlserver.security) - Re: SQL Server execution duration difference
... I am trying to figure out what you two are talking about now that doesn't make any sense about the speed of something running through SQL Server QA, which is in direct contact with SQL Server, as opposed to something that's running from a program that using OleDb ... ODBC: INSERT 20000 rows: 16,65625 seconds ... OLE DB: INSERT 20000 rows: 17,28125 seconds ... Anything coming from OLE DB or ODBC is going to be slower because those solutions are not in direct contact with SQL Server, as opposed to SQL Client or something running within SQL Server QA with those solutions being in direct contact with SQL Server. ... (microsoft.public.dotnet.general) |
|