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

Rebuilding the system merge repl indexes

Hi,

We have a client that has a large (5Gb) database replicated to 13 subscribers, the publisher is Sql 2005, the subscribers are Sql Express. The publication has as few filtered articles too. I have found that after several months of continuous running Replication Monitor is taking a long time to report history on each subscriber.

Do people tend to rebuild the indexes on the system merge replication tables on production servers, or should the standard replication jobs take care of this?

Thanks for your help

Graham

1. What is the retention period?

2. Was the cleanup job run?

|||

The retention period is 14 days for all subscribers.

The Agent history clean uo: Distributor job (publisher and distributor are on the same box), was last run yesterday successfully.

The Distribution Clean up: Distributor job has never been run and it not enabled.

The Replication monitoring refresher for Distributor job has never been run and is not enabled.

|||

1. Did the replication Monitor running all the time (on the subscriber)?

2. If you stop and re-start to launch it, does it still take a long time to refresh "sync status"?

3. if the repl monitor still takes a long time to refresh the sync status, can you turn on the profiler to see which RPC call takes unexpected long execution time? (I suspect the SQL Agent job history continuous to grow)

This posting is provided "AS IS" with no warranties, and confers no rights

|||

Replication does not do any index rebuilding or any defragmentation. It may be a good idea to create a job that does this for you during off-peak hours.

You may also want to monitor what's going on in the background while you're refreshing, replmonitor does make use of temp tables as well and it may have some contention with existing replication metadata tables that we're trying to improve for the next release of Katmai.

|||

Things took at turn for the worse yesterday. I had to reinitialize one of the subscribers because for some reason the publisher had decided to delete its merge meta data (the thing that normally happens when the subscriber does not sync for more than the retention period) dispite it sync'ing the day before. When I did the reinit, it then told me the snapshot was obsolete and I had to re-generate it. When I re-generated the snapshot it failed with a timeout after being stuck at 48% for 30minutes. Then all my other subscribers failed because of the same reason - the snapshot was obsolete.

In the end I tore down replication and re-created the publication and added all the subscribers again (this took all day too).

Now replication monitor is a lot more responsive.

Thanks for everyones help.

Rebuilding the master Database

I have a copy of SQL Server Express on a clients computer.

When i try & restart the services it fails with the following error:-

Error: 9003, Severity: 20, State1.

It looks like the master database has become corrupt & needs rebuilding.

I have found a utility rebuildm.exe that repairs the master db but unfortunately it is not supported in sql 2005.

Does anyone have any other suggestions on how to repair the master db.

Thanks.

i think this will help u

http://geekswithblogs.net/mskoolaid/archive/2005/12/17/63413.aspx

Madhu

|||

Rebuildm.exe is used in sql 2000 .....i think you can rebuild as below,

copy the sql server express exe file to your local hard disk and then in cmd go to relevant path where the setup file resides and run the below code in command prompt.........

start /wait <CD or DVD Drive>\setup.exe /qn INSTANCENAME=<InstanceName> REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD=<NewStrongPassword>

This works with sql 2005 and i think it will work with sql express also.........pls correct me if am wrong

Thanxx

Deepak

|||

Thanks for that.

Silly question but will the instance name be master & will the SAPWD be sa also do you think i need to use < > between instancename & sa

Does this look good to you guys.

setup.exe /qn INSTANCENAME=<master> REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD=<sa>

|||

Go to the appropriate path where your sql server setup.exe exist in the command prompt........I assume its in C:\test folder .......then command will be like this,

C:\Test> start /wait \setup.exe /qn INSTANCENAME="SQLEXPRESS" REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD="XXXXX"

SQL Server Express always installs a named instance (SQLExpress) unless you select a default instance.

http://technet.microsoft.com/en-us/library/ms143744.aspx

I am not sure if this is correct just try|||

Thanks guys.

Got it to work.

Respect.

Rebuilding the master Database

I have a copy of SQL Server Express on a clients computer.

When i try & restart the services it fails with the following error:-

Error: 9003, Severity: 20, State1.

It looks like the master database has become corrupt & needs rebuilding.

I have found a utility rebuildm.exe that repairs the master db but unfortunately it is not supported in sql 2005.

Does anyone have any other suggestions on how to repair the master db.

Thanks.

i think this will help u

http://geekswithblogs.net/mskoolaid/archive/2005/12/17/63413.aspx

Madhu

|||

Rebuildm.exe is used in sql 2000 .....i think you can rebuild as below,

