MSDE and ISA

I am running 2 instances of MSDE2000 on a server with Win2K server SP4 and
ISA Server 2000. From the workstations on the network I am able to create
an ODBC connection to the default instance of SQL (MSSQL) but receive an
error when trying to connect to the 2nd instance (MSSQL\INSTANCENAME). Both
names appear in the dropdown list when creating the ODBC connection. Both
instances are running and networking for TCP/IP is enabled using SVRNETCN.
Both instances use the same SA password and connection is made using SQL
Authentication.
Error Message is
Connection Failed
SQLState 01000
SQL Server Error: 10048
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection Failed
SQLState 08001
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied
If I stop both instances of SQL and start only the 2nd instance i am then
able to connect to it but am unable to connect to the default instance when
it is restarted. It seems that the first instance of SQL to start can have
a connection made to it and any other instances cannot have an ODBC
connection. I think it may be related to ISA Server but cannot confirm at
this stage
Any advice would be appreciated.
Darrin
Darrin Acreman wrote:
> I am running 2 instances of MSDE2000 on a server with Win2K server SP4 and
> ISA Server 2000. From the workstations on the network I am able to create
> an ODBC connection to the default instance of SQL (MSSQL) but receive an
> error when trying to connect to the 2nd instance (MSSQL\INSTANCENAME). Both
> names appear in the dropdown list when creating the ODBC connection. Both
> instances are running and networking for TCP/IP is enabled using SVRNETCN.
> Both instances use the same SA password and connection is made using SQL
> Authentication.
> Error Message is
> Connection Failed
> SQLState 01000
> SQL Server Error: 10048
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
> Connection Failed
> SQLState 08001
> SQL Server Error: 17
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied
> If I stop both instances of SQL and start only the 2nd instance i am then
> able to connect to it but am unable to connect to the default instance when
> it is restarted. It seems that the first instance of SQL to start can have
> a connection made to it and any other instances cannot have an ODBC
> connection. I think it may be related to ISA Server but cannot confirm at
> this stage
> Any advice would be appreciated.
> Darrin
>
Check the port numbers for both instances, they should be different
different. Check the application log/system log for any errors generated
by the second instance you start.

MSDE Access via the Network

I'm having a terrible time accessing an MSDE instance over the network.
sqlDMO's listAvailableSQLServers doesn't see the installed instance. I
installed the MSDE instance using setup.exe with the following command:
setup.exe disablenetworkprotocols=0 sapwd="<pwd>" securityMode=SQL
instanceName="<my instance name>"
No luck. So I thought I'd use the svrnetcn.exe utility to enable network
protocols since MSDE seems to be ignoring the command line. When I try to run
svrnetcn.exe, the screen flickers but the program never opens.
This *was* working several weeks ago. It quit working about the time I
installed Service Pack 2 for Windows XP on the box that was hosting this
server. Does anyone have any idea why this is happening to me? Any help
would be GREATLY appreciated.
Rob Reagan
rob@.digitallabsinc.com
hi Rob,
"Rob Reagan" <RobReagan@.discussions.microsoft.com> ha scritto nel messaggio
news:5B63E3CB-8307-49C8-ABC4-56B114893B1D@.microsoft.com...
> I'm having a terrible time accessing an MSDE instance over the network.
> sqlDMO's listAvailableSQLServers doesn't see the installed instance. I
> installed the MSDE instance using setup.exe with the following command:
> setup.exe disablenetworkprotocols=0 sapwd="<pwd>" securityMode=SQL
> instanceName="<my instance name>"
> No luck. So I thought I'd use the svrnetcn.exe utility to enable network
> protocols since MSDE seems to be ignoring the command line. When I try to
run
> svrnetcn.exe, the screen flickers but the program never opens.
> This *was* working several weeks ago. It quit working about the time I
> installed Service Pack 2 for Windows XP on the box that was hosting this
> server. Does anyone have any idea why this is happening to me? Any help
> would be GREATLY appreciated.
> Rob Reagan
> rob@.digitallabsinc.com
>
SP service pack 2 changed a lot of things regarding SQL Server connections
too..
I've not installed sp2 yet, but it's worth reading
http://support.microsoft.com/default.aspx?kbid=841249 and related links...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you so much! That's just the information I needed.
SP2 makes my PC so secure, not even my own applications can get through...
"Andrea Montanari" wrote:

