recent SQL 2005 hotfix creates problem

Here are the errors in event log. The installation packeage keeps trying
every 3 hours. How shouyld I fix it.
Microsoft SQL Server 2005 Tools Express Edition -- Install started.
Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
installer has encountered an unexpected error. The error code is 2711. The
specified Feature name ('SQL_Documentation') not found in Feature table.
Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
not be installed. Error code 1603. Additional information is available in the
log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB932557_sql run_tools.msp.log.
Hi
"fj" wrote:

> Here are the errors in event log. The installation packeage keeps trying
> every 3 hours. How shouyld I fix it.
>
> Microsoft SQL Server 2005 Tools Express Edition -- Install started.
> Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
> installer has encountered an unexpected error. The error code is 2711. The
> specified Feature name ('SQL_Documentation') not found in Feature table.
> Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
> for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
> not be installed. Error code 1603. Additional information is available in the
> log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB932557_sql run_tools.msp.log.
What does this log say?
It may be similar to http://support.microsoft.com/kb/916760/en-us
or http://support.microsoft.com/kb/834484/en-us i.e. the permissions or
folders expected may not exist or have the wrong permissions or the account
doing the install may not have enough permissions.
John
|||Here is the part I found that might cause the problem. The specified Feature
name ('SQL_Documentation') not found in Feature table.
....
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E, Object:
C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a 1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget, Object:
C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
Express Edition -- Error 2711. The installer has encountered an unexpected
error. The error code is 2711. The specified Feature name
('SQL_Documentation') not found in Feature table.
Error 2711. The installer has encountered an unexpected error. The error
code is 2711. The specified Feature name ('SQL_Documentation') not found in
Feature table.
Action ended 9:51:03: CostFinalize. Return value 3.
Action ended 9:51:03: INSTALL. Return value 3.
Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Property(S): ProductLanguage = 1033
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.00.1399.06
Property(S): MEDIAPACKAGEPATH = \Setup\
....
|||Hi
"fj" wrote:

> Here is the part I found that might cause the problem. The specified Feature
> name ('SQL_Documentation') not found in Feature table.
>
> ...
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E, Object:
> C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a 1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget, Object:
> C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
> Express Edition -- Error 2711. The installer has encountered an unexpected
> error. The error code is 2711. The specified Feature name
> ('SQL_Documentation') not found in Feature table.
> Error 2711. The installer has encountered an unexpected error. The error
> code is 2711. The specified Feature name ('SQL_Documentation') not found in
> Feature table.
> Action ended 9:51:03: CostFinalize. Return value 3.
> Action ended 9:51:03: INSTALL. Return value 3.
> Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> Property(S): ProductLanguage = 1033
> Property(S): Manufacturer = Microsoft Corporation
> Property(S): ProductVersion = 9.00.1399.06
> Property(S): MEDIAPACKAGEPATH = \Setup\
> ...
SQL Express is not one of the products that have been listed as affected by
the hotfix!
http://support.microsoft.com/kb/932557/en-us
John
|||"John Bell" wrote:

> Hi
> "fj" wrote:
>
> SQL Express is not one of the products that have been listed as affected by
> the hotfix!
> http://support.microsoft.com/kb/932557/en-us
> John
Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
installed by auto-update.
Now it seems like there is a scheduled job at somewhere, how I can stop or
remove it?
Is the hotfix referred by your link a fix to the problem?
Thanks
-FJ
|||Hi
"fj" wrote:

>
> "John Bell" wrote:
>
> Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
> installed by auto-update.
> Now it seems like there is a scheduled job at somewhere, how I can stop or
> remove it?
> Is the hotfix referred by your link a fix to the problem?
> Thanks
> -FJ
It looks like you may have something left over then, if you have removed it.
You may want to check out:
http://msdn2.microsoft.com/en-us/vstudio/aa718704.aspx
or http://support.microsoft.com/kb/909967
John
|||Thanks John,
Actually I found the problem is because I didn't install the client tool and
documents from the original 2005 SQL Server(64bit). BUT, the auto-update
downloaded the hotfix for the SQL server 2005 without checking if I need this
fix. This hotfix (MSDN article number 932557) has "hardwired" update for
those tools and docs whch I don't have so the update failed.
Since the update is scheduled to launch every 3 hours, I am keep getting
this annoying errors.
Now my question still remains, how I can terminate the remaining update
manually? Is there a way to intercept MicroSoft's auto-update?
I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
bug in this hotfix and Microsoft needs to know that.
Thanks
-FJ
|||Hi
"fj" wrote:

> Thanks John,
> Actually I found the problem is because I didn't install the client tool and
> documents from the original 2005 SQL Server(64bit). BUT, the auto-update
> downloaded the hotfix for the SQL server 2005 without checking if I need this
> fix. This hotfix (MSDN article number 932557) has "hardwired" update for
> those tools and docs whch I don't have so the update failed.
> Since the update is scheduled to launch every 3 hours, I am keep getting
> this annoying errors.
> Now my question still remains, how I can terminate the remaining update
> manually? Is there a way to intercept MicroSoft's auto-update?
> I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
> bug in this hotfix and Microsoft needs to know that.
> Thanks
> -FJ
Why not install the tools, allow the update or manually install the update
and then remove the tools?
Automatic updates are not something you would want on a production system so
you may want to turn them off, but the problem could still occur if you
turned them on at some point.
John
sql

recent SQL 2005 hotfix creates problem

Here are the errors in event log. The installation packeage keeps trying
every 3 hours. How shouyld I fix it.
Microsoft SQL Server 2005 Tools Express Edition -- Install started.
Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
installer has encountered an unexpected error. The error code is 2711. The
specified Feature name ('SQL_Documentation') not found in Feature table.
Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
not be installed. Error code 1603. Additional information is available in th
e
log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB
932557_sqlrun_tools.msp.log.Hi
"fj" wrote:

> Here are the errors in event log. The installation packeage keeps trying
> every 3 hours. How shouyld I fix it.
>
> Microsoft SQL Server 2005 Tools Express Edition -- Install started.
> Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. Th
e
> installer has encountered an unexpected error. The error code is 2711. The
> specified Feature name ('SQL_Documentation') not found in Feature table.
> Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 140
6
> for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
> not be installed. Error code 1603. Additional information is available in
the
> log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB
932557_sqlrun_tools.msp.log.
What does this log say?
It may be similar to http://support.microsoft.com/kb/916760/en-us
or http://support.microsoft.com/kb/834484/en-us i.e. the permissions or
folders expected may not exist or have the wrong permissions or the account
doing the install may not have enough permissions.
John|||Here is the part I found that might cause the problem. The specified Feature
name ('SQL_Documentation') not found in Feature table.
...
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_
dc990e4797f81af1\
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
Express Edition -- Error 2711. The installer has encountered an unexpected
error. The error code is 2711. The specified Feature name
('SQL_Documentation') not found in Feature table.
Error 2711. The installer has encountered an unexpected error. The error
code is 2711. The specified Feature name ('SQL_Documentation') not found in
Feature table.
Action ended 9:51:03: CostFinalize. Return value 3.
Action ended 9:51:03: INSTALL. Return value 3.
Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Property(S): ProductLanguage = 1033
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.00.1399.06
Property(S): MEDIAPACKAGEPATH = \Setup\
...|||Hi
"fj" wrote:

> Here is the part I found that might cause the problem. The specified Featu
re
> name ('SQL_Documentation') not found in Feature table.
>
> ...
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
> C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_non
e_dc990e4797f81af1\
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object
:
> C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Too
ls
> Express Edition -- Error 2711. The installer has encountered an unexpected
> error. The error code is 2711. The specified Feature name
> ('SQL_Documentation') not found in Feature table.
> Error 2711. The installer has encountered an unexpected error. The error
> code is 2711. The specified Feature name ('SQL_Documentation') not found i
n
> Feature table.
> Action ended 9:51:03: CostFinalize. Return value 3.
> Action ended 9:51:03: INSTALL. Return value 3.
> Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> Property(S): ProductLanguage = 1033
> Property(S): Manufacturer = Microsoft Corporation
> Property(S): ProductVersion = 9.00.1399.06
> Property(S): MEDIAPACKAGEPATH = \Setup\
> ...
SQL Express is not one of the products that have been listed as affected by
the hotfix!
http://support.microsoft.com/kb/932557/en-us
John|||"John Bell" wrote:

> Hi
> "fj" wrote:
>
> SQL Express is not one of the products that have been listed as affected b
y
> the hotfix!
> http://support.microsoft.com/kb/932557/en-us
> John
Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
installed by auto-update.
Now it seems like there is a scheduled job at somewhere, how I can stop or
remove it?
Is the hotfix referred by your link a fix to the problem?
Thanks
-FJ|||Hi
"fj" wrote:

