Can anyone tell me whether WMSDE (which installs with WSUS) can be patched?
I am trying to apply MSDE SP4 to the WSUS instance and it returns an error
message stating that SQL server is not installed.
Thanks in advance for your help.
Hi
You may want to print the exact error message, but any instance of SQL
Server should be patchable with the correct patch file.
John
"Buckeye" <Buckeye@.discussions.microsoft.com> wrote in message
news:94A93D9E-A8A8-481F-B1D8-12C9EA0E79E7@.microsoft.com...
> Can anyone tell me whether WMSDE (which installs with WSUS) can be
> patched?
> I am trying to apply MSDE SP4 to the WSUS instance and it returns an error
> message stating that SQL server is not installed.
> Thanks in advance for your help.
Showing posts with label msde. Show all posts
Showing posts with label msde. Show all posts
Tuesday, March 20, 2012
Patching WMSDE with SP4
Can anyone tell me whether WMSDE (which installs with WSUS) can be patched?
I am trying to apply MSDE SP4 to the WSUS instance and it returns an error
message stating that SQL server is not installed.
Thanks in advance for your help.Hi
You may want to print the exact error message, but any instance of SQL
Server should be patchable with the correct patch file.
John
"Buckeye" <Buckeye@.discussions.microsoft.com> wrote in message
news:94A93D9E-A8A8-481F-B1D8-12C9EA0E79E7@.microsoft.com...
> Can anyone tell me whether WMSDE (which installs with WSUS) can be
> patched?
> I am trying to apply MSDE SP4 to the WSUS instance and it returns an error
> message stating that SQL server is not installed.
> Thanks in advance for your help.
I am trying to apply MSDE SP4 to the WSUS instance and it returns an error
message stating that SQL server is not installed.
Thanks in advance for your help.Hi
You may want to print the exact error message, but any instance of SQL
Server should be patchable with the correct patch file.
John
"Buckeye" <Buckeye@.discussions.microsoft.com> wrote in message
news:94A93D9E-A8A8-481F-B1D8-12C9EA0E79E7@.microsoft.com...
> Can anyone tell me whether WMSDE (which installs with WSUS) can be
> patched?
> I am trying to apply MSDE SP4 to the WSUS instance and it returns an error
> message stating that SQL server is not installed.
> Thanks in advance for your help.
Patching WMSDE with SP4
Can anyone tell me whether WMSDE (which installs with WSUS) can be patched?
I am trying to apply MSDE SP4 to the WSUS instance and it returns an error
message stating that SQL server is not installed.
Thanks in advance for your help.Hi
You may want to print the exact error message, but any instance of SQL
Server should be patchable with the correct patch file.
John
"Buckeye" <Buckeye@.discussions.microsoft.com> wrote in message
news:94A93D9E-A8A8-481F-B1D8-12C9EA0E79E7@.microsoft.com...
> Can anyone tell me whether WMSDE (which installs with WSUS) can be
> patched?
> I am trying to apply MSDE SP4 to the WSUS instance and it returns an error
> message stating that SQL server is not installed.
> Thanks in advance for your help.
I am trying to apply MSDE SP4 to the WSUS instance and it returns an error
message stating that SQL server is not installed.
Thanks in advance for your help.Hi
You may want to print the exact error message, but any instance of SQL
Server should be patchable with the correct patch file.
John
"Buckeye" <Buckeye@.discussions.microsoft.com> wrote in message
news:94A93D9E-A8A8-481F-B1D8-12C9EA0E79E7@.microsoft.com...
> Can anyone tell me whether WMSDE (which installs with WSUS) can be
> patched?
> I am trying to apply MSDE SP4 to the WSUS instance and it returns an error
> message stating that SQL server is not installed.
> Thanks in advance for your help.
Patching WMSDE db's
Howdy,
Working on sql sp4 patching, we have one db that is an MSDE hybrid..WMSDE,
which is what ships with WSUS. If installed as the default on a Windows 200
3
server what sql version is it at, and has anyone had any experience with
patching this with MSDE SP4?
thxExperiencing the same issue on a WSUS server. ISS Internet Scanner says it
needs SQL SP4, but SP4 will not install. Anyone know if there is a version
of SP4 specifically designed for WMSDE? or whether or not WMSDE can be patc
hed at all?
**************
Working on sql sp4 patching, we have one db that is an MSDE hybrid..WMSDE,
which is what ships with WSUS. If installed as the default on a Windows 200
3
server what sql version is it at, and has anyone had any experience with
patching this with MSDE SP4?
thxExperiencing the same issue on a WSUS server. ISS Internet Scanner says it
needs SQL SP4, but SP4 will not install. Anyone know if there is a version
of SP4 specifically designed for WMSDE? or whether or not WMSDE can be patc
hed at all?
**************
quote:
Originally posted by bill_the_cat
Howdy,
Working on sql sp4 patching, we have one db that is an MSDE hybrid..WMSDE,
which is what ships with WSUS. If installed as the default on a Windows 200
3
server what sql version is it at, and has anyone had any experience with
patching this with MSDE SP4?
thx
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 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
>
>
Friday, March 9, 2012
Password protection
Basic, I know.....
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Password protection
Basic, I know.....
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".
Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>
|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".
Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>
|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Password protection
Basic, I know.....
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Password not Added after Installation
Hi,
I recently installed MSDE 2000, by giving the following to
setup parameters in the Command Prompt:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\> D:\MSDE2000\Setup.Exe SAPWD="apple" SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=0 /L*v C:\MSDELog.txt
C:\>
In log file, it did mentioned that the installation is
successfull at it's end of the file. However the SA
password is blank eventhough I gave the password
as "apple". Why did this happen. Is there anything wrong
in my setup parameter mentioned in the Command Prompt?
Help required on this matter, cos there are several
computers left to install MSDE 2000 and hoping to use the
above setup parameters.
Thanx in advance,
shahzard.
hi shahzard,
"Shahzard" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:574901c47465$e8574990$a301280a@.phx.gbl...
> Hi,
> I recently installed MSDE 2000, by giving the following to
> setup parameters in the Command Prompt:
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\> D:\MSDE2000\Setup.Exe SAPWD="apple" SECURITYMODE=SQL
> DISABLENETWORKPROTOCOLS=0 /L*v C:\MSDELog.txt
> C:\>
> In log file, it did mentioned that the installation is
> successfull at it's end of the file. However the SA
> password is blank eventhough I gave the password
> as "apple". Why did this happen. Is there anything wrong
> in my setup parameter mentioned in the Command Prompt?
> Help required on this matter, cos there are several
> computers left to install MSDE 2000 and hoping to use the
> above setup parameters.
the command line is ok, and i reproduced the problem on a Win2k box, where
SECURITYMODE=SQL has not been honored...
will investigate a little further... for workaround, run Regedit, locate
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\InstanceName\MSSQLServer
and set LoginMode key = 2
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
I recently installed MSDE 2000, by giving the following to
setup parameters in the Command Prompt:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\> D:\MSDE2000\Setup.Exe SAPWD="apple" SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=0 /L*v C:\MSDELog.txt
C:\>
In log file, it did mentioned that the installation is
successfull at it's end of the file. However the SA
password is blank eventhough I gave the password
as "apple". Why did this happen. Is there anything wrong
in my setup parameter mentioned in the Command Prompt?
Help required on this matter, cos there are several
computers left to install MSDE 2000 and hoping to use the
above setup parameters.
Thanx in advance,
shahzard.
hi shahzard,
"Shahzard" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:574901c47465$e8574990$a301280a@.phx.gbl...
> Hi,
> I recently installed MSDE 2000, by giving the following to
> setup parameters in the Command Prompt:
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\> D:\MSDE2000\Setup.Exe SAPWD="apple" SECURITYMODE=SQL
> DISABLENETWORKPROTOCOLS=0 /L*v C:\MSDELog.txt
> C:\>
> In log file, it did mentioned that the installation is
> successfull at it's end of the file. However the SA
> password is blank eventhough I gave the password
> as "apple". Why did this happen. Is there anything wrong
> in my setup parameter mentioned in the Command Prompt?
> Help required on this matter, cos there are several
> computers left to install MSDE 2000 and hoping to use the
> above setup parameters.
the command line is ok, and i reproduced the problem on a Win2k box, where
SECURITYMODE=SQL has not been honored...
will investigate a little further... for workaround, run Regedit, locate
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\InstanceName\MSSQLServer
and set LoginMode key = 2
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
Saturday, February 25, 2012
Password Change
Dear Friends
I have installed MSDE version on my pc but for the same
it have asked me to change the password of SA now i want
to change the password of SA with OSQL utility as i do
not have the Enterprise mangaer. Plese suggest how i can
change the same.
Your earlier reply will be helpful.
Best regards
ShaileshIn Osql you can use the sp_password system SP. Do please check the syntax in
Books OnLine.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"shailesh" <anonymous@.discussions.microsoft.com> wrote in message
news:7a0d01c3e8d5$a3d6fe80$a101280a@.phx.gbl...
From command prompt execute
OSQL -Usa -Ppassword -Sservername -Q"sp_password oldpassword,newpassword,sa"
Thanks
Hari
MCDBA
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:eVhRceN6DHA.1804@.TK2MSFTNGP12.phx.gbl...
in
I have installed MSDE version on my pc but for the same
it have asked me to change the password of SA now i want
to change the password of SA with OSQL utility as i do
not have the Enterprise mangaer. Plese suggest how i can
change the same.
Your earlier reply will be helpful.
Best regards
ShaileshIn Osql you can use the sp_password system SP. Do please check the syntax in
Books OnLine.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"shailesh" <anonymous@.discussions.microsoft.com> wrote in message
news:7a0d01c3e8d5$a3d6fe80$a101280a@.phx.gbl...
quote:|||Hi,
> Dear Friends
> I have installed MSDE version on my pc but for the same
> it have asked me to change the password of SA now i want
> to change the password of SA with OSQL utility as i do
> not have the Enterprise mangaer. Plese suggest how i can
> change the same.
> Your earlier reply will be helpful.
> Best regards
> Shailesh
From command prompt execute
OSQL -Usa -Ppassword -Sservername -Q"sp_password oldpassword,newpassword,sa"
Thanks
Hari
MCDBA
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:eVhRceN6DHA.1804@.TK2MSFTNGP12.phx.gbl...
quote:
> In Osql you can use the sp_password system SP. Do please check the syntax
in
quote:
> Books OnLine.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
> "shailesh" <anonymous@.discussions.microsoft.com> wrote in message
> news:7a0d01c3e8d5$a3d6fe80$a101280a@.phx.gbl...
>
Subscribe to:
Posts (Atom)