> hi Rob,
> "Rob Reagan" <RobReagan@.discussions.microsoft.com> ha scritto nel messaggio
> news:5B63E3CB-8307-49C8-ABC4-56B114893B1D@.microsoft.com...
> run
> SP service pack 2 changed a lot of things regarding SQL Server connections
> too..
> I've not installed sp2 yet, but it's worth reading
> http://support.microsoft.com/default.aspx?kbid=841249 and related links...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

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

MSDE 2K Merge replication without network

I'm new to replication, but have a challenging requirement...
I have multiple MSDE 2K instances that will be used by a surveying crew that
may be distributed across many miles - sometimes in jungle or desert
environments where they never even see each other.
All/any data in any instance is updateable; all changes must be propagated -
at irregular intervals (daily or?) to all other instances. There is no
designated "master" (or perhaps all instances could be considered "masters").
We can live with a hub-and-spoke replication topology (ie, all replication
occurs via a hub instance at the field camp, which then, eventually,
replicates to all the other spokes).
===> The instances are NOT (and are NEVER) connected over a network! (not
even wireless - although we should be able to at least keep the system clocks
synchronized, if that's required for reliable synchronization, by having
each system have a GPS receiver).
Therefore, all synchronization must be via files (flash drive, etc). Even
the definition/setup of the synchronization (subscriptions) must not require
a network connection.
Can Merge replication be implemented between MSDE instances, given these
network constraints?
Thanks!
David
Unless you provide at least an occasional network connectivity between
publisher and subscribers merge replication cannot be implemented.
Yury
"David" <David@.discussions.microsoft.com> wrote in message
news:32C0446B-5D11-4FAF-AB03-70F4096642BC@.microsoft.com...
> I'm new to replication, but have a challenging requirement...
> I have multiple MSDE 2K instances that will be used by a surveying crew
> that
> may be distributed across many miles - sometimes in jungle or desert
> environments where they never even see each other.
> All/any data in any instance is updateable; all changes must be
> propagated -
> at irregular intervals (daily or?) to all other instances. There is no
> designated "master" (or perhaps all instances could be considered
> "masters").
>
> We can live with a hub-and-spoke replication topology (ie, all replication
> occurs via a hub instance at the field camp, which then, eventually,
> replicates to all the other spokes).
> ===> The instances are NOT (and are NEVER) connected over a network! (not
> even wireless - although we should be able to at least keep the system
> clocks
> synchronized, if that's required for reliable synchronization, by having
> each system have a GPS receiver).
> Therefore, all synchronization must be via files (flash drive, etc). Even
> the definition/setup of the synchronization (subscriptions) must not
> require
> a network connection.
> Can Merge replication be implemented between MSDE instances, given these
> network constraints?
> Thanks!
> David
|||its probably better to use transactional replication with a local dummy
subscriber. Collect the contents of msrepl_commands and then mail them back
and forth. This will be a list of all database activity which you can run on
each node for synchronization purposes.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"David" <David@.discussions.microsoft.com> wrote in message
news:32C0446B-5D11-4FAF-AB03-70F4096642BC@.microsoft.com...
> I'm new to replication, but have a challenging requirement...
> I have multiple MSDE 2K instances that will be used by a surveying crew
that
> may be distributed across many miles - sometimes in jungle or desert
> environments where they never even see each other.
> All/any data in any instance is updateable; all changes must be
propagated -
> at irregular intervals (daily or?) to all other instances. There is no
> designated "master" (or perhaps all instances could be considered
"masters").
>
> We can live with a hub-and-spoke replication topology (ie, all replication
> occurs via a hub instance at the field camp, which then, eventually,
> replicates to all the other spokes).
> ===> The instances are NOT (and are NEVER) connected over a network! (not
> even wireless - although we should be able to at least keep the system
clocks
> synchronized, if that's required for reliable synchronization, by having
> each system have a GPS receiver).
> Therefore, all synchronization must be via files (flash drive, etc). Even
> the definition/setup of the synchronization (subscriptions) must not
require
> a network connection.
> Can Merge replication be implemented between MSDE instances, given these
> network constraints?
> Thanks!
> David