>
> "John Bell" wrote:
>
> Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix
is
> installed by auto-update.
> Now it seems like there is a scheduled job at somewhere, how I can stop or
> remove it?
> Is the hotfix referred by your link a fix to the problem?
> Thanks
> -FJ
It looks like you may have something left over then, if you have removed it.
You may want to check out:
http://msdn2.microsoft.com/en-us/vstudio/aa718704.aspx
or http://support.microsoft.com/kb/909967
John|||Thanks John,
Actually I found the problem is because I didn't install the client tool and
documents from the original 2005 SQL Server(64bit). BUT, the auto-update
downloaded the hotfix for the SQL server 2005 without checking if I need thi
s
fix. This hotfix (MSDN article number 932557) has "hardwired" update for
those tools and docs whch I don't have so the update failed.
Since the update is scheduled to launch every 3 hours, I am keep getting
this annoying errors.
Now my question still remains, how I can terminate the remaining update
manually? Is there a way to intercept MicroSoft's auto-update?
I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
bug in this hotfix and Microsoft needs to know that.
Thanks
-FJ|||Hi
"fj" wrote:

> Thanks John,
> Actually I found the problem is because I didn't install the client tool a
nd
> documents from the original 2005 SQL Server(64bit). BUT, the auto-update
> downloaded the hotfix for the SQL server 2005 without checking if I need t
his
> fix. This hotfix (MSDN article number 932557) has "hardwired" update for
> those tools and docs whch I don't have so the update failed.
> Since the update is scheduled to launch every 3 hours, I am keep getting
> this annoying errors.
> Now my question still remains, how I can terminate the remaining update
> manually? Is there a way to intercept MicroSoft's auto-update?
> I don't think I need to re-install or remove VS2005 or SQL 2005. There is
a
> bug in this hotfix and Microsoft needs to know that.
> Thanks
> -FJ
Why not install the tools, allow the update or manually install the update
and then remove the tools?
Automatic updates are not something you would want on a production system so
you may want to turn them off, but the problem could still occur if you
turned them on at some point.
John

recent SQL 2005 hotfix creates problem

Here are the errors in event log. The installation packeage keeps trying
every 3 hours. How shouyld I fix it.
Microsoft SQL Server 2005 Tools Express Edition -- Install started.
Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
installer has encountered an unexpected error. The error code is 2711. The
specified Feature name ('SQL_Documentation') not found in Feature table.
Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
not be installed. Error code 1603. Additional information is available in the
log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB932557_sqlrun_tools.msp.log.Hi
"fj" wrote:
> Here are the errors in event log. The installation packeage keeps trying
> every 3 hours. How shouyld I fix it.
>
> Microsoft SQL Server 2005 Tools Express Edition -- Install started.
> Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
> installer has encountered an unexpected error. The error code is 2711. The
> specified Feature name ('SQL_Documentation') not found in Feature table.
> Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
> for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
> not be installed. Error code 1603. Additional information is available in the
> log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB932557_sqlrun_tools.msp.log.
What does this log say?
It may be similar to http://support.microsoft.com/kb/916760/en-us
or http://support.microsoft.com/kb/834484/en-us i.e. the permissions or
folders expected may not exist or have the wrong permissions or the account
doing the install may not have enough permissions.
John|||Here is the part I found that might cause the problem. The specified Feature
name ('SQL_Documentation') not found in Feature table.
...
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
Express Edition -- Error 2711. The installer has encountered an unexpected
error. The error code is 2711. The specified Feature name
('SQL_Documentation') not found in Feature table.
Error 2711. The installer has encountered an unexpected error. The error
code is 2711. The specified Feature name ('SQL_Documentation') not found in
Feature table.
Action ended 9:51:03: CostFinalize. Return value 3.
Action ended 9:51:03: INSTALL. Return value 3.
Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Property(S): ProductLanguage = 1033
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.00.1399.06
Property(S): MEDIAPACKAGEPATH = \Setup\
...|||Hi
"fj" wrote:
> Here is the part I found that might cause the problem. The specified Feature
> name ('SQL_Documentation') not found in Feature table.
>
> ...
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
> C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
> C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
> Express Edition -- Error 2711. The installer has encountered an unexpected
> error. The error code is 2711. The specified Feature name
> ('SQL_Documentation') not found in Feature table.
> Error 2711. The installer has encountered an unexpected error. The error
> code is 2711. The specified Feature name ('SQL_Documentation') not found in
> Feature table.
> Action ended 9:51:03: CostFinalize. Return value 3.
> Action ended 9:51:03: INSTALL. Return value 3.
> Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> Property(S): ProductLanguage = 1033
> Property(S): Manufacturer = Microsoft Corporation
> Property(S): ProductVersion = 9.00.1399.06
> Property(S): MEDIAPACKAGEPATH = \Setup\
> ...
SQL Express is not one of the products that have been listed as affected by
the hotfix!
http://support.microsoft.com/kb/932557/en-us
John|||"John Bell" wrote:
> Hi
> "fj" wrote:
> > Here is the part I found that might cause the problem. The specified Feature
> > name ('SQL_Documentation') not found in Feature table.
> >
> >
> >
> > ...
> > MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> > payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
> > C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
> > MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
> > C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> > MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> > MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
> > Express Edition -- Error 2711. The installer has encountered an unexpected
> > error. The error code is 2711. The specified Feature name
> > ('SQL_Documentation') not found in Feature table.
> >
> > Error 2711. The installer has encountered an unexpected error. The error
> > code is 2711. The specified Feature name ('SQL_Documentation') not found in
> > Feature table.
> > Action ended 9:51:03: CostFinalize. Return value 3.
> > Action ended 9:51:03: INSTALL. Return value 3.
> > Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> > Property(S): ProductLanguage = 1033
> > Property(S): Manufacturer = Microsoft Corporation
> > Property(S): ProductVersion = 9.00.1399.06
> > Property(S): MEDIAPACKAGEPATH = \Setup\
> > ...
> SQL Express is not one of the products that have been listed as affected by
> the hotfix!
> http://support.microsoft.com/kb/932557/en-us
> John
Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
installed by auto-update.
Now it seems like there is a scheduled job at somewhere, how I can stop or
remove it?
Is the hotfix referred by your link a fix to the problem?
Thanks
-FJ|||Hi
"fj" wrote:
>
> "John Bell" wrote:
> > Hi
> >
> > "fj" wrote:
> >
> > > Here is the part I found that might cause the problem. The specified Feature
> > > name ('SQL_Documentation') not found in Feature table.
> > >
> > >
> > >
> > > ...
> > > MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> > > payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
> > > C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
> > > MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
> > > C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> > > MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> > > MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
> > > Express Edition -- Error 2711. The installer has encountered an unexpected
> > > error. The error code is 2711. The specified Feature name
> > > ('SQL_Documentation') not found in Feature table.
> > >
> > > Error 2711. The installer has encountered an unexpected error. The error
> > > code is 2711. The specified Feature name ('SQL_Documentation') not found in
> > > Feature table.
> > > Action ended 9:51:03: CostFinalize. Return value 3.
> > > Action ended 9:51:03: INSTALL. Return value 3.
> > > Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> > > Property(S): ProductLanguage = 1033
> > > Property(S): Manufacturer = Microsoft Corporation
> > > Property(S): ProductVersion = 9.00.1399.06
> > > Property(S): MEDIAPACKAGEPATH = \Setup\
> > > ...
> >
> > SQL Express is not one of the products that have been listed as affected by
> > the hotfix!
> > http://support.microsoft.com/kb/932557/en-us
> >
> > John
> Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
> installed by auto-update.
> Now it seems like there is a scheduled job at somewhere, how I can stop or
> remove it?
> Is the hotfix referred by your link a fix to the problem?
> Thanks
> -FJ
It looks like you may have something left over then, if you have removed it.
You may want to check out:
http://msdn2.microsoft.com/en-us/vstudio/aa718704.aspx
or http://support.microsoft.com/kb/909967
John|||Thanks John,
Actually I found the problem is because I didn't install the client tool and
documents from the original 2005 SQL Server(64bit). BUT, the auto-update
downloaded the hotfix for the SQL server 2005 without checking if I need this
fix. This hotfix (MSDN article number 932557) has "hardwired" update for
those tools and docs whch I don't have so the update failed.
Since the update is scheduled to launch every 3 hours, I am keep getting
this annoying errors.
Now my question still remains, how I can terminate the remaining update
manually? Is there a way to intercept MicroSoft's auto-update?
I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
bug in this hotfix and Microsoft needs to know that.
Thanks
-FJ|||Hi
"fj" wrote:
> Thanks John,
> Actually I found the problem is because I didn't install the client tool and
> documents from the original 2005 SQL Server(64bit). BUT, the auto-update
> downloaded the hotfix for the SQL server 2005 without checking if I need this
> fix. This hotfix (MSDN article number 932557) has "hardwired" update for
> those tools and docs whch I don't have so the update failed.
> Since the update is scheduled to launch every 3 hours, I am keep getting
> this annoying errors.
> Now my question still remains, how I can terminate the remaining update
> manually? Is there a way to intercept MicroSoft's auto-update?
> I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
> bug in this hotfix and Microsoft needs to know that.
> Thanks
> -FJ
Why not install the tools, allow the update or manually install the update
and then remove the tools?
Automatic updates are not something you would want on a production system so
you may want to turn them off, but the problem could still occur if you
turned them on at some point.
John

