Dear Sir,
Actually i want to ask, how to install the SQL Server Desktop Edition
2000 Client Tools only from the Command Prompt ? i have gone through the
internet but all the responds were about SQL Server Desktop Edition
2005, and it does not work for SQL Server Desktop Edition 2000.
I just could find the below command to install the full package:
setup.exe sapwd=abc123 sequritymode=sql
disablenetworkprotocols=0
Could you please help me to get this done,
Appreciate your kind consideration,
Best Regards,
Feri.
*** Sent via Developersdex http://www.codecomments.com ***
First, I would put something less like a junk mail subject in the subject. I
suggest: "SQL Server Desktop 2000 Installation".
Next, I would post this on the right newsgroup. This group focuses on
Connecting to SQL Server. You have an installation issue so I suggest using
microsoft.public.sqlserver.msde...
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Feri Sh" <far.sharifi@.gmail.com> wrote in message
news:uwMDZQM2HHA.1168@.TK2MSFTNGP02.phx.gbl...
> Dear Sir,
> Actually i want to ask, how to install the SQL Server Desktop Edition
> 2000 Client Tools only from the Command Prompt ? i have gone through the
> internet but all the responds were about SQL Server Desktop Edition
> 2005, and it does not work for SQL Server Desktop Edition 2000.
> I just could find the below command to install the full package:
> setup.exe sapwd=abc123 sequritymode=sql
> disablenetworkprotocols=0
> Could you please help me to get this done,
> Appreciate your kind consideration,
>
> Best Regards,
> Feri.
> *** Sent via Developersdex http://www.codecomments.com ***
sql
Showing posts with label desktop. Show all posts
Showing posts with label desktop. Show all posts
Wednesday, March 21, 2012
Pay Attention Please...
Dear Sir,
Actually i want to ask, how to install the SQL Server Desktop Edition
2000 Client Tools only from the Command Prompt ? i have gone through the
internet but all the responds were about SQL Server Desktop Edition
2005, and it does not work for SQL Server Desktop Edition 2000.
I just could find the below command to install the full package:
setup.exe sapwd=abc123 sequritymode=sql
disablenetworkprotocols=0
Could you please help me to get this done,
Appreciate your kind consideration,
Best Regards,
Feri.
*** Sent via Developersdex http://www.codecomments.com ***First, I would put something less like a junk mail subject in the subject. I
suggest: "SQL Server Desktop 2000 Installation".
Next, I would post this on the right newsgroup. This group focuses on
Connecting to SQL Server. You have an installation issue so I suggest using
microsoft.public.sqlserver.msde...
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Feri Sh" <far.sharifi@.gmail.com> wrote in message
news:uwMDZQM2HHA.1168@.TK2MSFTNGP02.phx.gbl...
> Dear Sir,
> Actually i want to ask, how to install the SQL Server Desktop Edition
> 2000 Client Tools only from the Command Prompt ? i have gone through the
> internet but all the responds were about SQL Server Desktop Edition
> 2005, and it does not work for SQL Server Desktop Edition 2000.
> I just could find the below command to install the full package:
> setup.exe sapwd=abc123 sequritymode=sql
> disablenetworkprotocols=0
> Could you please help me to get this done,
> Appreciate your kind consideration,
>
> Best Regards,
> Feri.
> *** Sent via Developersdex http://www.codecomments.com ***
Actually i want to ask, how to install the SQL Server Desktop Edition
2000 Client Tools only from the Command Prompt ? i have gone through the
internet but all the responds were about SQL Server Desktop Edition
2005, and it does not work for SQL Server Desktop Edition 2000.
I just could find the below command to install the full package:
setup.exe sapwd=abc123 sequritymode=sql
disablenetworkprotocols=0
Could you please help me to get this done,
Appreciate your kind consideration,
Best Regards,
Feri.
*** Sent via Developersdex http://www.codecomments.com ***First, I would put something less like a junk mail subject in the subject. I
suggest: "SQL Server Desktop 2000 Installation".
Next, I would post this on the right newsgroup. This group focuses on
Connecting to SQL Server. You have an installation issue so I suggest using
microsoft.public.sqlserver.msde...
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Feri Sh" <far.sharifi@.gmail.com> wrote in message
news:uwMDZQM2HHA.1168@.TK2MSFTNGP02.phx.gbl...
> Dear Sir,
> Actually i want to ask, how to install the SQL Server Desktop Edition
> 2000 Client Tools only from the Command Prompt ? i have gone through the
> internet but all the responds were about SQL Server Desktop Edition
> 2005, and it does not work for SQL Server Desktop Edition 2000.
> I just could find the below command to install the full package:
> setup.exe sapwd=abc123 sequritymode=sql
> disablenetworkprotocols=0
> Could you please help me to get this done,
> Appreciate your kind consideration,
>
> Best Regards,
> Feri.
> *** Sent via Developersdex http://www.codecomments.com ***
Tuesday, March 20, 2012
Patching SQLServer/MSDE
Patching SQLServer/MSDE
We are developing a desktop application that will use an MSDE database. The
data in the DB we deploy cannot be read by users, or administrators of the b
ox or other SQL Server admins. To accomplish this, we have learned we would
have to install a separate
instance of SQLServer/MSDE on the user's PC (or, alternately, encrypt the da
tabase).
The downside to a separate instance is we would be responsible to apply any
SQL Server patches to our instance. Our software is given to our customers,
and we have no control over their machines, so we will have to issue servic
e patches for our software
that contain the SQL Server patches as they come out.
My question is this: Obviously, it will be difficult for us to get patches o
f our software out there immediately after each SQL Server patch is released
my Microsoft. Are there threats that SQL Server remedy that can possibly ha
ve an adverse effect on sof
tware/hardware outside of the our database that is using the SQL Server inst
ance? I'm wondering about our liability if say, we release our version of a
patch 1-2 months after Microsoft releases their patch. I know our database
may be threatened, but is
there the possibility the user's machines/network would also be threatened i
f certain patches are not installed in a timely matter? I understand how th
is would be a major issue if we were talking about patches to IIS, but not
so sure about SQL Server.
Any thoughts on this are greatly appreciated.
Thanks!MSDE can be configured to listen only on Shared Memory. This will limit
your exposure from
external machines. So, other machines won't be able to connect to your
instance of MSDE, since
it's not listening on TCP or Named Pipes. Only local connections would
succeed.
MBSA 1.2 can be used to scan the local machine to see if it needs any SQL
related security fixes.
This could be documented in your application notes.
http://www.microsoft.com/technet/se...s/mbsahome.mspx
You can also find out Best Practices on the web ;
http://www.microsoft.com/technet/pr...n/sp3sec00.mspx
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
We are developing a desktop application that will use an MSDE database. The
data in the DB we deploy cannot be read by users, or administrators of the b
ox or other SQL Server admins. To accomplish this, we have learned we would
have to install a separate
instance of SQLServer/MSDE on the user's PC (or, alternately, encrypt the da
tabase).
The downside to a separate instance is we would be responsible to apply any
SQL Server patches to our instance. Our software is given to our customers,
and we have no control over their machines, so we will have to issue servic
e patches for our software
that contain the SQL Server patches as they come out.
My question is this: Obviously, it will be difficult for us to get patches o
f our software out there immediately after each SQL Server patch is released
my Microsoft. Are there threats that SQL Server remedy that can possibly ha
ve an adverse effect on sof
tware/hardware outside of the our database that is using the SQL Server inst
ance? I'm wondering about our liability if say, we release our version of a
patch 1-2 months after Microsoft releases their patch. I know our database
may be threatened, but is
there the possibility the user's machines/network would also be threatened i
f certain patches are not installed in a timely matter? I understand how th
is would be a major issue if we were talking about patches to IIS, but not
so sure about SQL Server.
Any thoughts on this are greatly appreciated.
Thanks!MSDE can be configured to listen only on Shared Memory. This will limit
your exposure from
external machines. So, other machines won't be able to connect to your
instance of MSDE, since
it's not listening on TCP or Named Pipes. Only local connections would
succeed.
MBSA 1.2 can be used to scan the local machine to see if it needs any SQL
related security fixes.
This could be documented in your application notes.
http://www.microsoft.com/technet/se...s/mbsahome.mspx
You can also find out Best Practices on the web ;
http://www.microsoft.com/technet/pr...n/sp3sec00.mspx
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Monday, March 12, 2012
patch / update which packages?
hi
i updated my sql server today to sp3
there are more packages to download from microsoft site
the analysis package and the
msde desktop engine
do i need those too to have a full patched and updated sql server ready?
thank you for your hints
mike schwarz
If you are running analysis services then you need the analysis package.
If you are utilizing msde then you need the msde package. Otherwise you are
ok.
"Mike Schwarz" <ctek@.ctek.ch> wrote in message
news:ejyoWTBHEHA.2768@.tk2msftngp13.phx.gbl...
> hi
> i updated my sql server today to sp3
> there are more packages to download from microsoft site
> the analysis package and the
> msde desktop engine
> do i need those too to have a full patched and updated sql server ready?
> thank you for your hints
> mike schwarz
>
>
i updated my sql server today to sp3
there are more packages to download from microsoft site
the analysis package and the
msde desktop engine
do i need those too to have a full patched and updated sql server ready?
thank you for your hints
mike schwarz
If you are running analysis services then you need the analysis package.
If you are utilizing msde then you need the msde package. Otherwise you are
ok.
"Mike Schwarz" <ctek@.ctek.ch> wrote in message
news:ejyoWTBHEHA.2768@.tk2msftngp13.phx.gbl...
> hi
> i updated my sql server today to sp3
> there are more packages to download from microsoft site
> the analysis package and the
> msde desktop engine
> do i need those too to have a full patched and updated sql server ready?
> thank you for your hints
> mike schwarz
>
>
patch / update which packages?
hi
i updated my sql server today to sp3
there are more packages to download from microsoft site
the analysis package and the
msde desktop engine
do i need those too to have a full patched and updated sql server ready?
thank you for your hints
mike schwarzIf you are running analysis services then you need the analysis package.
If you are utilizing msde then you need the msde package. Otherwise you are
ok.
"Mike Schwarz" <ctek@.ctek.ch> wrote in message
news:ejyoWTBHEHA.2768@.tk2msftngp13.phx.gbl...
> hi
> i updated my sql server today to sp3
> there are more packages to download from microsoft site
> the analysis package and the
> msde desktop engine
> do i need those too to have a full patched and updated sql server ready?
> thank you for your hints
> mike schwarz
>
>
i updated my sql server today to sp3
there are more packages to download from microsoft site
the analysis package and the
msde desktop engine
do i need those too to have a full patched and updated sql server ready?
thank you for your hints
mike schwarzIf you are running analysis services then you need the analysis package.
If you are utilizing msde then you need the msde package. Otherwise you are
ok.
"Mike Schwarz" <ctek@.ctek.ch> wrote in message
news:ejyoWTBHEHA.2768@.tk2msftngp13.phx.gbl...
> hi
> i updated my sql server today to sp3
> there are more packages to download from microsoft site
> the analysis package and the
> msde desktop engine
> do i need those too to have a full patched and updated sql server ready?
> thank you for your hints
> mike schwarz
>
>
patch / update which packages?
hi
i updated my sql server today to sp3
there are more packages to download from microsoft site
the analysis package and the
msde desktop engine
do i need those too to have a full patched and updated sql server ready?
thank you for your hints
mike schwarzIf you are running analysis services then you need the analysis package.
If you are utilizing msde then you need the msde package. Otherwise you are
ok.
"Mike Schwarz" <ctek@.ctek.ch> wrote in message
news:ejyoWTBHEHA.2768@.tk2msftngp13.phx.gbl...
> hi
> i updated my sql server today to sp3
> there are more packages to download from microsoft site
> the analysis package and the
> msde desktop engine
> do i need those too to have a full patched and updated sql server ready?
> thank you for your hints
> mike schwarz
>
>
i updated my sql server today to sp3
there are more packages to download from microsoft site
the analysis package and the
msde desktop engine
do i need those too to have a full patched and updated sql server ready?
thank you for your hints
mike schwarzIf you are running analysis services then you need the analysis package.
If you are utilizing msde then you need the msde package. Otherwise you are
ok.
"Mike Schwarz" <ctek@.ctek.ch> wrote in message
news:ejyoWTBHEHA.2768@.tk2msftngp13.phx.gbl...
> hi
> i updated my sql server today to sp3
> there are more packages to download from microsoft site
> the analysis package and the
> msde desktop engine
> do i need those too to have a full patched and updated sql server ready?
> thank you for your hints
> mike schwarz
>
>
Saturday, February 25, 2012
Password Change
I am relatively new to SQL and have the developer edition
on my desktop. I think that I may have used the wrong
method of authentication as I have to change my password
on the network every 90 dys and now the SQL server
service will not start and I get a password error. When I
try to view the properties I get an error saying the
password is incorrect.You can also change the Windows service account password for the SQL Server
service under Windows 2000/XP as follows.
Right-click on My Computer and select Manage
Select 'Service and Applications' and then Services
Double-click on 'MSSQLSERVER' (or 'MSSQL$YourInstanceName') from the
services list and clock the 'Log On' tab
Once you've successfully started the SQL Server service, you can change the
service account to the system account via Enterprise Manager so that you
don't need to bother with periodically changing the service password.
Hope this helps.
Dan Guzman
SQL Server MVP
"Mike" <mrestall@.superbolt.com> wrote in message
news:965e01c3eb21$359cc320$a101280a@.phx.gbl...
on my desktop. I think that I may have used the wrong
method of authentication as I have to change my password
on the network every 90 dys and now the SQL server
service will not start and I get a password error. When I
try to view the properties I get an error saying the
password is incorrect.You can also change the Windows service account password for the SQL Server
service under Windows 2000/XP as follows.
Right-click on My Computer and select Manage
Select 'Service and Applications' and then Services
Double-click on 'MSSQLSERVER' (or 'MSSQL$YourInstanceName') from the
services list and clock the 'Log On' tab
Once you've successfully started the SQL Server service, you can change the
service account to the system account via Enterprise Manager so that you
don't need to bother with periodically changing the service password.
Hope this helps.
Dan Guzman
SQL Server MVP
"Mike" <mrestall@.superbolt.com> wrote in message
news:965e01c3eb21$359cc320$a101280a@.phx.gbl...
quote:
> I am relatively new to SQL and have the developer edition
> on my desktop. I think that I may have used the wrong
> method of authentication as I have to change my password
> on the network every 90 dys and now the SQL server
> service will not start and I get a password error. When I
> try to view the properties I get an error saying the
> password is incorrect.
Subscribe to:
Posts (Atom)