MSDE 2000 changing disablenetworkprotocols after installation

Hi All
I wasn't aware of the security feature of MSDE, whereby it doesn't allow the
TCP/IP(?) network protocol to work and allow a networked PC to connect to an
SQL DB running on a MSDE installation on another PC. It only allows the
'host' PC to connect to the SQL DB.
I've sussed this in my MSDE installer so that it enables the network feature
when it installs, but I have a user who already has MSDE installed and
running with the protocol disabled and now that they are in the process of
connecting and using a 2nd PC I don't want to ask them to detach their db,
re-install MSDE with the right flag and then re-attach their db, as our
relationship is strained as it is.
Is there anyway to re-set/patch this flag on an installed version?
Thanks
Robbie
hi Robbie,
Astra wrote:
>..
> I've sussed this in my MSDE installer so that it enables the network
> feature when it installs, but I have a user who already has MSDE
> installed and running with the protocol disabled and now that they
> are in the process of connecting and using a 2nd PC I don't want to
> ask them to detach their db, re-install MSDE with the right flag and
> then re-attach their db, as our relationship is strained as it is.
> Is there anyway to re-set/patch this flag on an installed version?
please have a look at
http://support.microsoft.com/default...b;en-us;285097 in the part
regarding the Windows registry modification..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE 2000 behind WSUS server

Hello,
I'm a network / server guy at heart who has been given a quasi-DBA hat
to wear lately, so bear with me.
I have a WSUS (localized Windows updates) server that uses MSDE 2000
as its back end. Since last weekend I started to get an error that
points to a database problem. For the curious, read this:
http://support.microsoft.com/kb/910847
I am disgusted that I cannot go somewhere to download the hotfix, but
rather, I have to call and ask for it. And hope to not get charged for
the call. So, what I'm looking for are utilities that will allow me to
peek inside the database and try to do some cleanup. I'm not finding
much.
I found some command line utilities buried in the directory structure,
like the query tool osql.exe, and dtsrun.exe for DTS packages. But
anything this low level quickly puts me out of my comfort zone. It
seems as though Microsoft has gone to great lengths to keep the
innards of WSUS a secret. Anybody have any ideas how to expose them?
Thanks,
Justin
what.. you want to know more about the schema?
I don't think that it's reccomended that anyone go into the schema and
change anything.. if that's what you're referring to
I know in a heartbeat a real SQL person can dig through a 100 tables in an
hour and have a clue whats going on
<jschick@.aafp.org> wrote in message
news:1177614911.411800.103200@.r3g2000prh.googlegro ups.com...
> Hello,
> I'm a network / server guy at heart who has been given a quasi-DBA hat
> to wear lately, so bear with me.
> I have a WSUS (localized Windows updates) server that uses MSDE 2000
> as its back end. Since last weekend I started to get an error that
> points to a database problem. For the curious, read this:
> http://support.microsoft.com/kb/910847
> I am disgusted that I cannot go somewhere to download the hotfix, but
> rather, I have to call and ask for it. And hope to not get charged for
> the call. So, what I'm looking for are utilities that will allow me to
> peek inside the database and try to do some cleanup. I'm not finding
> much.
> I found some command line utilities buried in the directory structure,
> like the query tool osql.exe, and dtsrun.exe for DTS packages. But
> anything this low level quickly puts me out of my comfort zone. It
> seems as though Microsoft has gone to great lengths to keep the
> innards of WSUS a secret. Anybody have any ideas how to expose them?
> Thanks,
> Justin
>