Receiving SQL Server Error messages in SQL Server Log

Hi:
I've been receiving the below mentioned error messages in
my SQL Server Log for all databases ;
1. IO is thawed
2. IO is frozen for snapshot
Any idea as to for what reason this would be happening.
Thanks very much in advance!Most likely due to using dbcc freeze_io and thaw_io.
The commands are depreciated in SQL Server 2000 and are not
recommended to be used due to the depreciation as well as
the potential for these commands to hang the server.
-Sue
On Tue, 13 Apr 2004 07:39:20 -0700, "Arpit"
<apatel@.esricanada.com> wrote:
>Hi:
>I've been receiving the below mentioned error messages in
>my SQL Server Log for all databases ;
>1. IO is thawed
>2. IO is frozen for snapshot
>Any idea as to for what reason this would be happening.
>Thanks very much in advance!|||Thanks Sue!
I haven't use the dbcc freeze_io and thaw_io. Would there
any process of job that would have used this in the
background?
Thanks
>--Original Message--
>Most likely due to using dbcc freeze_io and thaw_io.
>The commands are depreciated in SQL Server 2000 and are
not
>recommended to be used due to the depreciation as well as
>the potential for these commands to hang the server.
>-Sue
>On Tue, 13 Apr 2004 07:39:20 -0700, "Arpit"
><apatel@.esricanada.com> wrote:
>>Hi:
>>I've been receiving the below mentioned error messages
in
>>my SQL Server Log for all databases ;
>>1. IO is thawed
>>2. IO is frozen for snapshot
>>Any idea as to for what reason this would be happening.
>>Thanks very much in advance!
>.
>|||I've read a couple posts where it seems some third party
vendor for backups or shadow copy backups uses this. SQL
Server itself or any of native functionality isn't likely to
be implementing this. I'd look at whatever third party
tools, products you may be using. You could look at the
times you are getting the messages logged and try to figure
out what's running at those times.
-Sue
On Tue, 13 Apr 2004 08:52:43 -0700, "Arpit"
<anonymous@.discussions.microsoft.com> wrote:
>Thanks Sue!
>I haven't use the dbcc freeze_io and thaw_io. Would there
>any process of job that would have used this in the
>background?
>Thanks
>>--Original Message--
>>Most likely due to using dbcc freeze_io and thaw_io.
>>The commands are depreciated in SQL Server 2000 and are
>not
>>recommended to be used due to the depreciation as well as
>>the potential for these commands to hang the server.
>>-Sue
>>On Tue, 13 Apr 2004 07:39:20 -0700, "Arpit"
>><apatel@.esricanada.com> wrote:
>>Hi:
>>I've been receiving the below mentioned error messages
>in
>>my SQL Server Log for all databases ;
>>1. IO is thawed
>>2. IO is frozen for snapshot
>>Any idea as to for what reason this would be happening.
>>Thanks very much in advance!
>>.

Receiving SQL Server Error messages in SQL Server Log

Hi:
I've been receiving the below mentioned error messages in
my SQL Server Log for all databases ;
1. IO is thawed
2. IO is frozen for snapshot
Any idea as to for what reason this would be happening.
Thanks very much in advance!
Most likely due to using dbcc freeze_io and thaw_io.
The commands are depreciated in SQL Server 2000 and are not
recommended to be used due to the depreciation as well as
the potential for these commands to hang the server.
-Sue
On Tue, 13 Apr 2004 07:39:20 -0700, "Arpit"
<apatel@.esricanada.com> wrote:

>Hi:
>I've been receiving the below mentioned error messages in
>my SQL Server Log for all databases ;
>1. IO is thawed
>2. IO is frozen for snapshot
>Any idea as to for what reason this would be happening.
>Thanks very much in advance!
|||Thanks Sue!
I haven't use the dbcc freeze_io and thaw_io. Would there
any process of job that would have used this in the
background?
Thanks
>--Original Message--
>Most likely due to using dbcc freeze_io and thaw_io.
>The commands are depreciated in SQL Server 2000 and are
not[color=darkblue]
>recommended to be used due to the depreciation as well as
>the potential for these commands to hang the server.
>-Sue
>On Tue, 13 Apr 2004 07:39:20 -0700, "Arpit"
><apatel@.esricanada.com> wrote:
in
>.
>
|||I've read a couple posts where it seems some third party
vendor for backups or shadow copy backups uses this. SQL
Server itself or any of native functionality isn't likely to
be implementing this. I'd look at whatever third party
tools, products you may be using. You could look at the
times you are getting the messages logged and try to figure
out what's running at those times.
-Sue
On Tue, 13 Apr 2004 08:52:43 -0700, "Arpit"
<anonymous@.discussions.microsoft.com> wrote:
[color=darkblue]
>Thanks Sue!
>I haven't use the dbcc freeze_io and thaw_io. Would there
>any process of job that would have used this in the
>background?
>Thanks
>not
>in

Receiving SQL Server Error messages in SQL Server Log

Hi:
I've been receiving the below mentioned error messages in
my SQL Server Log for all databases ;
1. IO is thawed
2. IO is frozen for snapshot
Any idea as to for what reason this would be happening.
Thanks very much in advance!Most likely due to using dbcc freeze_io and thaw_io.
The commands are depreciated in SQL Server 2000 and are not
recommended to be used due to the depreciation as well as
the potential for these commands to hang the server.
-Sue
On Tue, 13 Apr 2004 07:39:20 -0700, "Arpit"
<apatel@.esricanada.com> wrote:

>Hi:
>I've been receiving the below mentioned error messages in
>my SQL Server Log for all databases ;
>1. IO is thawed
>2. IO is frozen for snapshot
>Any idea as to for what reason this would be happening.
>Thanks very much in advance!|||Thanks Sue!
I haven't use the dbcc freeze_io and thaw_io. Would there
any process of job that would have used this in the
background?
Thanks
>--Original Message--
>Most likely due to using dbcc freeze_io and thaw_io.
>The commands are depreciated in SQL Server 2000 and are
not
>recommended to be used due to the depreciation as well as
>the potential for these commands to hang the server.
>-Sue
>On Tue, 13 Apr 2004 07:39:20 -0700, "Arpit"
><apatel@.esricanada.com> wrote:
>
in
>.
>|||I've read a couple posts where it seems some third party
vendor for backups or shadow copy backups uses this. SQL
Server itself or any of native functionality isn't likely to
be implementing this. I'd look at whatever third party
tools, products you may be using. You could look at the
times you are getting the messages logged and try to figure
out what's running at those times.
-Sue
On Tue, 13 Apr 2004 08:52:43 -0700, "Arpit"
<anonymous@.discussions.microsoft.com> wrote:
>Thanks Sue!
>I haven't use the dbcc freeze_io and thaw_io. Would there
>any process of job that would have used this in the
>background?
>Thanks
>not
>insql

Receiving DTC error after Windows Patch for latest zotob

Receiving "Failed to obtain TransactionDispenserInterface: Result Code =
0x8004d01b" in the error log of the SQL Server after the Windows Admins hav
e
patched the server. The MSDTC service is running and I don't see anything i
n
the Event Logs of the server.
Any clues on how to troubleshoot this?This affects both Windows 2000 and 2003 servers.
"Tom" wrote:

> Receiving "Failed to obtain TransactionDispenserInterface: Result Code =
> 0x8004d01b" in the error log of the SQL Server after the Windows Admins h
ave
> patched the server. The MSDTC service is running and I don't see anything
in
> the Event Logs of the server.
> Any clues on how to troubleshoot this?|||I'm having this problem also on an Active/Passive 2003 cluster. The
only thing I can find in the error logs, other than this message is:
Event Type: Information
Event Source: MSDTC
Event Category: TM
Event ID: 4097
Date: 8/22/2005
Time: 10:17:33 AM
User: N/A
Computer: SV2794
Description:
MS DTC started with the following settings:
Security Configuration (OFF = 0 and ON = 1):
Network Administration of Transactions = 1,
Network Clients = 0,
Distributed Transactions using Native MSDTC Protocol = 1,
Transaction Internet Protocol (TIP) = 0,
XA Transactions = 1
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
*** Sent via Developersdex http://www.codecomments.com ***|||I just fixed this on our server...What I did was verify MSDTC was
running normally in the event log, then do a 'Move Group', which simply
restarted the MSSQL services. I suspect that MSDTC just didn't start
before SQL Server, and MSSQL didn't catch on to it.
*** Sent via Developersdex http://www.codecomments.com ***|||Wayne, I have found the same error message in our SQL 2000 log. I would
appreciate if you could please make the steps more clear as I could not find
Move Group.
"Wayne Fairless" wrote:

> I just fixed this on our server...What I did was verify MSDTC was
> running normally in the event log, then do a 'Move Group', which simply
> restarted the MSSQL services. I suspect that MSDTC just didn't start
> before SQL Server, and MSSQL didn't catch on to it.
>
> *** Sent via Developersdex http://www.codecomments.com ***
>|||I hope Wayne comes back to clarify.
"Wayne Fairless" wrote:

> I just fixed this on our server...What I did was verify MSDTC was
> running normally in the event log, then do a 'Move Group', which simply
> restarted the MSSQL services. I suspect that MSDTC just didn't start
> before SQL Server, and MSSQL didn't catch on to it.
>
> *** Sent via Developersdex http://www.codecomments.com ***
>

Receiving DTC error after Windows Patch for latest zotob

Receiving "Failed to obtain TransactionDispenserInterface: Result Code =
0x8004d01b" in the error log of the SQL Server after the Windows Admins have
patched the server. The MSDTC service is running and I don't see anything in
the Event Logs of the server.
Any clues on how to troubleshoot this?
This affects both Windows 2000 and 2003 servers.
"Tom" wrote:

> Receiving "Failed to obtain TransactionDispenserInterface: Result Code =
> 0x8004d01b" in the error log of the SQL Server after the Windows Admins have
> patched the server. The MSDTC service is running and I don't see anything in
> the Event Logs of the server.
> Any clues on how to troubleshoot this?
|||I'm having this problem also on an Active/Passive 2003 cluster. The
only thing I can find in the error logs, other than this message is:
Event Type:Information
Event Source:MSDTC
Event Category:TM
Event ID:4097
Date:8/22/2005
Time:10:17:33 AM
User:N/A
Computer:SV2794
Description:
MS DTC started with the following settings:
Security Configuration (OFF = 0 and ON = 1):
Network Administration of Transactions = 1,
Network Clients = 0,
Distributed Transactions using Native MSDTC Protocol = 1,
Transaction Internet Protocol (TIP) = 0,
XA Transactions = 1
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
*** Sent via Developersdex http://www.codecomments.com ***
|||I just fixed this on our server...What I did was verify MSDTC was
running normally in the event log, then do a 'Move Group', which simply
restarted the MSSQL services. I suspect that MSDTC just didn't start
before SQL Server, and MSSQL didn't catch on to it.
*** Sent via Developersdex http://www.codecomments.com ***
|||Wayne, I have found the same error message in our SQL 2000 log. I would
appreciate if you could please make the steps more clear as I could not find
Move Group.
"Wayne Fairless" wrote:

> I just fixed this on our server...What I did was verify MSDTC was
> running normally in the event log, then do a 'Move Group', which simply
> restarted the MSSQL services. I suspect that MSDTC just didn't start
> before SQL Server, and MSSQL didn't catch on to it.
>
> *** Sent via Developersdex http://www.codecomments.com ***
>
|||I hope Wayne comes back to clarify.
"Wayne Fairless" wrote:

> I just fixed this on our server...What I did was verify MSDTC was
> running normally in the event log, then do a 'Move Group', which simply
> restarted the MSSQL services. I suspect that MSDTC just didn't start
> before SQL Server, and MSSQL didn't catch on to it.
>
> *** Sent via Developersdex http://www.codecomments.com ***
>

Receiving DTC error after Windows Patch for latest zotob

Receiving "Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b" in the error log of the SQL Server after the Windows Admins have
patched the server. The MSDTC service is running and I don't see anything in
the Event Logs of the server.
Any clues on how to troubleshoot this?This affects both Windows 2000 and 2003 servers.
"Tom" wrote:
> Receiving "Failed to obtain TransactionDispenserInterface: Result Code => 0x8004d01b" in the error log of the SQL Server after the Windows Admins have
> patched the server. The MSDTC service is running and I don't see anything in
> the Event Logs of the server.
> Any clues on how to troubleshoot this?|||I'm having this problem also on an Active/Passive 2003 cluster. The
only thing I can find in the error logs, other than this message is:
Event Type: Information
Event Source: MSDTC
Event Category: TM
Event ID: 4097
Date: 8/22/2005
Time: 10:17:33 AM
User: N/A
Computer: SV2794
Description:
MS DTC started with the following settings:
Security Configuration (OFF = 0 and ON = 1):
Network Administration of Transactions = 1,
Network Clients = 0,
Distributed Transactions using Native MSDTC Protocol = 1,
Transaction Internet Protocol (TIP) = 0,
XA Transactions = 1
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
*** Sent via Developersdex http://www.developersdex.com ***|||I just fixed this on our server...What I did was verify MSDTC was
running normally in the event log, then do a 'Move Group', which simply
restarted the MSSQL services. I suspect that MSDTC just didn't start
before SQL Server, and MSSQL didn't catch on to it.
*** Sent via Developersdex http://www.developersdex.com ***|||Wayne, I have found the same error message in our SQL 2000 log. I would
appreciate if you could please make the steps more clear as I could not find
Move Group.
"Wayne Fairless" wrote:
> I just fixed this on our server...What I did was verify MSDTC was
> running normally in the event log, then do a 'Move Group', which simply
> restarted the MSSQL services. I suspect that MSDTC just didn't start
> before SQL Server, and MSSQL didn't catch on to it.
>
> *** Sent via Developersdex http://www.developersdex.com ***
>|||I hope Wayne comes back to clarify.
"Wayne Fairless" wrote:
> I just fixed this on our server...What I did was verify MSDTC was
> running normally in the event log, then do a 'Move Group', which simply
> restarted the MSSQL services. I suspect that MSDTC just didn't start
> before SQL Server, and MSSQL didn't catch on to it.
>
> *** Sent via Developersdex http://www.developersdex.com ***
>

Recataloging a log backup disk file

Backup Log DataBaseName to
DISK='\\ServerName\ShareName\Path\FileName.TRN' with
RetainDays=1, Description='Daily Backup Routine'
When I restore a database and logs to an alternate
server, I can restore the full database backup and the
first iteration of the log backups without any problems.
The problem is with all subsequent log backups that were
performed and apended to the file created by the above
statement. I know and can get to the subsequent appended
logs via TSQL, but not an easy task if there are 15
appended log backups on the device. Is there a way I can
recatalog all the log backups so I can use Enterprise
Manager's point an click interface to restore? Will the
STOPAT parameter restore the first log backup, and all
subsequent backups, up to the STOPAT? The command used
to create the log backup is stated above.
Thanx soo much for your help,
D2David,
> Is there a way I can
> recatalog all the log backups so I can use Enterprise
> Manager's point an click interface to restore?
Not easily. I guess you can write a TSQL script that uses RESTORE HEADERONLY and based on that
inserts data into the backup history tables in msdb. Note that *this is not supported*! EM has an
option to generate backuphistory as you select a backup device in the restore dialog, but that isn't
dine on a file basis, but on a backup basis, so using EM to generate backuphistory, you would have
to go through that dialog 15 times.
> Will the
> STOPAT parameter restore the first log backup, and all
> subsequent backups, up to the STOPAT?
No. All RESTORE commands only addresses one backup at a time.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"David Danh" <anonymous@.discussions.microsoft.com> wrote in message
news:370101c4a05d$53fc68b0$a501280a@.phx.gbl...
> Backup Log DataBaseName to
> DISK='\\ServerName\ShareName\Path\FileName.TRN' with
> RetainDays=1, Description='Daily Backup Routine'
> When I restore a database and logs to an alternate
> server, I can restore the full database backup and the
> first iteration of the log backups without any problems.
> The problem is with all subsequent log backups that were
> performed and apended to the file created by the above
> statement. I know and can get to the subsequent appended
> logs via TSQL, but not an easy task if there are 15
> appended log backups on the device. Is there a way I can
> recatalog all the log backups so I can use Enterprise
> Manager's point an click interface to restore? Will the
> STOPAT parameter restore the first log backup, and all
> subsequent backups, up to the STOPAT? The command used
> to create the log backup is stated above.
> Thanx soo much for your help,
> D2
>|||Thanks for the help... I ended up doing this...
RESTORE VERIFYONLY FROM DISK='FilePath' WITH
FILE=#,LOADHISTORY
Replaced the # with 1 2 3 4 5 6 7 ...
I just wish it can be done with one command.
>--Original Message--
>David,
>> Is there a way I can
>> recatalog all the log backups so I can use Enterprise
>> Manager's point an click interface to restore?
>Not easily. I guess you can write a TSQL script that
uses RESTORE HEADERONLY and based on that
>inserts data into the backup history tables in msdb.
Note that *this is not supported*! EM has an
>option to generate backuphistory as you select a backup
device in the restore dialog, but that isn't
>dine on a file basis, but on a backup basis, so using EM
to generate backuphistory, you would have
>to go through that dialog 15 times.
>> Will the
>> STOPAT parameter restore the first log backup, and all
>> subsequent backups, up to the STOPAT?
>No. All RESTORE commands only addresses one backup at a
time.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>
>"David Danh" <anonymous@.discussions.microsoft.com> wrote
in message
>news:370101c4a05d$53fc68b0$a501280a@.phx.gbl...
>> Backup Log DataBaseName to
>> DISK='\\ServerName\ShareName\Path\FileName.TRN' with
>> RetainDays=1, Description='Daily Backup Routine'
>> When I restore a database and logs to an alternate
>> server, I can restore the full database backup and the
>> first iteration of the log backups without any
problems.
>> The problem is with all subsequent log backups that
were
>> performed and apended to the file created by the above
>> statement. I know and can get to the subsequent
appended
>> logs via TSQL, but not an easy task if there are 15
>> appended log backups on the device. Is there a way I
can
>> recatalog all the log backups so I can use Enterprise
>> Manager's point an click interface to restore? Will
the
>> STOPAT parameter restore the first log backup, and all
>> subsequent backups, up to the STOPAT? The command used
>> to create the log backup is stated above.
>> Thanx soo much for your help,
>> D2
>
>.
>

