I've got a situation where WSUS is already installed on a server and I'm
looking
at moving my anti-virus system on to the same server, however my AV uses
MSDE. The server is running 2003 and therefore WSUS is running in WMSDE.
I take it I can't use WMSDE for my AV solution so I'd like to know, is it
viable to simply install MSDE 2000 along side WMSDE, or will I have to move
WSUS out of WMSDE and into MSDE 2000?
I assume I'll have some conflicts at minimum with the ports clashing if the
two live together, and there are likely to be other major problems.
Does anyone have any ideas or suggestions?
hi,
AC wrote:
> I've got a situation where WSUS is already installed on a server and
> I'm looking
> at moving my anti-virus system on to the same server, however my AV
> uses MSDE. The server is running 2003 and therefore WSUS is running
> in WMSDE.
> I take it I can't use WMSDE for my AV solution so I'd like to know,
> is it viable to simply install MSDE 2000 along side WMSDE, or will I
> have to move WSUS out of WMSDE and into MSDE 2000?
> I assume I'll have some conflicts at minimum with the ports clashing
> if the two live together, and there are likely to be other major
> problems.
> Does anyone have any ideas or suggestions?
WMSDE should not be used for other means then the ones it has been released
for, so just install another instance of MSDE for your AV...
you'll have no "ports clashing" or conflicts, as SQL Server 2000 allows up
to 16 instances to be locally installed...
only one of them can be the "default" instance, litening (by default) on
TCP/IP 1433 where all other instances have to be named instances, where
their full name is composed by the ComputerName\InstanceName...
you can leave for all of them the default "dynamically assigned port"
setting, an additional service, the SQL Server Resolution Service is then
listening on UDP 1434 to resolve and address the correct named instance on
it's appropriate port..
if you manually set the TCP/IP port the named instance(s) will be listen on,
you can close (on your firewall) the UDP 1434 port as it is no longer
needed, but you'll probably need to specify an ALIAS (via Client Network
Utility, cliconfg.exe) on all your remote clients..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you very much for your reply Andrea.
Although I've seen installations with several MSDE instances before I never
thought about how they worked untill now, therefore I've never even realised
there is a manager service to resolve the ports for each service!
Thank you for enlightening to this!
"Andrea Montanari" wrote:
> hi,
> AC wrote:
> WMSDE should not be used for other means then the ones it has been released
> for, so just install another instance of MSDE for your AV...
> you'll have no "ports clashing" or conflicts, as SQL Server 2000 allows up
> to 16 instances to be locally installed...
> only one of them can be the "default" instance, litening (by default) on
> TCP/IP 1433 where all other instances have to be named instances, where
> their full name is composed by the ComputerName\InstanceName...
> you can leave for all of them the default "dynamically assigned port"
> setting, an additional service, the SQL Server Resolution Service is then
> listening on UDP 1434 to resolve and address the correct named instance on
> it's appropriate port..
> if you manually set the TCP/IP port the named instance(s) will be listen on,
> you can close (on your firewall) the UDP 1434 port as it is no longer
> needed, but you'll probably need to specify an ALIAS (via Client Network
> Utility, cliconfg.exe) on all your remote clients..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
sql
Showing posts with label ive. Show all posts
Showing posts with label ive. Show all posts
Friday, March 30, 2012
MSDE access over network slow for XP workstations, not Win2K
I've installed MSDE SP3a on a Windows 2000 Server, and the VB6 client
application on multiple workstations.
These workstations are either Win2000 Pro or WinXP Pro (both SP1 and SP2).
All workstations can access and ping the server under 1MS.
When the client application opens and reads data from the database server,
it takes a short time for this to be performed on the Win2000 Pro machines,
but all the XP machines take an abnormally long time to connect and to
retrieve the data.
The XP's do connect, but the retrieval is very slow, sometimes it timesout
during a retrieval.
This occurs even when nobody is connected to the database, so I've ruled out
the governer.
I'm using ADO to connect and all PC's have MDAC 2.7 or greater.
The install process only installed MDAC 2.7 if the current version is before
that.
Anybody have an idea what might be the problem?
All responses are welcome.
TIA
Jim K
Hi Jim,
Name resolution problems perhaps? Try connecting to the IP address instead
of the server name to find out.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim K" <krusej@.megsinet.net> wrote in message
news:enMo6BQ7EHA.1596@.tk2msftngp13.phx.gbl...
> I've installed MSDE SP3a on a Windows 2000 Server, and the VB6 client
> application on multiple workstations.
> These workstations are either Win2000 Pro or WinXP Pro (both SP1 and SP2).
> All workstations can access and ping the server under 1MS.
> When the client application opens and reads data from the database server,
> it takes a short time for this to be performed on the Win2000 Pro
> machines,
> but all the XP machines take an abnormally long time to connect and to
> retrieve the data.
> The XP's do connect, but the retrieval is very slow, sometimes it timesout
> during a retrieval.
> This occurs even when nobody is connected to the database, so I've ruled
> out
> the governer.
> I'm using ADO to connect and all PC's have MDAC 2.7 or greater.
> The install process only installed MDAC 2.7 if the current version is
> before
> that.
> Anybody have an idea what might be the problem?
> All responses are welcome.
> TIA
> Jim K
>
|||Thanks, I didn't think of that.
I have connected using the IP in other apps, but that was to the default
instance.
Since I have a named instance in this case, how would I format the IP and
instance?
Ex: default instance installed on server SERVER1, I can substitute the IP
for SERVER1
for named instance SERVER1/DB1, how would I format the IP? IP#/DB1 ?
Thanks!
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:u0zukkl7EHA.3124@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Hi Jim,
> Name resolution problems perhaps? Try connecting to the IP address instead
> of the server name to find out.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Jim K" <krusej@.megsinet.net> wrote in message
> news:enMo6BQ7EHA.1596@.tk2msftngp13.phx.gbl...
SP2).[vbcol=seagreen]
server,[vbcol=seagreen]
timesout
>
|||Hi Jim,
I'd suggest setting a fixed port for the named instance, then just connect
to that port. Even set up an alias on the client boxes that knows about the
port. It would completely avoid the sql browser function that essentially
just maps your instance name to a port anyway. To do that:
1. Open svrnetcn.exe and for the named instance, uncheck the "dynamic port"
box and select your own port (ie 38474 or something).
2. Restart the instance.
3. On the client, run cliconfg.exe and set up an alias pointing to that port
on the server.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim K" <krusej@.megsinet.net> wrote in message
news:u6vH8Mo7EHA.2196@.TK2MSFTNGP11.phx.gbl...
> Thanks, I didn't think of that.
> I have connected using the IP in other apps, but that was to the default
> instance.
> Since I have a named instance in this case, how would I format the IP and
> instance?
> Ex: default instance installed on server SERVER1, I can substitute the
> IP
> for SERVER1
> for named instance SERVER1/DB1, how would I format the IP? IP#/DB1 ?
> Thanks!
> "Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
> news:u0zukkl7EHA.3124@.TK2MSFTNGP11.phx.gbl...
> SP2).
> server,
> timesout
>
sql
application on multiple workstations.
These workstations are either Win2000 Pro or WinXP Pro (both SP1 and SP2).
All workstations can access and ping the server under 1MS.
When the client application opens and reads data from the database server,
it takes a short time for this to be performed on the Win2000 Pro machines,
but all the XP machines take an abnormally long time to connect and to
retrieve the data.
The XP's do connect, but the retrieval is very slow, sometimes it timesout
during a retrieval.
This occurs even when nobody is connected to the database, so I've ruled out
the governer.
I'm using ADO to connect and all PC's have MDAC 2.7 or greater.
The install process only installed MDAC 2.7 if the current version is before
that.
Anybody have an idea what might be the problem?
All responses are welcome.
TIA
Jim K
Hi Jim,
Name resolution problems perhaps? Try connecting to the IP address instead
of the server name to find out.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim K" <krusej@.megsinet.net> wrote in message
news:enMo6BQ7EHA.1596@.tk2msftngp13.phx.gbl...
> I've installed MSDE SP3a on a Windows 2000 Server, and the VB6 client
> application on multiple workstations.
> These workstations are either Win2000 Pro or WinXP Pro (both SP1 and SP2).
> All workstations can access and ping the server under 1MS.
> When the client application opens and reads data from the database server,
> it takes a short time for this to be performed on the Win2000 Pro
> machines,
> but all the XP machines take an abnormally long time to connect and to
> retrieve the data.
> The XP's do connect, but the retrieval is very slow, sometimes it timesout
> during a retrieval.
> This occurs even when nobody is connected to the database, so I've ruled
> out
> the governer.
> I'm using ADO to connect and all PC's have MDAC 2.7 or greater.
> The install process only installed MDAC 2.7 if the current version is
> before
> that.
> Anybody have an idea what might be the problem?
> All responses are welcome.
> TIA
> Jim K
>
|||Thanks, I didn't think of that.
I have connected using the IP in other apps, but that was to the default
instance.
Since I have a named instance in this case, how would I format the IP and
instance?
Ex: default instance installed on server SERVER1, I can substitute the IP
for SERVER1
for named instance SERVER1/DB1, how would I format the IP? IP#/DB1 ?
Thanks!
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:u0zukkl7EHA.3124@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Hi Jim,
> Name resolution problems perhaps? Try connecting to the IP address instead
> of the server name to find out.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Jim K" <krusej@.megsinet.net> wrote in message
> news:enMo6BQ7EHA.1596@.tk2msftngp13.phx.gbl...
SP2).[vbcol=seagreen]
server,[vbcol=seagreen]
timesout
>
|||Hi Jim,
I'd suggest setting a fixed port for the named instance, then just connect
to that port. Even set up an alias on the client boxes that knows about the
port. It would completely avoid the sql browser function that essentially
just maps your instance name to a port anyway. To do that:
1. Open svrnetcn.exe and for the named instance, uncheck the "dynamic port"
box and select your own port (ie 38474 or something).
2. Restart the instance.
3. On the client, run cliconfg.exe and set up an alias pointing to that port
on the server.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim K" <krusej@.megsinet.net> wrote in message
news:u6vH8Mo7EHA.2196@.TK2MSFTNGP11.phx.gbl...
> Thanks, I didn't think of that.
> I have connected using the IP in other apps, but that was to the default
> instance.
> Since I have a named instance in this case, how would I format the IP and
> instance?
> Ex: default instance installed on server SERVER1, I can substitute the
> IP
> for SERVER1
> for named instance SERVER1/DB1, how would I format the IP? IP#/DB1 ?
> Thanks!
> "Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
> news:u0zukkl7EHA.3124@.TK2MSFTNGP11.phx.gbl...
> SP2).
> server,
> timesout
>
sql
Wednesday, March 28, 2012
MSDE 2000 SP4 Merge Modules
I have a MSDE 2000 InstallShield install package that I've created using the
merge modules. I downloaded the SP4 of the desktop engine from the microsoft
site. When downloaded and extracted, there is a folder on my machine
\MSDE\MSM which has all of the merge modules. I've noticed that the SP4
release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and qfepatch.msm.
In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I go
and build I receive the following error: "Error retrieving dependency
MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
why I'm getting this error?
Thanks.
Joanne
hi Joanne
jbayog wrote:
> I have a MSDE 2000 InstallShield install package that I've created
> using the merge modules. I downloaded the SP4 of the desktop engine
> from the microsoft site. When downloaded and extracted, there is a
> folder on my machine \MSDE\MSM which has all of the merge modules.
> I've noticed that the SP4 release has 3 new mm's: msxmlsql32.msm,
> msxmlsqlr32.msm, and qfepatch.msm. In the InstallShield DevStudio
> 9.01 IDE, I check the 3 new mm's. When I go and build I receive the
> following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone
> know why I'm getting this error?
no idea, never used MSDE merge modules, always installed using the setup.exe
boostrap installer.... but have you tried modifying the order of
installation?
http://msdn.microsoft.com/library/de...stsql_8yeq.asp
has not been updated (as BOL in general) at sp4 level, so no additional info
about those new merge modules seems available..
BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
specifies:
"Note Merge modules are not supported for new installations. They are
provided in SP4 for servicing instances of MSDE 2000 that were previously
installed using merge modules."
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I don't know much about MSDE and am just doing some research on it as of
this week.
However, I cam across this link yesterday which might be useful:
http://www.microsoft.com/sql/downloads/2000/sp4.asp
Here is an extract from the site:
"Users who have an existing instance of MSDE 2000 must know how their
instance of MSDE 2000 was installed to know how to update it. In particular,
you must know the original package name for your instance of MSDE 2000. To
determine the original package name, see the article How To Identify Which
MSI File Was Used for an Existing MSDE Installation in the Microsoft
Knowledge Base."
"jbayog" <jbayog@.discussions.microsoft.com> wrote in message
news:8D058312-1747-4A51-A100-FE79DC32C086@.microsoft.com...
>I have a MSDE 2000 InstallShield install package that I've created using
>the
> merge modules. I downloaded the SP4 of the desktop engine from the
> microsoft
> site. When downloaded and extracted, there is a folder on my machine
> \MSDE\MSM which has all of the merge modules. I've noticed that the SP4
> release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and
> qfepatch.msm.
> In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I
> go
> and build I receive the following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
> why I'm getting this error?
> Thanks.
> Joanne
|||Thanks so much for your help. This an existing MSDE 2000 InstallShield
install package and we have a client who wants to upgrade to SP4 so that is
why I'm trying to build an upgrade for them. I'd like to get rid of using
the MSDE 2000 merge modules per Microsoft's comment. I got it to build by
editing the msxmlsql32.msm and the msxmlsqlr32.msm using the Orca tool. I
think there is a problem with the rows in the ModuleDependency table. I
guess I have the option of building it without these two mm's as our database
application doesn't use xml. I'm a little apprehensive of doing this only
because there is no documentation on these new mm's. I might post to
InstallShield also. Again thanks.
Joanne
Joanne
"Andrea Montanari" wrote:
> hi Joanne
> jbayog wrote:
> no idea, never used MSDE merge modules, always installed using the setup.exe
> boostrap installer.... but have you tried modifying the order of
> installation?
> http://msdn.microsoft.com/library/de...stsql_8yeq.asp
> has not been updated (as BOL in general) at sp4 level, so no additional info
> about those new merge modules seems available..
> BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
> specifies:
> "Note Merge modules are not supported for new installations. They are
> provided in SP4 for servicing instances of MSDE 2000 that were previously
> installed using merge modules."
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
merge modules. I downloaded the SP4 of the desktop engine from the microsoft
site. When downloaded and extracted, there is a folder on my machine
\MSDE\MSM which has all of the merge modules. I've noticed that the SP4
release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and qfepatch.msm.
In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I go
and build I receive the following error: "Error retrieving dependency
MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
why I'm getting this error?
Thanks.
Joanne
hi Joanne
jbayog wrote:
> I have a MSDE 2000 InstallShield install package that I've created
> using the merge modules. I downloaded the SP4 of the desktop engine
> from the microsoft site. When downloaded and extracted, there is a
> folder on my machine \MSDE\MSM which has all of the merge modules.
> I've noticed that the SP4 release has 3 new mm's: msxmlsql32.msm,
> msxmlsqlr32.msm, and qfepatch.msm. In the InstallShield DevStudio
> 9.01 IDE, I check the 3 new mm's. When I go and build I receive the
> following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone
> know why I'm getting this error?
no idea, never used MSDE merge modules, always installed using the setup.exe
boostrap installer.... but have you tried modifying the order of
installation?
http://msdn.microsoft.com/library/de...stsql_8yeq.asp
has not been updated (as BOL in general) at sp4 level, so no additional info
about those new merge modules seems available..
BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
specifies:
"Note Merge modules are not supported for new installations. They are
provided in SP4 for servicing instances of MSDE 2000 that were previously
installed using merge modules."
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I don't know much about MSDE and am just doing some research on it as of
this week.
However, I cam across this link yesterday which might be useful:
http://www.microsoft.com/sql/downloads/2000/sp4.asp
Here is an extract from the site:
"Users who have an existing instance of MSDE 2000 must know how their
instance of MSDE 2000 was installed to know how to update it. In particular,
you must know the original package name for your instance of MSDE 2000. To
determine the original package name, see the article How To Identify Which
MSI File Was Used for an Existing MSDE Installation in the Microsoft
Knowledge Base."
"jbayog" <jbayog@.discussions.microsoft.com> wrote in message
news:8D058312-1747-4A51-A100-FE79DC32C086@.microsoft.com...
>I have a MSDE 2000 InstallShield install package that I've created using
>the
> merge modules. I downloaded the SP4 of the desktop engine from the
> microsoft
> site. When downloaded and extracted, there is a folder on my machine
> \MSDE\MSM which has all of the merge modules. I've noticed that the SP4
> release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and
> qfepatch.msm.
> In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I
> go
> and build I receive the following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
> why I'm getting this error?
> Thanks.
> Joanne
|||Thanks so much for your help. This an existing MSDE 2000 InstallShield
install package and we have a client who wants to upgrade to SP4 so that is
why I'm trying to build an upgrade for them. I'd like to get rid of using
the MSDE 2000 merge modules per Microsoft's comment. I got it to build by
editing the msxmlsql32.msm and the msxmlsqlr32.msm using the Orca tool. I
think there is a problem with the rows in the ModuleDependency table. I
guess I have the option of building it without these two mm's as our database
application doesn't use xml. I'm a little apprehensive of doing this only
because there is no documentation on these new mm's. I might post to
InstallShield also. Again thanks.
Joanne
Joanne
"Andrea Montanari" wrote:
> hi Joanne
> jbayog wrote:
> no idea, never used MSDE merge modules, always installed using the setup.exe
> boostrap installer.... but have you tried modifying the order of
> installation?
> http://msdn.microsoft.com/library/de...stsql_8yeq.asp
> has not been updated (as BOL in general) at sp4 level, so no additional info
> about those new merge modules seems available..
> BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
> specifies:
> "Note Merge modules are not supported for new installations. They are
> provided in SP4 for servicing instances of MSDE 2000 that were previously
> installed using merge modules."
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
Monday, March 26, 2012
MSDE 2000 Release A
I just installed MSDE 2000 Release A. I expected to see an icon in the
system try which lets you start and stop msde. I've seen this before,
but it didn't appear on my machine. Can I get this icon to appear
somehow ? Thanks...
hi,
mberger@.skypoint.com wrote:
> I just installed MSDE 2000 Release A. I expected to see an icon in the
> system try which lets you start and stop msde. I've seen this before,
> but it didn't appear on my machine. Can I get this icon to appear
> somehow ? Thanks...
the icon in the systray area should be there, if you correctly installed
MSDE... it can be empty becouse of network protocols status, as reported in
http://support.microsoft.com/default...b;EN-US;814132 ..
if you can't find the Service Manager icon in the tray area, please verify
the service has been correctly installed checking the Services applet in the
OS management tools..
if it's there, up and running (:D) verify in your the "Startup" folder the
presence of the Service Manager entry, usually pointing to
"C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmangr.exe" /n
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea, the Service Manager was in my Startup, and clicking on
that caused the icon to show in the system tray. Then, I re-booted, and
the icon showed up. (I had not re-booted after installation)
Mike
system try which lets you start and stop msde. I've seen this before,
but it didn't appear on my machine. Can I get this icon to appear
somehow ? Thanks...
hi,
mberger@.skypoint.com wrote:
> I just installed MSDE 2000 Release A. I expected to see an icon in the
> system try which lets you start and stop msde. I've seen this before,
> but it didn't appear on my machine. Can I get this icon to appear
> somehow ? Thanks...
the icon in the systray area should be there, if you correctly installed
MSDE... it can be empty becouse of network protocols status, as reported in
http://support.microsoft.com/default...b;EN-US;814132 ..
if you can't find the Service Manager icon in the tray area, please verify
the service has been correctly installed checking the Services applet in the
OS management tools..
if it's there, up and running (:D) verify in your the "Startup" folder the
presence of the Service Manager entry, usually pointing to
"C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmangr.exe" /n
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea, the Service Manager was in my Startup, and clicking on
that caused the icon to show in the system tray. Then, I re-booted, and
the icon showed up. (I had not re-booted after installation)
Mike
Friday, March 23, 2012
MSDE 2000 database setup trouble
Hello
I am running a stand-alone test environment for an application in XP Pro
which I can only use MSDE to manage my databases.
I've successfully installed msde and am finally able to connect using 'osql
-Usa -Ppassword -S (local)\testmachine' , because I can get the '1>' command
prompt.
My trouble is when I try to create and/or restore a database for the test
application to use I'm running into trouble. For example enter this :
1> USE master
2> RESTORE DATABASE master FROM DISK='C:\master\master_db2.BAK'
3>GO
and I get an error message telling me that "RESTORE DATABASE must be used in
single user mode when trying to restore the master database" ...... I also
get a similar message when trying to create and restore a database called
'public'.
how do I successfully get into 'single user mode' ?
hi,
APB wrote:
> Hello
> I am running a stand-alone test environment for an application in XP
> Pro which I can only use MSDE to manage my databases.
> I've successfully installed msde and am finally able to connect using
> 'osql -Usa -Ppassword -S (local)\testmachine' , because I can get the
> '1>' command prompt.
> My trouble is when I try to create and/or restore a database for the
> test application to use I'm running into trouble. For example enter
> this :
> 1> USE master
> 2> RESTORE DATABASE master FROM DISK='C:\master\master_db2.BAK'
> 3>GO
> and I get an error message telling me that "RESTORE DATABASE must be
> used in single user mode when trying to restore the master database"
> ...... I also get a similar message when trying to create and
> restore a database called 'public'.
> how do I successfully get into 'single user mode' ?
have a look at http://msdn2.microsoft.com/en-us/library/ms180965.aspx ..
typically you open a command window, navigate to the \Binn folder of the
instance you want to start and execute something like
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\>sqlservr.exe -s
InstanceName -m
this will start the instance in single user modo, so that you'll be able to
restore the master database...
to restore "normal user's" database(s) the single user mode is not required,
but the database(s) to be restored must not be in use... so no active
connections must be running against the database(s) to be restored..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
-- remove DMO to reply
I am running a stand-alone test environment for an application in XP Pro
which I can only use MSDE to manage my databases.
I've successfully installed msde and am finally able to connect using 'osql
-Usa -Ppassword -S (local)\testmachine' , because I can get the '1>' command
prompt.
My trouble is when I try to create and/or restore a database for the test
application to use I'm running into trouble. For example enter this :
1> USE master
2> RESTORE DATABASE master FROM DISK='C:\master\master_db2.BAK'
3>GO
and I get an error message telling me that "RESTORE DATABASE must be used in
single user mode when trying to restore the master database" ...... I also
get a similar message when trying to create and restore a database called
'public'.
how do I successfully get into 'single user mode' ?
hi,
APB wrote:
> Hello
> I am running a stand-alone test environment for an application in XP
> Pro which I can only use MSDE to manage my databases.
> I've successfully installed msde and am finally able to connect using
> 'osql -Usa -Ppassword -S (local)\testmachine' , because I can get the
> '1>' command prompt.
> My trouble is when I try to create and/or restore a database for the
> test application to use I'm running into trouble. For example enter
> this :
> 1> USE master
> 2> RESTORE DATABASE master FROM DISK='C:\master\master_db2.BAK'
> 3>GO
> and I get an error message telling me that "RESTORE DATABASE must be
> used in single user mode when trying to restore the master database"
> ...... I also get a similar message when trying to create and
> restore a database called 'public'.
> how do I successfully get into 'single user mode' ?
have a look at http://msdn2.microsoft.com/en-us/library/ms180965.aspx ..
typically you open a command window, navigate to the \Binn folder of the
instance you want to start and execute something like
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\>sqlservr.exe -s
InstanceName -m
this will start the instance in single user modo, so that you'll be able to
restore the master database...
to restore "normal user's" database(s) the single user mode is not required,
but the database(s) to be restored must not be in use... so no active
connections must be running against the database(s) to be restored..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
-- remove DMO to reply
Wednesday, March 21, 2012
MSDE 1.0 TO MSDE 2000 Release A
I've used MSDE 1.0 for a number of years.
Today I downloaded Release A with the intention of installing it, but when I
attempt to run Setup I get a dialog saying "The instance name specified is
invalid." What could be causing this?
Also... what impact will an installation of MSDE 2000 have on my existing
MSDE 1.0 databases? Is there a procedure I should be following?
Thanks in advance.
Nancy
hi Nancy,
"Nancy Lorieau" <NancyLorieau@.discussions.microsoft.com> ha scritto nel
messaggio news:81D8BF32-88C8-4F0C-AE24-0C8BCC213BC5@.microsoft.com...
> I've used MSDE 1.0 for a number of years.
> Today I downloaded Release A with the intention of installing it, but when
I
> attempt to run Setup I get a dialog saying "The instance name specified is
> invalid." What could be causing this?
>
personally I never "upgraded" MSDE 1.0 instance to MSDE 2000 ... I always
backedup the users database and restored them on the MSDE2000 new instance
after uninstalling MSDE 1.0.. but I had no reason to maintain the MSDE 1.0
instance at all...
anyway,
http://msdn.microsoft.com/library/de...stsql_84xl.asp
reports you have to add the
UPGRADE=1 UPGRADEUSER=username UPGRADEPWD=userpwd
commandline parameters to your call to the setup.exe bootstrap installer...
> Also... what impact will an installation of MSDE 2000 have on my existing
> MSDE 1.0 databases? Is there a procedure I should be following?
the users databases will be upgraded to MSDE 2000 level... you coul'd be
affected by cross database ownership chaining, which behaviour has been
changed... further info at
http://msdn.microsoft.com/library/de...onfig_8d7m.asp
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
Today I downloaded Release A with the intention of installing it, but when I
attempt to run Setup I get a dialog saying "The instance name specified is
invalid." What could be causing this?
Also... what impact will an installation of MSDE 2000 have on my existing
MSDE 1.0 databases? Is there a procedure I should be following?
Thanks in advance.
Nancy
hi Nancy,
"Nancy Lorieau" <NancyLorieau@.discussions.microsoft.com> ha scritto nel
messaggio news:81D8BF32-88C8-4F0C-AE24-0C8BCC213BC5@.microsoft.com...
> I've used MSDE 1.0 for a number of years.
> Today I downloaded Release A with the intention of installing it, but when
I
> attempt to run Setup I get a dialog saying "The instance name specified is
> invalid." What could be causing this?
>
personally I never "upgraded" MSDE 1.0 instance to MSDE 2000 ... I always
backedup the users database and restored them on the MSDE2000 new instance
after uninstalling MSDE 1.0.. but I had no reason to maintain the MSDE 1.0
instance at all...
anyway,
http://msdn.microsoft.com/library/de...stsql_84xl.asp
reports you have to add the
UPGRADE=1 UPGRADEUSER=username UPGRADEPWD=userpwd
commandline parameters to your call to the setup.exe bootstrap installer...
> Also... what impact will an installation of MSDE 2000 have on my existing
> MSDE 1.0 databases? Is there a procedure I should be following?
the users databases will be upgraded to MSDE 2000 level... you coul'd be
affected by cross database ownership chaining, which behaviour has been
changed... further info at
http://msdn.microsoft.com/library/de...onfig_8d7m.asp
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
Monday, March 19, 2012
MSDE / SQL Express Question
what is the limitation in terms of connections? I've read something along
the lines of 5-10 connections?
MSDE had a 5 concurrent connection 'governor. With SQL Server 2005 Express,
the governor has been removed, and the limit is mostly related to the type
of activity and hardware. Of course, there will be some relationship with
and processor/memory/disk subsystem -up to the limits.
With low to moderate frequency activity (small packets) in a small OLTP
database, you might be able to adequately support 20-30 users. Large
resultsets in a OLAP may only support 1-5 users. Plan to thoroughly test any
implementation.
See specifications at:
http://www.microsoft.com/sql/prodinf...-features.mspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"g" <gregoranton_nospamplease_@.hotmail.com> wrote in message
news:8pIPg.24564$Lb5.16987@.edtnps89...
> what is the limitation in terms of connections? I've read something along
> the lines of 5-10 connections?
>
|||On Tue, 19 Sep 2006 02:15:32 GMT, g wrote:
>what is the limitation in terms of connections? I've read something along
>the lines of 5-10 connections?
>
Hi g,
In addition to Arnie's answer: the MSDE workload governor limits
concurrent _WORKLOADS_, not connections. An idle connection is not a
workload, a working connection is. Some connections might even spawn
multiple workloads. So ten, twenty, fifty or even hundred data entry
typists coould all simultaneously be connected to MSDE without ever
hitting the 5-workload limit. But one carefully architected procedure
that spawns multiple connections (not easy to do, but possible) could
bring MSDE to it's knees all by itself.
Oh, and if you surpass the maximum of 5 concurrent workloads, the effect
will be that the workload governor starts to throttle performance. A bit
if you have only 6 workloads, but progressively more as the number of
workloads increases - effectively, MSDE will slow down to an almost halt
if you keep increasing concurrent workloads.
Hugo Kornelis, SQL Server MVP
the lines of 5-10 connections?
MSDE had a 5 concurrent connection 'governor. With SQL Server 2005 Express,
the governor has been removed, and the limit is mostly related to the type
of activity and hardware. Of course, there will be some relationship with
and processor/memory/disk subsystem -up to the limits.
With low to moderate frequency activity (small packets) in a small OLTP
database, you might be able to adequately support 20-30 users. Large
resultsets in a OLAP may only support 1-5 users. Plan to thoroughly test any
implementation.
See specifications at:
http://www.microsoft.com/sql/prodinf...-features.mspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"g" <gregoranton_nospamplease_@.hotmail.com> wrote in message
news:8pIPg.24564$Lb5.16987@.edtnps89...
> what is the limitation in terms of connections? I've read something along
> the lines of 5-10 connections?
>
|||On Tue, 19 Sep 2006 02:15:32 GMT, g wrote:
>what is the limitation in terms of connections? I've read something along
>the lines of 5-10 connections?
>
Hi g,
In addition to Arnie's answer: the MSDE workload governor limits
concurrent _WORKLOADS_, not connections. An idle connection is not a
workload, a working connection is. Some connections might even spawn
multiple workloads. So ten, twenty, fifty or even hundred data entry
typists coould all simultaneously be connected to MSDE without ever
hitting the 5-workload limit. But one carefully architected procedure
that spawns multiple connections (not easy to do, but possible) could
bring MSDE to it's knees all by itself.
Oh, and if you surpass the maximum of 5 concurrent workloads, the effect
will be that the workload governor starts to throttle performance. A bit
if you have only 6 workloads, but progressively more as the number of
workloads increases - effectively, MSDE will slow down to an almost halt
if you keep increasing concurrent workloads.
Hugo Kornelis, SQL Server MVP
Monday, March 12, 2012
MSDE - MSSQL$MICROSOFTSMLBIZ ?
I need to work with MSDE on a new laptop ive been given. Apparently msde is already installed. I have a service runningnamed "MSSQL$MICROSOFTSMLBIZ" - how do i configure it, or shouldI just download a later copy of msde and setup a new copy ? Iknow I know...use sql express. However, I need to work with msdein this case to make it easier (on me) for moving the data into a sql2000 database.
thanks
So you have SQL2000 instance? Then you can register the MSDE instance in Enterprise Manager, thus it should be much easier to manage the MSDE databases: Open Enterprise Manager->right click a SQL Server Group->choose New SQL Server Registration.
Otherwise you have to use osql utility to manage MSDE, which would be painful if you're not familiar with T-SQL.
Friday, March 9, 2012
MSDE - Failed to configure server
I've been looking into this all day and haven't gotten anywhere. I'm using
InstallShield to install a .Net application, the application uses MSDE as
its database. I've added InstallShield's MSDE object to the install, works
fine sometimes but most of the time I get the following error message when
the MSDE is almost installed.
"Setup failed to configure the server. Refer to the server error logs and
setup errors for more information."
I've scoured the internet looking into this error and nothing seems to
correct this issue. I've remove all files, registry keys and anything
related to MSDE and I still get the same error.
Thanks in advance,
Dave
Have you tried installing MSDE using the file available for download from
Microsoft?
Linda
"Dave" <dave.golightly@.stgutah.com> wrote in message
news:uDSjGMDzEHA.2568@.TK2MSFTNGP10.phx.gbl...
> I've been looking into this all day and haven't gotten anywhere. I'm
> using
> InstallShield to install a .Net application, the application uses MSDE as
> its database. I've added InstallShield's MSDE object to the install,
> works
> fine sometimes but most of the time I get the following error message when
> the MSDE is almost installed.
> "Setup failed to configure the server. Refer to the server error logs and
> setup errors for more information."
> I've scoured the internet looking into this error and nothing seems to
> correct this issue. I've remove all files, registry keys and anything
> related to MSDE and I still get the same error.
> Thanks in advance,
> Dave
>
>
|||Have you tried installing MSDE using the file available for download from
Microsoft?
Linda
"Dave" <dave.golightly@.stgutah.com> wrote in message
news:uDSjGMDzEHA.2568@.TK2MSFTNGP10.phx.gbl...
> I've been looking into this all day and haven't gotten anywhere. I'm
> using
> InstallShield to install a .Net application, the application uses MSDE as
> its database. I've added InstallShield's MSDE object to the install,
> works
> fine sometimes but most of the time I get the following error message when
> the MSDE is almost installed.
> "Setup failed to configure the server. Refer to the server error logs and
> setup errors for more information."
> I've scoured the internet looking into this error and nothing seems to
> correct this issue. I've remove all files, registry keys and anything
> related to MSDE and I still get the same error.
> Thanks in advance,
> Dave
>
>
InstallShield to install a .Net application, the application uses MSDE as
its database. I've added InstallShield's MSDE object to the install, works
fine sometimes but most of the time I get the following error message when
the MSDE is almost installed.
"Setup failed to configure the server. Refer to the server error logs and
setup errors for more information."
I've scoured the internet looking into this error and nothing seems to
correct this issue. I've remove all files, registry keys and anything
related to MSDE and I still get the same error.
Thanks in advance,
Dave
Have you tried installing MSDE using the file available for download from
Microsoft?
Linda
"Dave" <dave.golightly@.stgutah.com> wrote in message
news:uDSjGMDzEHA.2568@.TK2MSFTNGP10.phx.gbl...
> I've been looking into this all day and haven't gotten anywhere. I'm
> using
> InstallShield to install a .Net application, the application uses MSDE as
> its database. I've added InstallShield's MSDE object to the install,
> works
> fine sometimes but most of the time I get the following error message when
> the MSDE is almost installed.
> "Setup failed to configure the server. Refer to the server error logs and
> setup errors for more information."
> I've scoured the internet looking into this error and nothing seems to
> correct this issue. I've remove all files, registry keys and anything
> related to MSDE and I still get the same error.
> Thanks in advance,
> Dave
>
>
|||Have you tried installing MSDE using the file available for download from
Microsoft?
Linda
"Dave" <dave.golightly@.stgutah.com> wrote in message
news:uDSjGMDzEHA.2568@.TK2MSFTNGP10.phx.gbl...
> I've been looking into this all day and haven't gotten anywhere. I'm
> using
> InstallShield to install a .Net application, the application uses MSDE as
> its database. I've added InstallShield's MSDE object to the install,
> works
> fine sometimes but most of the time I get the following error message when
> the MSDE is almost installed.
> "Setup failed to configure the server. Refer to the server error logs and
> setup errors for more information."
> I've scoured the internet looking into this error and nothing seems to
> correct this issue. I've remove all files, registry keys and anything
> related to MSDE and I still get the same error.
> Thanks in advance,
> Dave
>
>
Wednesday, March 7, 2012
MSDE
I've been tasked to find all servers running sql and msde. I've used the
sqlping utility. 1. Does anyone know if the sqlping utility will pick up
the msde? 2. How do I determine the license agreement for the instance of
sql running? 3. Is there a better way to do this?
Thanks
Hi
"brymer28303" wrote:
> I've been tasked to find all servers running sql and msde. I've used the
> sqlping utility. 1. Does anyone know if the sqlping utility will pick up
> the msde? 2. How do I determine the license agreement for the instance of
> sql running? 3. Is there a better way to do this?
> Thanks
Try using SQLRecon
http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx which will
try to use a number of ways to discover if SQL Server is present.
You may want to try your own tests by enabling/disabling the network
protocols on your MSDE instance.
John
sqlping utility. 1. Does anyone know if the sqlping utility will pick up
the msde? 2. How do I determine the license agreement for the instance of
sql running? 3. Is there a better way to do this?
Thanks
Hi
"brymer28303" wrote:
> I've been tasked to find all servers running sql and msde. I've used the
> sqlping utility. 1. Does anyone know if the sqlping utility will pick up
> the msde? 2. How do I determine the license agreement for the instance of
> sql running? 3. Is there a better way to do this?
> Thanks
Try using SQLRecon
http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx which will
try to use a number of ways to discover if SQL Server is present.
You may want to try your own tests by enabling/disabling the network
protocols on your MSDE instance.
John
Saturday, February 25, 2012
msdb refuses to back up w/ plan
All,
I've created (and re-created) a Mx plan for the system databases.
Part of it is a complete backup. All the default options in the
wizard were chosen, including the option to verify.
Master and Model back up fine. MSDB, however, fails. According to
the Mx Plan log, the backup completes successfully, but the verify
fails as follows:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup
device 'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042207.BAK '. Device
error or device off-line. See the SQL Server error log for more
details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
terminating abnormally.
1- It doesn't appear that the backup actually succeeded, as there is
no msdb_db_200407042207.bak file in the directory.
2- There is no additional information in the SQL Server error log
3- I can successfully back up msdb -manually- without a hiccup.
I've tried:
1- Recreating a new Mx Plan from scratch (no effect)
2- Can full index/optimizations on msdb (no errors found)
3- Tried shrinking the database (it's 215MBish) to make it faster
4- Tried a full backup/restore of msdb in case it had any mystery
corruption (no effect)
Oh yes, SQL Server standard 2000 sp3 on W2.3K standard. NTFS
partition. SQL Agent using a domain account, SQL Server running under
the same account.
Can anyone shed light on this? I can come up with no reason why the
Mx plan would fail for just this one database, when I can back it up
just fine manually.
Geof
Here's some more info:
I did find some additional information in the app event log, giving the specific T-SQL that was failing:
BACKUP DATABASE [msdb] TO DISK = N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BA K' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
After some pondering and re-reading my own post, I went ahead and logged into the server interactively using SQL Server's account. I attempted to execute the above SQL and lo and behond, it failed (General Network Error). When executed under my normal U
serID, it executed fine.
Trial and error then produced the rather odd discovery that the problem part of the statement is the seemingly innocuous "STATS=10" command. If the same statement is run under the SQL Server account EXCEPT for removing the stats=10 command, it works fine
|||Go the Maintenance Plan and right click and view maintenance history out
there ...Thats where most of the reasoning is for the failure..
"Geof" <Geof@.discussions.microsoft.com> wrote in message
news:C6436F94-BF81-41FD-9869-5595F7FBA6B4@.microsoft.com...
> Here's some more info:
> I did find some additional information in the app event log, giving the
specific T-SQL that was failing:
> BACKUP DATABASE [msdb] TO DISK =
N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BA K' WITH INIT , NOUNLOAD
, NOSKIP , STATS = 10, NOFORMAT
> After some pondering and re-reading my own post, I went ahead and logged
into the server interactively using SQL Server's account. I attempted to
execute the above SQL and lo and behond, it failed (General Network Error).
When executed under my normal UserID, it executed fine.
> Trial and error then produced the rather odd discovery that the problem
part of the statement is the seemingly innocuous "STATS=10" command. If the
same statement is run under the SQL Server account EXCEPT for removing the
stats=10 command, it works fine.
> While I've gotten more information on exactly what is causing the problem,
I:
> 1- Have no idea why the problem is occurring, and
> 2- Don't know a way around it (other than backup w/o using a Mx Plan)
> My nearest stab would be that this particular T-SQL (and STATS option in
particular) is causing some sort of collision between SQL Server and SQL
Server Agent since they would both be running under the same account. (But
surely I'm not the only one in the history of SQL Server to have created a
sysdb mx plan w/ both SQL and SQL Agent running under an identical domain
account, huh?)
> Ideas?
|||In my first post I listed what was in the Mx Plan History. Does
anyone have any other ideas?
Geof
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:<#GDGyveYEHA.996@.TK2MSFTNGP12.phx.gbl>...
> Go the Maintenance Plan and right click and view maintenance history out
> there ...Thats where most of the reasoning is for the failure..
I've created (and re-created) a Mx plan for the system databases.
Part of it is a complete backup. All the default options in the
wizard were chosen, including the option to verify.
Master and Model back up fine. MSDB, however, fails. According to
the Mx Plan log, the backup completes successfully, but the verify
fails as follows:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup
device 'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042207.BAK '. Device
error or device off-line. See the SQL Server error log for more
details.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
terminating abnormally.
1- It doesn't appear that the backup actually succeeded, as there is
no msdb_db_200407042207.bak file in the directory.
2- There is no additional information in the SQL Server error log
3- I can successfully back up msdb -manually- without a hiccup.
I've tried:
1- Recreating a new Mx Plan from scratch (no effect)
2- Can full index/optimizations on msdb (no errors found)
3- Tried shrinking the database (it's 215MBish) to make it faster
4- Tried a full backup/restore of msdb in case it had any mystery
corruption (no effect)
Oh yes, SQL Server standard 2000 sp3 on W2.3K standard. NTFS
partition. SQL Agent using a domain account, SQL Server running under
the same account.
Can anyone shed light on this? I can come up with no reason why the
Mx plan would fail for just this one database, when I can back it up
just fine manually.
Geof
Here's some more info:
I did find some additional information in the app event log, giving the specific T-SQL that was failing:
BACKUP DATABASE [msdb] TO DISK = N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BA K' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
After some pondering and re-reading my own post, I went ahead and logged into the server interactively using SQL Server's account. I attempted to execute the above SQL and lo and behond, it failed (General Network Error). When executed under my normal U
serID, it executed fine.
Trial and error then produced the rather odd discovery that the problem part of the statement is the seemingly innocuous "STATS=10" command. If the same statement is run under the SQL Server account EXCEPT for removing the stats=10 command, it works fine
|||Go the Maintenance Plan and right click and view maintenance history out
there ...Thats where most of the reasoning is for the failure..
"Geof" <Geof@.discussions.microsoft.com> wrote in message
news:C6436F94-BF81-41FD-9869-5595F7FBA6B4@.microsoft.com...
> Here's some more info:
> I did find some additional information in the app event log, giving the
specific T-SQL that was failing:
> BACKUP DATABASE [msdb] TO DISK =
N'd:\sql_data\MSSQL\BACKUP\msdb_db_200407042238.BA K' WITH INIT , NOUNLOAD
, NOSKIP , STATS = 10, NOFORMAT
> After some pondering and re-reading my own post, I went ahead and logged
into the server interactively using SQL Server's account. I attempted to
execute the above SQL and lo and behond, it failed (General Network Error).
When executed under my normal UserID, it executed fine.
> Trial and error then produced the rather odd discovery that the problem
part of the statement is the seemingly innocuous "STATS=10" command. If the
same statement is run under the SQL Server account EXCEPT for removing the
stats=10 command, it works fine.
> While I've gotten more information on exactly what is causing the problem,
I:
> 1- Have no idea why the problem is occurring, and
> 2- Don't know a way around it (other than backup w/o using a Mx Plan)
> My nearest stab would be that this particular T-SQL (and STATS option in
particular) is causing some sort of collision between SQL Server and SQL
Server Agent since they would both be running under the same account. (But
surely I'm not the only one in the history of SQL Server to have created a
sysdb mx plan w/ both SQL and SQL Agent running under an identical domain
account, huh?)
> Ideas?
|||In my first post I listed what was in the Mx Plan History. Does
anyone have any other ideas?
Geof
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:<#GDGyveYEHA.996@.TK2MSFTNGP12.phx.gbl>...
> Go the Maintenance Plan and right click and view maintenance history out
> there ...Thats where most of the reasoning is for the failure..
Subscribe to:
Posts (Atom)