MSDE 2.0 Install Fails - Unable to disable network access

I have one super stubborn machine that I am about ready to give up and redo Windows on in order to get MSDE to install.
I am trying to install MSDE 2000 Rel A on a DELL Latitude C840 Laptop. This laptop has all Windows Updates as of 5/20/04. It has MDAC v2.8 prior to install. Virus scan and spyware scan are both clean. I am installing under local Administrator account. I also close all background processes and apps prior to install. Machine name is all caps.
Here are my execution parms: (both have same results)
setup.exe SAPWD=@.@.@.@.@.@.@.
setup.exe INSTANCENAME=@.@.@.@.@.@.@. DISABLENETWORKPROTOCOLS=1 SAPWD=@.@.@.@.@.@.@.
Installation fails and then performs a rollback. I logged the install and here is what it is reporting:
================================================== =======
.
.
MSI (s) (8C:48): Creating MSIHANDLE (239) of type 790536 for thread 1096
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action DisableNetAccess()
Error : unable to disable network access to MSDE.
Ending custom action DisableNetAccess()
Action ended 14:53:45: InstallFinalize. Return value 3.
MSI (s) (8C:48): User policy value 'DisableRollback' is 0
MSI (s) (8C:48): Machine policy value 'DisableRollback' is 0
.
.
================================================== =======
It is failing to disable network access to MSDE. I verified that all prereqs for installation (file sharing, and policy settings) are correct. I think I even tried holding my breath and standing on my head while installing with no success.
Any ideas, sympathy, or support? I have searched and searched on the net but apparantly I'm the only one with this particular installation error. Lucky Me.Ok - so I learned some more information about this machine. Apparantly it has had a lot of virus problems in the past with multiple instances of the W32.Netsky.P@.mm virus that were all "removed" with the installation of Norton Anti-Virus.
One thing I decided to try was to check the registry permissions that MSDE is trying to write as it installs. Specifically I checked the permissions on the key HKLM\Software\Microsoft\MSSQLServer and I found that no read or write permissions were set for any user. I set full control to SYTEM and Administrators using RegEdt32.
Upon another logged reinstall of MSDE I recieved a different error:
================================================== ======
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action SetFileAndRegACLs()
Installation drive does not support NTFS security.
Failed to set registry security.
Ending custom action SetFileAndRegACLs().
Action ended 9:27:12: InstallFinalize. Return value 3.
MSI (s) (E4:6C): User policy value 'DisableRollback' is 0
MSI (s) (E4:6C): Machine policy value 'DisableRollback' is 0
================================================== ======
This confirms that I am on the right path, but that this registry permission problem is bigger than I thought. I am wondering if there is some default registry permission that is out of whack that affect new entries being set to no read/write permissions for all users - most likely thanks to those friendly viruses that were running rampant before I came along.
Any thoughts or ideas?|||After more investigation into this registry permission problem I discovered that the registry permissions on this computer have been severely altered. (Problably by one of the many viruses that had been present and since removed)
Permissions on the top level keys, like HKEY_LOCAL_MACHINE, were set to to "Full Control for user Everyone" with no other users defined. No wonder when the MSSQLServer key was added under Software\Microsoft the Administrator and System users were denied permissions. These keys are created to inherit permissions - and with no Administrator or SYSTEM permissions set on top level nodes it just causes havok.
I also installed Norton Anti-Virus 2004 in replace of the "other" virus scanner and it had several problems during install that were related to registry permission failures.
I am offically giving up and re-installing Windows. There is no way I will ever hope to restore the correct permissions throughout the registry.

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