Rebuilding Indexes While logshipping

We implemented logshipping on one of our database and the log is shipped via
wan to different destination.it works great but on weekends we do rebuild
indexes for that databases which generates huge log and it takes forever to
copy that log at least two days.is there a work around for it.
Thanks,
We had the same problem, so we stopped rebuilding index's until a solution
is found. It was more important to have disaster recovery than index's that
are not defragged.
Sorry cant help more.
regards
steve
"chinn" <chinn@.discussions.microsoft.com> wrote in message
news:DAF0B62E-AC27-4766-8366-371101325AD4@.microsoft.com...
> We implemented logshipping on one of our database and the log is shipped
> via
> wan to different destination.it works great but on weekends we do rebuild
> indexes for that databases which generates huge log and it takes forever
> to
> copy that log at least two days.is there a work around for it.
> Thanks,
|||place the DB in bulk logged mode during index maintenance. this will reduce
logging for index changs.
Greg Jackson
PDX, Oregon
|||Actually that does not help with log shipping. While it will reduce the
amount of data sent to the transaction log the backup itself will include
ALL the changes and will be just as large.
Andrew J. Kelly SQL MVP
"pdxJaxon" <GregoryAJackson@.Hotmail.com> wrote in message
news:%233o4dsUQGHA.5924@.TK2MSFTNGP09.phx.gbl...
> place the DB in bulk logged mode during index maintenance. this will
> reduce logging for index changs.
>
> Greg Jackson
> PDX, Oregon
>
|||I agree with Andrew because i tested it and it didn't make a difference.
"Andrew J. Kelly" wrote:

> Actually that does not help with log shipping. While it will reduce the
> amount of data sent to the transaction log the backup itself will include
> ALL the changes and will be just as large.
> --
> Andrew J. Kelly SQL MVP
>
> "pdxJaxon" <GregoryAJackson@.Hotmail.com> wrote in message
> news:%233o4dsUQGHA.5924@.TK2MSFTNGP09.phx.gbl...
>
>
|||One thing you should look at is only rebuild indexes that actually need it.
This KB should be helpful and there is a sample script in BooksOnLine under
DBCC SHOWCONTIG that will only reindex the indexes that are fragmented
beyond a certain point. This should cut down the amount that is being
logged dramatically.
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx
Andrew J. Kelly SQL MVP
"chinn" <chinn@.discussions.microsoft.com> wrote in message
news:FF010CDA-3598-4607-8DE2-0BECECE5593D@.microsoft.com...[vbcol=seagreen]
>I agree with Andrew because i tested it and it didn't make a difference.
> "Andrew J. Kelly" wrote:
|||hmm...that's too bad.
How about:
1. disable Log Shipping
2. Perform Index Maintenance
3. ReSeed your Standby DB
4. Start logshipping back up
This is a pain, but MUCH better than NOT doing index maintenance...
GAJ

Rebuilding Indexes While logshipping

We implemented logshipping on one of our database and the log is shipped via
wan to different destination.it works great but on weekends we do rebuild
indexes for that databases which generates huge log and it takes forever to
copy that log at least two days.is there a work around for it.
Thanks,We had the same problem, so we stopped rebuilding index's until a solution
is found. It was more important to have disaster recovery than index's that
are not defragged.
Sorry cant help more.
regards
steve
"chinn" <chinn@.discussions.microsoft.com> wrote in message
news:DAF0B62E-AC27-4766-8366-371101325AD4@.microsoft.com...
> We implemented logshipping on one of our database and the log is shipped
> via
> wan to different destination.it works great but on weekends we do rebuild
> indexes for that databases which generates huge log and it takes forever
> to
> copy that log at least two days.is there a work around for it.
> Thanks,|||place the DB in bulk logged mode during index maintenance. this will reduce
logging for index changs.
Greg Jackson
PDX, Oregon|||Actually that does not help with log shipping. While it will reduce the
amount of data sent to the transaction log the backup itself will include
ALL the changes and will be just as large.
Andrew J. Kelly SQL MVP
"pdxJaxon" <GregoryAJackson@.Hotmail.com> wrote in message
news:%233o4dsUQGHA.5924@.TK2MSFTNGP09.phx.gbl...
> place the DB in bulk logged mode during index maintenance. this will
> reduce logging for index changs.
>
> Greg Jackson
> PDX, Oregon
>|||I agree with Andrew because i tested it and it didn't make a difference.
"Andrew J. Kelly" wrote:

> Actually that does not help with log shipping. While it will reduce the
> amount of data sent to the transaction log the backup itself will include
> ALL the changes and will be just as large.
> --
> Andrew J. Kelly SQL MVP
>
> "pdxJaxon" <GregoryAJackson@.Hotmail.com> wrote in message
> news:%233o4dsUQGHA.5924@.TK2MSFTNGP09.phx.gbl...
>
>|||One thing you should look at is only rebuild indexes that actually need it.
This KB should be helpful and there is a sample script in BooksOnLine under
DBCC SHOWCONTIG that will only reindex the indexes that are fragmented
beyond a certain point. This should cut down the amount that is being
logged dramatically.
http://www.microsoft.com/technet/pr...n/ss2kidbp.mspx
Andrew J. Kelly SQL MVP
"chinn" <chinn@.discussions.microsoft.com> wrote in message
news:FF010CDA-3598-4607-8DE2-0BECECE5593D@.microsoft.com...[vbcol=seagreen]
>I agree with Andrew because i tested it and it didn't make a difference.
> "Andrew J. Kelly" wrote:
>|||hmm...that's too bad.
How about:
1. disable Log Shipping
2. Perform Index Maintenance
3. ReSeed your Standby DB
4. Start logshipping back up
This is a pain, but MUCH better than NOT doing index maintenance...
GAJsql

Rebuilding Indexes While logshipping