copy the sql server express exe file to your local hard disk and then in cmd go to relevant path where the setup file resides and run the below code in command prompt.........

start /wait <CD or DVD Drive>\setup.exe /qn INSTANCENAME=<InstanceName> REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD=<NewStrongPassword>

This works with sql 2005 and i think it will work with sql express also.........pls correct me if am wrong

Thanxx

Deepak

|||

Thanks for that.

Silly question but will the instance name be master & will the SAPWD be sa also do you think i need to use < > between instancename & sa

Does this look good to you guys.

setup.exe /qn INSTANCENAME=<master> REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD=<sa>

|||

Go to the appropriate path where your sql server setup.exe exist in the command prompt........I assume its in C:\test folder .......then command will be like this,

C:\Test> start /wait \setup.exe /qn INSTANCENAME="SQLEXPRESS" REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD="XXXXX"

SQL Server Express always installs a named instance (SQLExpress) unless you select a default instance.

http://technet.microsoft.com/en-us/library/ms143744.aspx

I am not sure if this is correct just try|||

Thanks guys.

Got it to work.

Respect.

Rebuild SQL Server Express database on a SQL Server 2000

Hi,
Anyone know if it's possible to rebuild a
SQL Server Express database on a SQL Server 2000?
Thanks!
Regards
D.Dahab wrote:
> Hi,
> Anyone know if it's possible to rebuild a
> SQL Server Express database on a SQL Server 2000?
> Thanks!
> Regards
> D.
>
No - you can't go from SQL2005 to SQL2000.
Regards
Steen Schlter Persson
Database Administrator / System Administrator|||The easiest way is to use SSIS Import and Export Wizard to migrate the data
(assuming you have a higher version of SQL Server 2005 around somewhere).
This way the data mappings will get done for you if you have used some
incompatible features.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||Thanks Paul!
D.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23UKL2oGbHHA.4312@.TK2MSFTNGP05.phx.gbl...
> The easiest way is to use SSIS Import and Export Wizard to migrate the
> data (assuming you have a higher version of SQL Server 2005 around
> somewhere). This way the data mappings will get done for you if you have
> used some incompatible features.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>

Rebuild SQL Server Express database on a SQL Server 2000

Hi,
Anyone know if it's possible to rebuild a
SQL Server Express database on a SQL Server 2000?
Thanks!
Regards
D.Dahab wrote:
> Hi,
> Anyone know if it's possible to rebuild a
> SQL Server Express database on a SQL Server 2000?
> Thanks!
> Regards
> D.
>
No - you can't go from SQL2005 to SQL2000.
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator|||The easiest way is to use SSIS Import and Export Wizard to migrate the data
(assuming you have a higher version of SQL Server 2005 around somewhere).
This way the data mappings will get done for you if you have used some
incompatible features.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||Thanks Paul!
D.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23UKL2oGbHHA.4312@.TK2MSFTNGP05.phx.gbl...
> The easiest way is to use SSIS Import and Export Wizard to migrate the
> data (assuming you have a higher version of SQL Server 2005 around
> somewhere). This way the data mappings will get done for you if you have
> used some incompatible features.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>

Rebuild indexes affects other databases?

