MSDE

Hi
Trying to install Microsoft SQL Server 2000 Service Pack 4 on Win XP machine.
MSDE 2000 Sp3 already installed on D: drive, instance name= db1
In enterprise manager the db appears as ABC-111\DB1
ABC-111 is the name of the machine
I am using mixed authentication mode.
After reading the help I came up with this to install sp4:
setup /upgradesp sqlrun instancename="db1" securitymode=sql upgradeuser=sa
upgradepwd=sapw /L*v C:\MSDELog.log
I have also tried having instancename="ABC-111\DB1" but always the same error:
This product is not installed. Check is a appropriate instance of MSDE is
installed.
Now, note that the MSDE is installed here on my machine:
D:\Program Files\MSDE\MSSQL$DB1
Could that possible affect this?
I noticed when I looked in the registry that I did not find what the readme
file described, still, the database has been running smoothly for months...
Any hints somebody?
gst Valgar wrote:
> Hi
> Trying to install Microsoft SQL Server 2000 Service Pack 4 on Win XP
> machine. MSDE 2000 Sp3 already installed on D: drive, instance name=
> db1
> In enterprise manager the db appears as ABC-111\DB1
> ABC-111 is the name of the machine
> I am using mixed authentication mode.
> After reading the help I came up with this to install sp4:
> --
> setup /upgradesp sqlrun instancename="db1" securitymode=sql
> upgradeuser=sa upgradepwd=sapw /L*v C:\MSDELog.log
try setup /upgradesp sqlrun instancename=db1 securitymode=sql upgradeuser=sa
upgradepwd=sapw /L*v C:\MSDELog.log
without quotes...
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
|||The error pervails...
"Andrea Montanari" wrote:

> ágúst Valgare wrote:
> try setup /upgradesp sqlrun instancename=db1 securitymode=sql upgradeuser=sa
> upgradepwd=sapw /L*v C:\MSDELog.log
> without quotes...
> --
> 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
>
>
|||Sorry, my mistake, this seems to work, thank you!
"ágúst Valgare" wrote:
[vbcol=seagreen]
> The error pervails...
> "Andrea Montanari" wrote:

msdb.dbo.sysdbmaintplan_history table question

Hi,
I am trying to check that a backup integrity check has verified a log
backup because it is being done over a network drive.
There is an entry verify backup for each backup performed in the
msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
correct one I should be looking at to see if RESTORE VERIFYONLY
succeeded ?
My question is how do I tell that a verification found an error?
Thanks
--SamMaint plan executed RESTORE VERIFYONLY. It will produce errors of such are f
ound. Make sure you
handle the job so your are notified if errors occurs.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message news:1147179633.997410.37830@.j73g2000cwa.googlegroup
s.com...
> Hi,
> I am trying to check that a backup integrity check has verified a log
> backup because it is being done over a network drive.
> There is an entry verify backup for each backup performed in the
> msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
> correct one I should be looking at to see if RESTORE VERIFYONLY
> succeeded ?
> My question is how do I tell that a verification found an error?
> Thanks
> --Sam
>|||Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_histor=ADy has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_histor=ADy table ?
Many Thanks
--Sam|||I don't know, I'm afraid. I'd guess that Maint plans are smart enough to mar
k the execution as
failed and log the errors returned by RESTORE VERIFYONLY. I don't use maint
plans myself, as I
prefer more control over these things. Perhaps you can try, for instance doi
ng the backup to the
"nul" file name?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message
news:1147180762.992024.182010@.u72g2000cwu.googlegroups.com...
Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_histor_y has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_histor_y table ?
Many Thanks
--Sam

msdb.dbo.sysdbmaintplan_history table question

Hi,
I am trying to check that a backup integrity check has verified a log
backup because it is being done over a network drive.
There is an entry verify backup for each backup performed in the
msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
correct one I should be looking at to see if RESTORE VERIFYONLY
succeeded ?
My question is how do I tell that a verification found an error?
Thanks
--SamMaint plan executed RESTORE VERIFYONLY. It will produce errors of such are found. Make sure you
handle the job so your are notified if errors occurs.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message news:1147179633.997410.37830@.j73g2000cwa.googlegroups.com...
> Hi,
> I am trying to check that a backup integrity check has verified a log
> backup because it is being done over a network drive.
> There is an entry verify backup for each backup performed in the
> msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
> correct one I should be looking at to see if RESTORE VERIFYONLY
> succeeded ?
> My question is how do I tell that a verification found an error?
> Thanks
> --Sam
>|||Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_histor=ADy has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_histor=ADy table ?
Many Thanks
--Sam|||I don't know, I'm afraid. I'd guess that Maint plans are smart enough to mark the execution as
failed and log the errors returned by RESTORE VERIFYONLY. I don't use maint plans myself, as I
prefer more control over these things. Perhaps you can try, for instance doing the backup to the
"nul" file name?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message
news:1147180762.992024.182010@.u72g2000cwu.googlegroups.com...
Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_histor­y has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_histor­y table ?
Many Thanks
--Sam