We implemented logshipping on one of our database and the log is shipped via
wan to different destination.it works great but on weekends we do rebuild
indexes for that databases which generates huge log and it takes forever to
copy that log at least two days.is there a work around for it.
Thanks,We had the same problem, so we stopped rebuilding index's until a solution
is found. It was more important to have disaster recovery than index's that
are not defragged.
Sorry cant help more.
regards
steve
"chinn" <chinn@.discussions.microsoft.com> wrote in message
news:DAF0B62E-AC27-4766-8366-371101325AD4@.microsoft.com...
> We implemented logshipping on one of our database and the log is shipped
> via
> wan to different destination.it works great but on weekends we do rebuild
> indexes for that databases which generates huge log and it takes forever
> to
> copy that log at least two days.is there a work around for it.
> Thanks,|||place the DB in bulk logged mode during index maintenance. this will reduce
logging for index changs.
Greg Jackson
PDX, Oregon|||Actually that does not help with log shipping. While it will reduce the
amount of data sent to the transaction log the backup itself will include
ALL the changes and will be just as large.
--
Andrew J. Kelly SQL MVP
"pdxJaxon" <GregoryAJackson@.Hotmail.com> wrote in message
news:%233o4dsUQGHA.5924@.TK2MSFTNGP09.phx.gbl...
> place the DB in bulk logged mode during index maintenance. this will
> reduce logging for index changs.
>
> Greg Jackson
> PDX, Oregon
>|||I agree with Andrew because i tested it and it didn't make a difference.
"Andrew J. Kelly" wrote:
> Actually that does not help with log shipping. While it will reduce the
> amount of data sent to the transaction log the backup itself will include
> ALL the changes and will be just as large.
> --
> Andrew J. Kelly SQL MVP
>
> "pdxJaxon" <GregoryAJackson@.Hotmail.com> wrote in message
> news:%233o4dsUQGHA.5924@.TK2MSFTNGP09.phx.gbl...
> > place the DB in bulk logged mode during index maintenance. this will
> > reduce logging for index changs.
> >
> >
> >
> > Greg Jackson
> > PDX, Oregon
> >
>
>|||One thing you should look at is only rebuild indexes that actually need it.
This KB should be helpful and there is a sample script in BooksOnLine under
DBCC SHOWCONTIG that will only reindex the indexes that are fragmented
beyond a certain point. This should cut down the amount that is being
logged dramatically.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
Andrew J. Kelly SQL MVP
"chinn" <chinn@.discussions.microsoft.com> wrote in message
news:FF010CDA-3598-4607-8DE2-0BECECE5593D@.microsoft.com...
>I agree with Andrew because i tested it and it didn't make a difference.
> "Andrew J. Kelly" wrote:
>> Actually that does not help with log shipping. While it will reduce the
>> amount of data sent to the transaction log the backup itself will include
>> ALL the changes and will be just as large.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "pdxJaxon" <GregoryAJackson@.Hotmail.com> wrote in message
>> news:%233o4dsUQGHA.5924@.TK2MSFTNGP09.phx.gbl...
>> > place the DB in bulk logged mode during index maintenance. this will
>> > reduce logging for index changs.
>> >
>> >
>> >
>> > Greg Jackson
>> > PDX, Oregon
>> >
>>|||hmm...that's too bad.
How about:
1. disable Log Shipping
2. Perform Index Maintenance
3. ReSeed your Standby DB
4. Start logshipping back up
This is a pain, but MUCH better than NOT doing index maintenance...
GAJ

Rebuild .LDF File