Hi all,
I'm facing a very strange problem. I have two databases (in
particular) that are attached to SQL Server 2005 Express (say, #1 and
#2), and I have two queries (among others) that I use to access their
data. Now, after rebuilding all indexes in database #1, the query to
access that database seems to be very fast. Then, I rebuild the
indexes in database #2, but the query to access database #1 takes about
6 times longer. However, the query to access database #2 is now very
fast. Rebuilding database #1 speeds access to #1 at the expense of
slowing down database #2. Here are the queries I'm using:
Query #1:
SELECT [EXDT] AS [Date], [AMT] AS [Dividend], [SHR] AS [Factor]
FROM KRAM_Splits.dbo.Data
WHERE [No] = 10230
ORDER BY [EXDT] ASC
Query #2:
SELECT [No], MAX([Symbol]) AS [Symbol], MAX([Company]) AS [Company],
MAX([SICCD]) AS [SICCD], MIN([Start_Date]) AS [Start_Date],
MAX([End_Date]) AS [End_Date]
FROM CO_History.dbo.Nos
WHERE [Symbol] = 'INTC'
GROUP BY [No]
ORDER BY [End_Date] DESC
Rebuild Query:
USE [CO_History] /* Or [KRAM_Splits] */
DECLARE @.TableName sysname
DECLARE cur_reindex CURSOR FOR
SELECT table_name
FROM information_schema.TABLES
WHERE table_type = 'base table'
OPEN cur_reindex
FETCH NEXT FROM cur_reindex INTO @.TableName
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'Reindexing ' + @.TableName + ' table'
DBCC DBREINDEX (@.TableName, ' ', 0)
FETCH NEXT FROM cur_reindex INTO @.TableName
END
CLOSE cur_reindex
DEALLOCATE cur_reindex
Both query #1 and #2 are prefixed by:
DBCC FREEPROCCACHE
DBCC DROPCLEANBUFFERS
Here are some timing statistics. I got these using SQL Server
Management Studio Express with client statistics enabled. The last
column is an average of the first five trials.
Time Statistics (Database #1 after rebuild of #1)
Client processing time 0 15 31 0 63 21.8
Total execution time 62 93 62 46 125 77.6
Wait time on server replies 62 78 31 46 62 55.8
Time Statistics (Database #1 after rebuild of #2)
Client processing time 15 0 0 0 16 6.2
Total execution time 296 390 421 390 359 371.2
Wait time on server replies 281 390 421 390 343 365
Time Statistics (Database #2 after rebuild of #2)
Client processing time 0 0 16 31 16 15.6667
Total execution time 78 46 62 62 78 62
Wait time on server replies 78 46 46 31 62 46.3333
Time Statistics (Database #1 after rebuild of #1)
Client processing time 16 31 0 16 0 12.6
Total execution time 78 46 62 109 62 71.4
Wait time on server replies 62 15 62 93 62 58.8
Time Statistics (Database #2 after rebuild of #1)
Client processing time 0 0 0 16 0 3.2
Total execution time 281 437 312 312 343 337
Wait time on server replies 281 437 312 296 343 333.8
What is going on here? Am I losing my mind!?
Thanks for any help!
Jonathan
Sounds like you don't have enough RAM. When you do a bunch of index
rebuilds, it's likely those pages stayed in memory long enough for you do
query the same DB and get good results. When you go to query the other DB,
it ages out those pages from memory and has to go to disk to get the new
ones. If you have lots of RAM, this can be mitigated.
To make it an apples to apples comparison try either of the following:
Method 1
1) run DBCC DROPCLEANBUFFERS before the index rebuild and run your query
2) rebuild the index
3) repeat step 1 and compare the results
This will show you how long it takes for both a fragmented and
non-fragmented index to get the data from the disk
Method 2
1) run your query a few of times, then take stats on the last one or two
2) rebuild your index
3) repeat 1 and compare the results
This will show you the performance when the data are cached.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
<jonathanve@.gmail.com> wrote in message
news:1140653001.018380.251370@.z14g2000cwz.googlegr oups.com...
Hi all,
I'm facing a very strange problem. I have two databases (in
particular) that are attached to SQL Server 2005 Express (say, #1 and
#2), and I have two queries (among others) that I use to access their
data. Now, after rebuilding all indexes in database #1, the query to
access that database seems to be very fast. Then, I rebuild the
indexes in database #2, but the query to access database #1 takes about
6 times longer. However, the query to access database #2 is now very
fast. Rebuilding database #1 speeds access to #1 at the expense of
slowing down database #2. Here are the queries I'm using:
Query #1:
SELECT [EXDT] AS [Date], [AMT] AS [Dividend], [SHR] AS [Factor]
FROM KRAM_Splits.dbo.Data
WHERE [No] = 10230
ORDER BY [EXDT] ASC
Query #2:
SELECT [No], MAX([Symbol]) AS [Symbol], MAX([Company]) AS [Company],
MAX([SICCD]) AS [SICCD], MIN([Start_Date]) AS [Start_Date],
MAX([End_Date]) AS [End_Date]
FROM CO_History.dbo.Nos
WHERE [Symbol] = 'INTC'
GROUP BY [No]
ORDER BY [End_Date] DESC
Rebuild Query:
USE [CO_History] /* Or [KRAM_Splits] */
DECLARE @.TableName sysname
DECLARE cur_reindex CURSOR FOR
SELECT table_name
FROM information_schema.TABLES
WHERE table_type = 'base table'
OPEN cur_reindex
FETCH NEXT FROM cur_reindex INTO @.TableName
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'Reindexing ' + @.TableName + ' table'
DBCC DBREINDEX (@.TableName, ' ', 0)
FETCH NEXT FROM cur_reindex INTO @.TableName
END
CLOSE cur_reindex
DEALLOCATE cur_reindex
Both query #1 and #2 are prefixed by:
DBCC FREEPROCCACHE
DBCC DROPCLEANBUFFERS
Here are some timing statistics. I got these using SQL Server
Management Studio Express with client statistics enabled. The last
column is an average of the first five trials.
Time Statistics (Database #1 after rebuild of #1)
Client processing time 0 15 31 0 63 21.8
Total execution time 62 93 62 46 125 77.6
Wait time on server replies 62 78 31 46 62 55.8
Time Statistics (Database #1 after rebuild of #2)
Client processing time 15 0 0 0 16 6.2
Total execution time 296 390 421 390 359 371.2
Wait time on server replies 281 390 421 390 343 365
Time Statistics (Database #2 after rebuild of #2)
Client processing time 0 0 16 31 16 15.6667
Total execution time 78 46 62 62 78 62
Wait time on server replies 78 46 46 31 62 46.3333
Time Statistics (Database #1 after rebuild of #1)
Client processing time 16 31 0 16 0 12.6
Total execution time 78 46 62 109 62 71.4
Wait time on server replies 62 15 62 93 62 58.8
Time Statistics (Database #2 after rebuild of #1)
Client processing time 0 0 0 16 0 3.2
Total execution time 281 437 312 312 343 337
Wait time on server replies 281 437 312 296 343 333.8
What is going on here? Am I losing my mind!?
Thanks for any help!
Jonathan
|||OK, I see what you mean. This computer has 512MB which is on the low
side.
But I'm unclear about one thing: After reindexing, the query seems to
take almost no time at all (~0 msec), which means that a good part is
in memory. But even without reindexing (like when I run the query on
database #2 after indexing database #1), wouldn't running the query a
few times put a lot of the pages from the query in memory so that it
would also take almost no time after that? It seems like even after
running the query a bunch of times, it still takes about 200 msec or
so, which is better than the first run (so it is caching something),
but not as fast as after a reindex. What's the reason behind this?
Also, is SQL Server 2005 a bit more memory hungry than MSDE (which is
what I used before)?
Thanks for the quick response!
Jonathan
sql

Rebuild indexes affects other databases?

Hi all,
I'm facing a very strange problem. I have two databases (in
particular) that are attached to SQL Server 2005 Express (say, #1 and
#2), and I have two queries (among others) that I use to access their
data. Now, after rebuilding all indexes in database #1, the query to
access that database seems to be very fast. Then, I rebuild the
indexes in database #2, but the query to access database #1 takes about
6 times longer. However, the query to access database #2 is now very
fast. Rebuilding database #1 speeds access to #1 at the expense of
slowing down database #2. Here are the queries I'm using:
Query #1:
SELECT [EXDT] AS [Date], [AMT] AS [Dividend], [SHR] AS [Factor]
FROM KRAM_Splits.dbo.Data
WHERE [No] = 10230
ORDER BY [EXDT] ASC
Query #2:
SELECT [No], MAX([Symbol]) AS [Symbol], MAX([Company]) AS [Company],
MAX([SICCD]) AS [SICCD], MIN([Start_Date]) AS [Start_Date],
MAX([End_Date]) AS [End_Date]
FROM CO_History.dbo.Nos
WHERE [Symbol] = 'INTC'
GROUP BY [No]
ORDER BY [End_Date] DESC
Rebuild Query:
USE [CO_History] /* Or [KRAM_Splits] */
DECLARE @.TableName sysname
DECLARE cur_reindex CURSOR FOR
SELECT table_name
FROM information_schema.TABLES
WHERE table_type = 'base table'
OPEN cur_reindex
FETCH NEXT FROM cur_reindex INTO @.TableName
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'Reindexing ' + @.TableName + ' table'
DBCC DBREINDEX (@.TableName, ' ', 0)
FETCH NEXT FROM cur_reindex INTO @.TableName
END
CLOSE cur_reindex
DEALLOCATE cur_reindex
Both query #1 and #2 are prefixed by:
DBCC FREEPROCCACHE
DBCC DROPCLEANBUFFERS
Here are some timing statistics. I got these using SQL Server
Management Studio Express with client statistics enabled. The last
column is an average of the first five trials.
Time Statistics (Database #1 after rebuild of #1)
Client processing time 0 15 31 0 63 21.8
Total execution time 62 93 62 46 125 77.6
Wait time on server replies 62 78 31 46 62 55.8
Time Statistics (Database #1 after rebuild of #2)
Client processing time 15 0 0 0 16 6.2
Total execution time 296 390 421 390 359 371.2
Wait time on server replies 281 390 421 390 343 365
Time Statistics (Database #2 after rebuild of #2)
Client processing time 0 0 16 31 16 15.6667
Total execution time 78 46 62 62 78 62
Wait time on server replies 78 46 46 31 62 46.3333
Time Statistics (Database #1 after rebuild of #1)
Client processing time 16 31 0 16 0 12.6
Total execution time 78 46 62 109 62 71.4
Wait time on server replies 62 15 62 93 62 58.8
Time Statistics (Database #2 after rebuild of #1)
Client processing time 0 0 0 16 0 3.2
Total execution time 281 437 312 312 343 337
Wait time on server replies 281 437 312 296 343 333.8
What is going on here? Am I losing my mind!?
Thanks for any help!
JonathanSounds like you don't have enough RAM. When you do a bunch of index
rebuilds, it's likely those pages stayed in memory long enough for you do
query the same DB and get good results. When you go to query the other DB,
it ages out those pages from memory and has to go to disk to get the new
ones. If you have lots of RAM, this can be mitigated.
To make it an apples to apples comparison try either of the following:
Method 1
1) run DBCC DROPCLEANBUFFERS before the index rebuild and run your query
2) rebuild the index
3) repeat step 1 and compare the results
This will show you how long it takes for both a fragmented and
non-fragmented index to get the data from the disk
Method 2
1) run your query a few of times, then take stats on the last one or two
2) rebuild your index
3) repeat 1 and compare the results
This will show you the performance when the data are cached.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
<jonathanve@.gmail.com> wrote in message
news:1140653001.018380.251370@.z14g2000cwz.googlegroups.com...
Hi all,
I'm facing a very strange problem. I have two databases (in
particular) that are attached to SQL Server 2005 Express (say, #1 and
#2), and I have two queries (among others) that I use to access their
data. Now, after rebuilding all indexes in database #1, the query to
access that database seems to be very fast. Then, I rebuild the
indexes in database #2, but the query to access database #1 takes about
6 times longer. However, the query to access database #2 is now very
fast. Rebuilding database #1 speeds access to #1 at the expense of
slowing down database #2. Here are the queries I'm using:
Query #1:
SELECT [EXDT] AS [Date], [AMT] AS [Dividend], [SHR] AS [Factor]
FROM KRAM_Splits.dbo.Data
WHERE [No] = 10230
ORDER BY [EXDT] ASC
Query #2:
SELECT [No], MAX([Symbol]) AS [Symbol], MAX([Company]) AS [Company],
MAX([SICCD]) AS [SICCD], MIN([Start_Date]) AS [Start_Date],
MAX([End_Date]) AS [End_Date]
FROM CO_History.dbo.Nos
WHERE [Symbol] = 'INTC'
GROUP BY [No]
ORDER BY [End_Date] DESC
Rebuild Query:
USE [CO_History] /* Or [KRAM_Splits] */
DECLARE @.TableName sysname
DECLARE cur_reindex CURSOR FOR
SELECT table_name
FROM information_schema.TABLES
WHERE table_type = 'base table'
OPEN cur_reindex
FETCH NEXT FROM cur_reindex INTO @.TableName
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'Reindexing ' + @.TableName + ' table'
DBCC DBREINDEX (@.TableName, ' ', 0)
FETCH NEXT FROM cur_reindex INTO @.TableName
END
CLOSE cur_reindex
DEALLOCATE cur_reindex
Both query #1 and #2 are prefixed by:
DBCC FREEPROCCACHE
DBCC DROPCLEANBUFFERS
Here are some timing statistics. I got these using SQL Server
Management Studio Express with client statistics enabled. The last
column is an average of the first five trials.
Time Statistics (Database #1 after rebuild of #1)
Client processing time 0 15 31 0 63 21.8
Total execution time 62 93 62 46 125 77.6
Wait time on server replies 62 78 31 46 62 55.8
Time Statistics (Database #1 after rebuild of #2)
Client processing time 15 0 0 0 16 6.2
Total execution time 296 390 421 390 359 371.2
Wait time on server replies 281 390 421 390 343 365
Time Statistics (Database #2 after rebuild of #2)
Client processing time 0 0 16 31 16 15.6667
Total execution time 78 46 62 62 78 62
Wait time on server replies 78 46 46 31 62 46.3333
Time Statistics (Database #1 after rebuild of #1)
Client processing time 16 31 0 16 0 12.6
Total execution time 78 46 62 109 62 71.4
Wait time on server replies 62 15 62 93 62 58.8
Time Statistics (Database #2 after rebuild of #1)
Client processing time 0 0 0 16 0 3.2
Total execution time 281 437 312 312 343 337
Wait time on server replies 281 437 312 296 343 333.8
What is going on here? Am I losing my mind!?
Thanks for any help!
Jonathan|||OK, I see what you mean. This computer has 512MB which is on the low
side.
But I'm unclear about one thing: After reindexing, the query seems to
take almost no time at all (~0 msec), which means that a good part is
in memory. But even without reindexing (like when I run the query on
database #2 after indexing database #1), wouldn't running the query a
few times put a lot of the pages from the query in memory so that it
would also take almost no time after that? It seems like even after
running the query a bunch of times, it still takes about 200 msec or
so, which is better than the first run (so it is caching something),
but not as fast as after a reindex. What's the reason behind this?
Also, is SQL Server 2005 a bit more memory hungry than MSDE (which is
what I used before)?
Thanks for the quick response!
Jonathan

Rebuild indexes affects other databases?

Hi all,
I'm facing a very strange problem. I have two databases (in
particular) that are attached to SQL Server 2005 Express (say, #1 and
#2), and I have two queries (among others) that I use to access their
data. Now, after rebuilding all indexes in database #1, the query to
access that database seems to be very fast. Then, I rebuild the
indexes in database #2, but the query to access database #1 takes about
6 times longer. However, the query to access database #2 is now very
fast. Rebuilding database #1 speeds access to #1 at the expense of
slowing down database #2. Here are the queries I'm using:
Query #1:
SELECT [EXDT] AS [Date], [AMT] AS [Dividend], [SHR] AS &
#91;Factor]
FROM KRAM_Splits.dbo.Data
WHERE [No] = 10230
ORDER BY [EXDT] ASC
Query #2:
SELECT [No], MAX([Symbol]) AS [Symbol], MAX([Company]) AS &#
91;Company],
MAX([SICCD]) AS [SICCD], MIN([Start_Date]) AS [Start_Date],
MAX([End_Date]) AS [End_Date]
FROM CO_History.dbo.Nos
WHERE [Symbol] = 'INTC'
GROUP BY [No]
ORDER BY [End_Date] DESC
Rebuild Query:
USE [CO_History] /* Or [KRAM_Splits] */
DECLARE @.TableName sysname
DECLARE cur_reindex CURSOR FOR
SELECT table_name
FROM information_schema.TABLES
WHERE table_type = 'base table'
OPEN cur_reindex
FETCH NEXT FROM cur_reindex INTO @.TableName
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'Reindexing ' + @.TableName + ' table'
DBCC DBREINDEX (@.TableName, ' ', 0)
FETCH NEXT FROM cur_reindex INTO @.TableName
END
CLOSE cur_reindex
DEALLOCATE cur_reindex
Both query #1 and #2 are prefixed by:
DBCC FREEPROCCACHE
DBCC DROPCLEANBUFFERS
Here are some timing statistics. I got these using SQL Server
Management Studio Express with client statistics enabled. The last
column is an average of the first five trials.
Time Statistics (Database #1 after rebuild of #1)
Client processing time 0 15 31 0 63 21.8
Total execution time 62 93 62 46 125 77.6
Wait time on server replies 62 78 31 46 62 55.8
Time Statistics (Database #1 after rebuild of #2)
Client processing time 15 0 0 0 16 6.2
Total execution time 296 390 421 390 359 371.2
Wait time on server replies 281 390 421 390 343 365
Time Statistics (Database #2 after rebuild of #2)
Client processing time 0 0 16 31 16 15.6667
Total execution time 78 46 62 62 78 62
Wait time on server replies 78 46 46 31 62 46.3333
Time Statistics (Database #1 after rebuild of #1)
Client processing time 16 31 0 16 0 12.6
Total execution time 78 46 62 109 62 71.4
Wait time on server replies 62 15 62 93 62 58.8
Time Statistics (Database #2 after rebuild of #1)
Client processing time 0 0 0 16 0 3.2
Total execution time 281 437 312 312 343 337
Wait time on server replies 281 437 312 296 343 333.8
What is going on here? Am I losing my mind!?
Thanks for any help!
JonathanSounds like you don't have enough RAM. When you do a bunch of index
rebuilds, it's likely those pages stayed in memory long enough for you do
query the same DB and get good results. When you go to query the other DB,
it ages out those pages from memory and has to go to disk to get the new
ones. If you have lots of RAM, this can be mitigated.
To make it an apples to apples comparison try either of the following:
Method 1
1) run DBCC DROPCLEANBUFFERS before the index rebuild and run your query
2) rebuild the index
3) repeat step 1 and compare the results
This will show you how long it takes for both a fragmented and
non-fragmented index to get the data from the disk
Method 2
1) run your query a few of times, then take stats on the last one or two
2) rebuild your index
3) repeat 1 and compare the results
This will show you the performance when the data are cached.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
<jonathanve@.gmail.com> wrote in message
news:1140653001.018380.251370@.z14g2000cwz.googlegroups.com...
Hi all,
I'm facing a very strange problem. I have two databases (in
particular) that are attached to SQL Server 2005 Express (say, #1 and
#2), and I have two queries (among others) that I use to access their
data. Now, after rebuilding all indexes in database #1, the query to
access that database seems to be very fast. Then, I rebuild the
indexes in database #2, but the query to access database #1 takes about
6 times longer. However, the query to access database #2 is now very
fast. Rebuilding database #1 speeds access to #1 at the expense of
slowing down database #2. Here are the queries I'm using:
Query #1:
SELECT [EXDT] AS [Date], [AMT] AS [Dividend], [SHR] AS &
#91;Factor]
FROM KRAM_Splits.dbo.Data
WHERE [No] = 10230
ORDER BY [EXDT] ASC
Query #2:
SELECT [No], MAX([Symbol]) AS [Symbol], MAX([Company]) AS &#
91;Company],
MAX([SICCD]) AS [SICCD], MIN([Start_Date]) AS [Start_Date],
MAX([End_Date]) AS [End_Date]
FROM CO_History.dbo.Nos
WHERE [Symbol] = 'INTC'
GROUP BY [No]
ORDER BY [End_Date] DESC
Rebuild Query:
USE [CO_History] /* Or [KRAM_Splits] */
DECLARE @.TableName sysname
DECLARE cur_reindex CURSOR FOR
SELECT table_name
FROM information_schema.TABLES
WHERE table_type = 'base table'
OPEN cur_reindex
FETCH NEXT FROM cur_reindex INTO @.TableName
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'Reindexing ' + @.TableName + ' table'
DBCC DBREINDEX (@.TableName, ' ', 0)
FETCH NEXT FROM cur_reindex INTO @.TableName
END
CLOSE cur_reindex
DEALLOCATE cur_reindex
Both query #1 and #2 are prefixed by:
DBCC FREEPROCCACHE
DBCC DROPCLEANBUFFERS
Here are some timing statistics. I got these using SQL Server
Management Studio Express with client statistics enabled. The last
column is an average of the first five trials.
Time Statistics (Database #1 after rebuild of #1)
Client processing time 0 15 31 0 63 21.8
Total execution time 62 93 62 46 125 77.6
Wait time on server replies 62 78 31 46 62 55.8
Time Statistics (Database #1 after rebuild of #2)
Client processing time 15 0 0 0 16 6.2
Total execution time 296 390 421 390 359 371.2
Wait time on server replies 281 390 421 390 343 365
Time Statistics (Database #2 after rebuild of #2)
Client processing time 0 0 16 31 16 15.6667
Total execution time 78 46 62 62 78 62
Wait time on server replies 78 46 46 31 62 46.3333
Time Statistics (Database #1 after rebuild of #1)
Client processing time 16 31 0 16 0 12.6
Total execution time 78 46 62 109 62 71.4
Wait time on server replies 62 15 62 93 62 58.8
Time Statistics (Database #2 after rebuild of #1)
Client processing time 0 0 0 16 0 3.2
Total execution time 281 437 312 312 343 337
Wait time on server replies 281 437 312 296 343 333.8
What is going on here? Am I losing my mind!?
Thanks for any help!
Jonathan|||OK, I see what you mean. This computer has 512MB which is on the low
side.
But I'm unclear about one thing: After reindexing, the query seems to
take almost no time at all (~0 msec), which means that a good part is
in memory. But even without reindexing (like when I run the query on
database #2 after indexing database #1), wouldn't running the query a
few times put a lot of the pages from the query in memory so that it
would also take almost no time after that? It seems like even after
running the query a bunch of times, it still takes about 200 msec or
so, which is better than the first run (so it is caching something),
but not as fast as after a reindex. What's the reason behind this?
Also, is SQL Server 2005 a bit more memory hungry than MSDE (which is
what I used before)?
Thanks for the quick response!
Jonathan

Really urgent - Data field retrieve and store

Basically i make use of FormView in Web Developer Express Edition to create and store information to the database ...

what i want to do further is to capture the value within the primary key of the newly created recordset that I set it become auto increament ....

this value would be stored within a session string in global condition that allowed any page able to access it ....

If you simply want to return the ID to use within the application, and you are using a stored procedure, do this.

Insert the record as normal in the table, then add a statement such as SELECT SCOPE_IDENETITY() as TheNewId

If your insert fails, this line never executes. If insert is OK, you get teh new ID passed back

In your code, perform an execute scaler method call on the connection, and cast the return (decimal as object) into an integer, and store in session. If the returned value is null, the insert failed

What I often create for projects is a global "Execute Scaler" method that accepts the name of a stored procedure, and a string dictionary of name/value pairs.

IN the method, create the SQL Command object, call the SQLCommandBuilder static method to get the parameters, then iterate through the dictionary to add these by name.

Call the command ExecuteScaler as mentioned and proceed as above

|||Really appreciate ur feedback men... but it looks so technical for me men... i am totally a new beginner but have to complete this project within another week time...

can u demonstrate the code (sorry for the hassle)... i kind of not sure how to achieve what u had mentioned...|||

Example SP

CREATE PROCEDURE

dbo.MyTable_Insert

(

@.Parameter1varchar(100)

)

AS

SET NOCOUNT ON

INSERT INTOMyTable (MyData)VALUES(@.Parameter1)

SELECT SCOPE_IDENTITY()asTheNewId

Example Code

int InsertRecord(string insertValue)

{

// assumes you have set cnn as a suitable connection

SqlCommand cmd =newSqlCommand("MyTable_Insert", cnn);

cmd.CommandType = System.Data.CommandType.StoredProcedure;

cmd.Parameters["@.Parameter1"].Value = insertValue;

object retObject = cmd.ExecuteScalar();

if (retObject !=null)

return (int)retObject;

else

return 0;// no new record

}

Real problem installing SQL Server express 2005

When I first installed MS SQL Server 2005 Express Editon, I didn't I selected Windows Auth instead of mixed mode, so I uninstalled sql server and then attempted to reinstall. On the earlier installtion I did setup to instances which show in the "Control Panel/admin tool/services". Anyway, I used the unistall through the control panel, but on installing again it told me that I had instances aready running and needed to stop them. Couldn't work out how to do that. So after many different things, including using the MS's removal tool and windows installer clean up, I still failed. Now however I get the following error message:

Setup failed because Service MSSQL$SQLExpress is disabled for the current hardware profile. Services must be set with the current Hardware Profile logon property profile enabled. For more information on how to enable the hardware profile logon property refer to the product documentation.

Can someone help?

Cheers

Dave

Hello,

Did you get an answer to your questio?

I am having the same problem and I do not know how to solve it?!

So if you solved it can you please share the solution with me.

Thanks,

Eitan

|||

No, had no answers. Really *** forum, obviously noone can help and too difficult. If you get somewhere I'd really appreciate the info. Thanks

Dave

|||

It sounds like the uninstall was unsucessful leaving something behind on the machine. You might want to try the following article to clean up the machine first and then reinstall.

http://support.microsoft.com/kb/909967

Michelle

Ready for Production?

I must release a new Db on 4/1 into an isolated small network (pier workgroup) and my choices are MSDE or Express. I'm new to both (MSDE yesterday, Express today). I am familiar with SQL Server and prefer using the tools with Express, but is it stable enough to use in this type of production environment?

I hope so. I also am going live with SQL Express 05 around April or May and it will be ran on 1-15 computer systems at a time.

Also, just to make it fun... we are still running a VB6 front end so we are using ADO 2.8.

I think it is ready. One way to find out. I'll post here if i come across something crazy.

|||

Yep, I think it's stable enough, we went live a month ago with a shrink-wrapped product using SQL Express as the backend.

|||

Thanks for the comments Matt & Scott.

SQL Express released in November 2005 and I have not heard anything to suggest that it isn't stable enought to use as you've all suggested. There is a new member of the "family" called SQL Express with Advanced Services that has just been released to CTP. That is pre-release software so it should not be used in production environments at this time.

Regards,

Mike Wachal - SQL Express team