I'm running SQL Server 2000, trying to rebuild a
transaction log since I only have an .MDF file. I've tried
creating a new database with the same name, stopping SQL
Server, then inserting the real data file, and setting the
database to emergency mode, then running the DBBC
Rebuild_Log('dbname', 'c:\somepath') and that command
appears to execute ok in Query Analyzer, but the log file
is not created. Is there any other method for attaching
the .mdf when you don't have the valid .ldf that goes with
it. (I've tried sp_attach_single_file) and that doesn't
work either. I get an error message that says it can't
find the log file (this db was pulled off of another
system that had the log file path stored pointed to
another drive). Any help is appreciated.
Thanks
Sounds like you have tried "sp_attach_single_file_db" (although this isn't
what you typed). This command to use to attach a database that only has a
the data file. I would review BOL and try this command again. Also is it
possible that you data file is corrupted?
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"Steve" <anonymous@.discussions.microsoft.com> wrote in message
news:382a01c4a55e$ce066150$a301280a@.phx.gbl...
> I'm running SQL Server 2000, trying to rebuild a
> transaction log since I only have an .MDF file. I've tried
> creating a new database with the same name, stopping SQL
> Server, then inserting the real data file, and setting the
> database to emergency mode, then running the DBBC
> Rebuild_Log('dbname', 'c:\somepath') and that command
> appears to execute ok in Query Analyzer, but the log file
> is not created. Is there any other method for attaching
> the .mdf when you don't have the valid .ldf that goes with
> it. (I've tried sp_attach_single_file) and that doesn't
> work either. I get an error message that says it can't
> find the log file (this db was pulled off of another
> system that had the log file path stored pointed to
> another drive). Any help is appreciated.
> Thanks
|||If sp_attach_single_file doesn't work then see
http://www.nigelrivett.net/RecoverCorruptDatabase.html
"Steve" wrote:

> I'm running SQL Server 2000, trying to rebuild a
> transaction log since I only have an .MDF file. I've tried
> creating a new database with the same name, stopping SQL
> Server, then inserting the real data file, and setting the
> database to emergency mode, then running the DBBC
> Rebuild_Log('dbname', 'c:\somepath') and that command
> appears to execute ok in Query Analyzer, but the log file
> is not created. Is there any other method for attaching
> the .mdf when you don't have the valid .ldf that goes with
> it. (I've tried sp_attach_single_file) and that doesn't
> work either. I get an error message that says it can't
> find the log file (this db was pulled off of another
> system that had the log file path stored pointed to
> another drive). Any help is appreciated.
> Thanks
>
|||ok, that's what I meant, I didn't check the exact syntax,
but the "sp_attach_single_file_db" doesn't work... I don't
believe the .mdf data file is corrupted. All error
messages seem to point to the log file.

>--Original Message--
>Sounds like you have tried "sp_attach_single_file_db"
(although this isn't
>what you typed). This command to use to attach a
database that only has a
>the data file. I would review BOL and try this command
again. Also is it
>possible that you data file is corrupted?
>--
>----
--
>----
--
>-
>Need SQL Server Examples check out my website
>http://www.geocities.com/sqlserverexamples
>
>"Steve" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:382a01c4a55e$ce066150$a301280a@.phx.gbl...
tried[vbcol=seagreen]
the[vbcol=seagreen]
file[vbcol=seagreen]
with
>
>.
>
|||Ok, I just tried your instructions and it didn't work.
The database is in emergency mode, and I can't see any of
the tables, and when I try to setup a dts, I get an error
saying that it can't initialize the database.
[vbcol=seagreen]
>--Original Message--
>If sp_attach_single_file doesn't work then see
>http://www.nigelrivett.net/RecoverCorruptDatabase.html
>"Steve" wrote:
tried[vbcol=seagreen]
SQL[vbcol=seagreen]
the[vbcol=seagreen]
file[vbcol=seagreen]
with
>.
>

Rebuild .LDF File

I'm running SQL Server 2000, trying to rebuild a
transaction log since I only have an .MDF file. I've tried
creating a new database with the same name, stopping SQL
Server, then inserting the real data file, and setting the
database to emergency mode, then running the DBBC
Rebuild_Log('dbname', 'c:\somepath') and that command
appears to execute ok in Query Analyzer, but the log file
is not created. Is there any other method for attaching
the .mdf when you don't have the valid .ldf that goes with
it. (I've tried sp_attach_single_file) and that doesn't
work either. I get an error message that says it can't
find the log file (this db was pulled off of another
system that had the log file path stored pointed to
another drive). Any help is appreciated.
ThanksSounds like you have tried "sp_attach_single_file_db" (although this isn't
what you typed). This command to use to attach a database that only has a
the data file. I would review BOL and try this command again. Also is it
possible that you data file is corrupted?
--
----
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"Steve" <anonymous@.discussions.microsoft.com> wrote in message
news:382a01c4a55e$ce066150$a301280a@.phx.gbl...
> I'm running SQL Server 2000, trying to rebuild a
> transaction log since I only have an .MDF file. I've tried
> creating a new database with the same name, stopping SQL
> Server, then inserting the real data file, and setting the
> database to emergency mode, then running the DBBC
> Rebuild_Log('dbname', 'c:\somepath') and that command
> appears to execute ok in Query Analyzer, but the log file
> is not created. Is there any other method for attaching
> the .mdf when you don't have the valid .ldf that goes with
> it. (I've tried sp_attach_single_file) and that doesn't
> work either. I get an error message that says it can't
> find the log file (this db was pulled off of another
> system that had the log file path stored pointed to
> another drive). Any help is appreciated.
> Thanks|||If sp_attach_single_file doesn't work then see
http://www.nigelrivett.net/RecoverCorruptDatabase.html
"Steve" wrote:
> I'm running SQL Server 2000, trying to rebuild a
> transaction log since I only have an .MDF file. I've tried
> creating a new database with the same name, stopping SQL
> Server, then inserting the real data file, and setting the
> database to emergency mode, then running the DBBC
> Rebuild_Log('dbname', 'c:\somepath') and that command
> appears to execute ok in Query Analyzer, but the log file
> is not created. Is there any other method for attaching
> the .mdf when you don't have the valid .ldf that goes with
> it. (I've tried sp_attach_single_file) and that doesn't
> work either. I get an error message that says it can't
> find the log file (this db was pulled off of another
> system that had the log file path stored pointed to
> another drive). Any help is appreciated.
> Thanks
>|||ok, that's what I meant, I didn't check the exact syntax,
but the "sp_attach_single_file_db" doesn't work... I don't
believe the .mdf data file is corrupted. All error
messages seem to point to the log file.
>--Original Message--
>Sounds like you have tried "sp_attach_single_file_db"
(although this isn't
>what you typed). This command to use to attach a
database that only has a
>the data file. I would review BOL and try this command
again. Also is it
>possible that you data file is corrupted?
>--
>----
--
>----
--
>-
>Need SQL Server Examples check out my website
>http://www.geocities.com/sqlserverexamples
>
>"Steve" <anonymous@.discussions.microsoft.com> wrote in
message
>news:382a01c4a55e$ce066150$a301280a@.phx.gbl...
>> I'm running SQL Server 2000, trying to rebuild a
>> transaction log since I only have an .MDF file. I've
tried
>> creating a new database with the same name, stopping SQL
>> Server, then inserting the real data file, and setting
the
>> database to emergency mode, then running the DBBC
>> Rebuild_Log('dbname', 'c:\somepath') and that command
>> appears to execute ok in Query Analyzer, but the log
file
>> is not created. Is there any other method for attaching
>> the .mdf when you don't have the valid .ldf that goes
with
>> it. (I've tried sp_attach_single_file) and that doesn't
>> work either. I get an error message that says it can't
>> find the log file (this db was pulled off of another
>> system that had the log file path stored pointed to
>> another drive). Any help is appreciated.
>> Thanks
>
>.
>|||Hi Steve.
I have a feeling that the reason it didn't work is because
you did not detatch the database first using sp_detach_db,
though that is just a gut feeling.
Unfortunatly now you have a problem, anyway you have three
choices
1. Use Nigels very interesting and funky method to restore
it
2. Restore it from backup
3. Have a pretend nervous breakdown, take down your pants
and run from the office (be it slowly) screaming (that
SHOULD stop your boss from shouting at you).
nb if you have the original database try it again either
back it up, or try an sp_detatch_db.
Peter
"There is no such thing as public opinion. There is only
published opinion."
Winston Churchill
>--Original Message--
>I'm running SQL Server 2000, trying to rebuild a
>transaction log since I only have an .MDF file. I've
tried
>creating a new database with the same name, stopping SQL
>Server, then inserting the real data file, and setting
the
>database to emergency mode, then running the DBBC
>Rebuild_Log('dbname', 'c:\somepath') and that command
>appears to execute ok in Query Analyzer, but the log file
>is not created. Is there any other method for attaching
>the .mdf when you don't have the valid .ldf that goes
with
>it. (I've tried sp_attach_single_file) and that doesn't
>work either. I get an error message that says it can't
>find the log file (this db was pulled off of another
>system that had the log file path stored pointed to
>another drive). Any help is appreciated.
>Thanks
>.
>|||Ok, I just tried your instructions and it didn't work.
The database is in emergency mode, and I can't see any of
the tables, and when I try to setup a dts, I get an error
saying that it can't initialize the database.
>--Original Message--
>If sp_attach_single_file doesn't work then see
>http://www.nigelrivett.net/RecoverCorruptDatabase.html
>"Steve" wrote:
>> I'm running SQL Server 2000, trying to rebuild a
>> transaction log since I only have an .MDF file. I've
tried
>> creating a new database with the same name, stopping
SQL
>> Server, then inserting the real data file, and setting
the
>> database to emergency mode, then running the DBBC
>> Rebuild_Log('dbname', 'c:\somepath') and that command
>> appears to execute ok in Query Analyzer, but the log
file
>> is not created. Is there any other method for attaching
>> the .mdf when you don't have the valid .ldf that goes
with
>> it. (I've tried sp_attach_single_file) and that doesn't
>> work either. I get an error message that says it can't
>> find the log file (this db was pulled off of another
>> system that had the log file path stored pointed to
>> another drive). Any help is appreciated.
>> Thanks
>.
>|||I'll buy that... I received the file from a client, who
probably just did a standard detach through EM. I'll
probably have to resort to trying to get a hold of
the .BAK file. However I might pull the 3rd suggestion
just for fun.
Thanks
>--Original Message--
>Hi Steve.
>I have a feeling that the reason it didn't work is
because
>you did not detatch the database first using
sp_detach_db,
>though that is just a gut feeling.
>Unfortunatly now you have a problem, anyway you have
three
>choices
>1. Use Nigels very interesting and funky method to
restore
>it
>2. Restore it from backup
>3. Have a pretend nervous breakdown, take down your pants
>and run from the office (be it slowly) screaming (that
>SHOULD stop your boss from shouting at you).
>nb if you have the original database try it again either
>back it up, or try an sp_detatch_db.
>Peter
>"There is no such thing as public opinion. There is only
>published opinion."
>Winston Churchill
>
>>--Original Message--
>>I'm running SQL Server 2000, trying to rebuild a
>>transaction log since I only have an .MDF file. I've
>tried
>>creating a new database with the same name, stopping SQL
>>Server, then inserting the real data file, and setting
>the
>>database to emergency mode, then running the DBBC
>>Rebuild_Log('dbname', 'c:\somepath') and that command
>>appears to execute ok in Query Analyzer, but the log
file
>>is not created. Is there any other method for attaching
>>the .mdf when you don't have the valid .ldf that goes
>with
>>it. (I've tried sp_attach_single_file) and that doesn't
>>work either. I get an error message that says it can't
>>find the log file (this db was pulled off of another
>>system that had the log file path stored pointed to
>>another drive). Any help is appreciated.
>>Thanks
>>.
>.
>|||Other ways of stopping you boss from shouting at you
include superglue...
>--Original Message--
>I'll buy that... I received the file from a client, who
>probably just did a standard detach through EM. I'll
>probably have to resort to trying to get a hold of
>the .BAK file. However I might pull the 3rd suggestion
>just for fun.
>Thanks
>
>>--Original Message--
>>Hi Steve.
>>I have a feeling that the reason it didn't work is
>because
>>you did not detatch the database first using
>sp_detach_db,
>>though that is just a gut feeling.
>>Unfortunatly now you have a problem, anyway you have
>three
>>choices
>>1. Use Nigels very interesting and funky method to
>restore
>>it
>>2. Restore it from backup
>>3. Have a pretend nervous breakdown, take down your
pants
>>and run from the office (be it slowly) screaming (that
>>SHOULD stop your boss from shouting at you).
>>nb if you have the original database try it again either
>>back it up, or try an sp_detatch_db.
>>Peter
>>"There is no such thing as public opinion. There is only
>>published opinion."
>>Winston Churchill
>>
>>--Original Message--
>>I'm running SQL Server 2000, trying to rebuild a
>>transaction log since I only have an .MDF file. I've
>>tried
>>creating a new database with the same name, stopping
SQL
>>Server, then inserting the real data file, and setting
>>the
>>database to emergency mode, then running the DBBC
>>Rebuild_Log('dbname', 'c:\somepath') and that command
>>appears to execute ok in Query Analyzer, but the log
>file
>>is not created. Is there any other method for attaching
>>the .mdf when you don't have the valid .ldf that goes
>>with
>>it. (I've tried sp_attach_single_file) and that doesn't
>>work either. I get an error message that says it can't
>>find the log file (this db was pulled off of another
>>system that had the log file path stored pointed to
>>another drive). Any help is appreciated.
>>Thanks
>>.
>>.
>.
>

Rebuilbm not working

I don't have a new sql log.
I checked Server network utility and shared memory is enabled.
How can I verify if Shared Memory is loaded?
I rebooted the server and I get the same error.
Look at the SQL Server errolog and verify that Shared Memory is loaded. If
> not, reboot the machine. Rebuildm makes a shared memory connection so if
> shared memory is not loaded it will fail.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
You should have an errorlog file, each time SQL Server starts it creates such a file. The name of the file is
"errorlog".
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"joj100" <joj100@.discussions.microsoft.com> wrote in message
news:6587E07D-DE45-4B81-BDB8-B9FC8C9DB0E7@.microsoft.com...[vbcol=seagreen]
> I don't have a new sql log.
> I checked Server network utility and shared memory is enabled.
> How can I verify if Shared Memory is loaded?
> I rebooted the server and I get the same error.
>
> Look at the SQL Server errolog and verify that Shared Memory is loaded. If

Rebuilbm not working

I don't have a new sql log.
I checked Server network utility and shared memory is enabled.
How can I verify if Shared Memory is loaded?
I rebooted the server and I get the same error.
Look at the SQL Server errolog and verify that Shared Memory is loaded. If
> not, reboot the machine. Rebuildm makes a shared memory connection so if
> shared memory is not loaded it will fail.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>You should have an errorlog file, each time SQL Server starts it creates suc
h a file. The name of the file is
"errorlog".
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"joj100" <joj100@.discussions.microsoft.com> wrote in message
news:6587E07D-DE45-4B81-BDB8-B9FC8C9DB0E7@.microsoft.com...[vbcol=seagreen]
> I don't have a new sql log.
> I checked Server network utility and shared memory is enabled.
> How can I verify if Shared Memory is loaded?
> I rebooted the server and I get the same error.
>
> Look at the SQL Server errolog and verify that Shared Memory is loaded. I
f

Rebooting SQL server

We have a SQL server 2000 server residing on an iSeries intel card which is being rebooted once per week. The server log has the following two entries:

When shutting down:
1. SQL Server terminating because of system shutdown.

During startup:
1. Recovery of database "ERPDB" is complete
2. Two transactions rolled back in "ERPDB".
3. Recovery is checkpointing "ERPDB"
4. Recovery complete.

The database is 70GB and is a copy of an iSeries database. The recovery model is set to 'Simple' but I am still concerned if the above messages indicate that the server is shut down without properly waiting for replication tasks to complete?

Rgds

Bertrand

Is there any reason for the reboot every week?

The message on error log is by default as the services for SQL Server has been stopped when there are connections on SQL Server are idle or performing any activity.

The messages during the startup are also by default as it need to bring up the database and those rolledback transactions are due to when the SQL was stopping these were initiated. It is better to stop the SQL Server services when there is no such activity on server.

Rebooting SAN with SQL Data Files

Please help.
We are rebooting our SAN tonight and it has a lot of our Data and Log files
on it, including the master and msdb data files. Approximately 35 of our SQL
Servers are storing files on this SAN. Will SQL Server gracefully recover
from the reboot or will I need to stop the services prior to the reboot or is
there anything else I need to do? Thank you in advance for any help.
James
Are you asking if you can reboot the SAN while SQL Server is still running?
If so then I would not recommend that at all. You are likely to come up
with 35 db's in suspect mode. You should stop all the services to ensure no
one is writing to the data or log files when you reboot.
Andrew J. Kelly SQL MVP
"Hex Caliber" <hex@.caliber.com> wrote in message
news:C5EAC564-2231-46D2-BC59-B49627A757B6@.microsoft.com...
> Please help.
> We are rebooting our SAN tonight and it has a lot of our Data and Log
> files
> on it, including the master and msdb data files. Approximately 35 of our
> SQL
> Servers are storing files on this SAN. Will SQL Server gracefully recover
> from the reboot or will I need to stop the services prior to the reboot or
> is
> there anything else I need to do? Thank you in advance for any help.
> James
|||If at all possible I would recommend to shutdown any and all hosts
connected to your SAN before rebooting it. What kind of SAN is it? Do
you have multiple storage processors? Are you completely rebooting the
disk enclosures as well as the storage processors? You could consider
trespassing LUNs over and rebooting the storage processors in series
rather than all at once.
While I don't have any direct experience with yanking the drives out
from under SQL, I can't imagine it would be very good to do. You will
probably be facing data corruption lost transactions and serious data
inconsistency.
tM
Hex Caliber wrote:

> Please help.
> We are rebooting our SAN tonight and it has a lot of our Data and Log files
> on it, including the master and msdb data files. Approximately 35 of our SQL
> Servers are storing files on this SAN. Will SQL Server gracefully recover
> from the reboot or will I need to stop the services prior to the reboot or is
> there anything else I need to do? Thank you in advance for any help.
> James
|||Thank you, both of you. I'm not sure of the answers to TM's questions, but
it sounds like our plan will be to shut down the SQL Servers and then go
ahead with the SAN fix. Thanks again.
"Hex Caliber" wrote:

> Please help.
> We are rebooting our SAN tonight and it has a lot of our Data and Log files
> on it, including the master and msdb data files. Approximately 35 of our SQL
> Servers are storing files on this SAN. Will SQL Server gracefully recover
> from the reboot or will I need to stop the services prior to the reboot or is
> there anything else I need to do? Thank you in advance for any help.
> James
|||If I were you, shut the servers down, not just SQL Server.
The OS will not like it, and some NT Admins tend to put pagefiles on the
nice big SAN drives, resulting in your boxes blue screening when the drives
drop out from under the OS.
Rather safe than sorry....
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Hex Caliber" <hex@.caliber.com> wrote in message
news:21B570FA-8773-4994-9A81-465243F59286@.microsoft.com...
> Thank you, both of you. I'm not sure of the answers to TM's questions,
but[vbcol=seagreen]
> it sounds like our plan will be to shut down the SQL Servers and then go
> ahead with the SAN fix. Thanks again.
> "Hex Caliber" wrote:
files[vbcol=seagreen]
our SQL[vbcol=seagreen]
recover[vbcol=seagreen]
or is[vbcol=seagreen]

Rebooting SAN with SQL Data Files

Please help.
We are rebooting our SAN tonight and it has a lot of our Data and Log files
on it, including the master and msdb data files. Approximately 35 of our SQ
L
Servers are storing files on this SAN. Will SQL Server gracefully recover
from the reboot or will I need to stop the services prior to the reboot or i
s
there anything else I need to do? Thank you in advance for any help.
JamesAre you asking if you can reboot the SAN while SQL Server is still running?
If so then I would not recommend that at all. You are likely to come up
with 35 db's in suspect mode. You should stop all the services to ensure no
one is writing to the data or log files when you reboot.
Andrew J. Kelly SQL MVP
"Hex Caliber" <hex@.caliber.com> wrote in message
news:C5EAC564-2231-46D2-BC59-B49627A757B6@.microsoft.com...
> Please help.
> We are rebooting our SAN tonight and it has a lot of our Data and Log
> files
> on it, including the master and msdb data files. Approximately 35 of our
> SQL
> Servers are storing files on this SAN. Will SQL Server gracefully recover
> from the reboot or will I need to stop the services prior to the reboot or
> is
> there anything else I need to do? Thank you in advance for any help.
> James|||If at all possible I would recommend to shutdown any and all hosts
connected to your SAN before rebooting it. What kind of SAN is it? Do
you have multiple storage processors? Are you completely rebooting the
disk enclosures as well as the storage processors? You could consider
trespassing LUNs over and rebooting the storage processors in series
rather than all at once.
While I don't have any direct experience with yanking the drives out
from under SQL, I can't imagine it would be very good to do. You will
probably be facing data corruption lost transactions and serious data
inconsistency.
tM
Hex Caliber wrote:

> Please help.
> We are rebooting our SAN tonight and it has a lot of our Data and Log file
s
> on it, including the master and msdb data files. Approximately 35 of our
SQL
> Servers are storing files on this SAN. Will SQL Server gracefully recover
> from the reboot or will I need to stop the services prior to the reboot or
is
> there anything else I need to do? Thank you in advance for any help.
> James|||Thank you, both of you. I'm not sure of the answers to TM's questions, but
it sounds like our plan will be to shut down the SQL Servers and then go
ahead with the SAN fix. Thanks again.
"Hex Caliber" wrote:

> Please help.
> We are rebooting our SAN tonight and it has a lot of our Data and Log file
s
> on it, including the master and msdb data files. Approximately 35 of our
SQL
> Servers are storing files on this SAN. Will SQL Server gracefully recover
> from the reboot or will I need to stop the services prior to the reboot or
is
> there anything else I need to do? Thank you in advance for any help.
> James|||If I were you, shut the servers down, not just SQL Server.
The OS will not like it, and some NT Admins tend to put pagefiles on the
nice big SAN drives, resulting in your boxes blue screening when the drives
drop out from under the OS.
Rather safe than sorry....
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Hex Caliber" <hex@.caliber.com> wrote in message
news:21B570FA-8773-4994-9A81-465243F59286@.microsoft.com...
> Thank you, both of you. I'm not sure of the answers to TM's questions,
but[vbcol=seagreen]
> it sounds like our plan will be to shut down the SQL Servers and then go
> ahead with the SAN fix. Thanks again.
> "Hex Caliber" wrote:
>
files[vbcol=seagreen]
our SQL[vbcol=seagreen]
recover[vbcol=seagreen]
or is[vbcol=seagreen]