reboot reboot reboot

I have installed ss2005 and now I want to change some things (add the
AdventureWorks dbs). On one machine it worked fine but on the other System
Configuration Check keeps getting a reboot required message that says...
"A previous installation required a reboot of the machine for changes to
take effect. To proceed, restart your computer and then run SQL Server
Setup again."
So, I reboot but it keeps getting the same message. What can I do?
Tinn ManI presume that there is an installation issue.
and at every reboot, Sql server starts and detect a file problem, like a
missing or worng DLL, then the installer starts a repair process.
when the reinstallation is done, the system ask for a reboot.
but this reinstallation doesn't works really fine and at every reboot the
same event occurs.
you'll see some installer event log in the windows log if the installer
starts himself.
Try to reinstall SQL server interactively to catch some installation issues.
stop any SQL services , reboot, see if the installer starts, then do a clean
install or repair process.
"Tinn Man" <tm@.nospammeexcite.com> wrote in message
news:uw8ZVLQiGHA.4512@.TK2MSFTNGP02.phx.gbl...
>I have installed ss2005 and now I want to change some things (add the
>AdventureWorks dbs). On one machine it worked fine but on the other System
>Configuration Check keeps getting a reboot required message that says...
> "A previous installation required a reboot of the machine for changes to
> take effect. To proceed, restart your computer and then run SQL Server
> Setup again."
> So, I reboot but it keeps getting the same message. What can I do?
> Tinn Man
>

reboot reboot reboot

I have installed ss2005 and now I want to change some things (add the
AdventureWorks dbs). On one machine it worked fine but on the other System
Configuration Check keeps getting a reboot required message that says...
"A previous installation required a reboot of the machine for changes to
take effect. To proceed, restart your computer and then run SQL Server
Setup again."
So, I reboot but it keeps getting the same message. What can I do?
Tinn ManI presume that there is an installation issue.
and at every reboot, Sql server starts and detect a file problem, like a
missing or worng DLL, then the installer starts a repair process.
when the reinstallation is done, the system ask for a reboot.
but this reinstallation doesn't works really fine and at every reboot the
same event occurs.
you'll see some installer event log in the windows log if the installer
starts himself.
Try to reinstall SQL server interactively to catch some installation issues.
stop any SQL services , reboot, see if the installer starts, then do a clean
install or repair process.
"Tinn Man" <tm@.nospammeexcite.com> wrote in message
news:uw8ZVLQiGHA.4512@.TK2MSFTNGP02.phx.gbl...
>I have installed ss2005 and now I want to change some things (add the
>AdventureWorks dbs). On one machine it worked fine but on the other System
>Configuration Check keeps getting a reboot required message that says...
> "A previous installation required a reboot of the machine for changes to
> take effect. To proceed, restart your computer and then run SQL Server
> Setup again."
> So, I reboot but it keeps getting the same message. What can I do?
> Tinn Man
>

real time reporting + OLTP dbs

How does one implement real time reporting off of data from the OLTP
systems. Right now we run nightly extracts and load into OLAP DBs to
minimise locking,etc while the extracts are being run. However our customers
now want to see real time data as soon as possible and we cannot give them
access to the live OLTP systems. Are there any ways to implement this
efficiently ?Have you tried replication? It should give you more frequent updates.
You might want to consider using read uncommitted query because replication
also needs to make changes to your OLAP database to keep data up to date.
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:upTfU1d0EHA.3584@.TK2MSFTNGP11.phx.gbl...
> How does one implement real time reporting off of data from the OLTP
> systems. Right now we run nightly extracts and load into OLAP DBs to
> minimise locking,etc while the extracts are being run. However our
> customers
> now want to see real time data as soon as possible and we cannot give them
> access to the live OLTP systems. Are there any ways to implement this
> efficiently ?
>|||we thought about replication but cant really justify replicating each of our
OLTP dbs to serve the reporting needs besides the administration needed to
support it ,etc..
"wei xiao [MSFT]" <weix@.online.microsoft.com> wrote in message
news:Oc0vFSf0EHA.2568@.TK2MSFTNGP11.phx.gbl...
> Have you tried replication? It should give you more frequent updates.
> You might want to consider using read uncommitted query because
replication
> also needs to make changes to your OLAP database to keep data up to date.
> --
> Wei Xiao [MSFT]
> SQL Server Storage Engine Development
> http://weblogs.asp.net/weix
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:upTfU1d0EHA.3584@.TK2MSFTNGP11.phx.gbl...
> > How does one implement real time reporting off of data from the OLTP
> > systems. Right now we run nightly extracts and load into OLAP DBs to
> > minimise locking,etc while the extracts are being run. However our
> > customers
> > now want to see real time data as soon as possible and we cannot give
them
> > access to the live OLTP systems. Are there any ways to implement this
> > efficiently ?
> >
> >
>

real time reporting + OLTP dbs

How does one implement real time reporting off of data from the OLTP
systems. Right now we run nightly extracts and load into OLAP DBs to
minimise locking,etc while the extracts are being run. However our customers
now want to see real time data as soon as possible and we cannot give them
access to the live OLTP systems. Are there any ways to implement this
efficiently ?
Have you tried replication? It should give you more frequent updates.
You might want to consider using read uncommitted query because replication
also needs to make changes to your OLAP database to keep data up to date.
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:upTfU1d0EHA.3584@.TK2MSFTNGP11.phx.gbl...
> How does one implement real time reporting off of data from the OLTP
> systems. Right now we run nightly extracts and load into OLAP DBs to
> minimise locking,etc while the extracts are being run. However our
> customers
> now want to see real time data as soon as possible and we cannot give them
> access to the live OLTP systems. Are there any ways to implement this
> efficiently ?
>
|||we thought about replication but cant really justify replicating each of our
OLTP dbs to serve the reporting needs besides the administration needed to
support it ,etc..
"wei xiao [MSFT]" <weix@.online.microsoft.com> wrote in message
news:Oc0vFSf0EHA.2568@.TK2MSFTNGP11.phx.gbl...
> Have you tried replication? It should give you more frequent updates.
> You might want to consider using read uncommitted query because
replication
> also needs to make changes to your OLAP database to keep data up to date.
> --
> Wei Xiao [MSFT]
> SQL Server Storage Engine Development
> http://weblogs.asp.net/weix
> This posting is provided "AS IS" with no warranties, and confers no
rights.[vbcol=seagreen]
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:upTfU1d0EHA.3584@.TK2MSFTNGP11.phx.gbl...
them
>

real time reporting + OLTP dbs

How does one implement real time reporting off of data from the OLTP
systems. Right now we run nightly extracts and load into OLAP DBs to
minimise locking,etc while the extracts are being run. However our customers
now want to see real time data as soon as possible and we cannot give them
access to the live OLTP systems. Are there any ways to implement this
efficiently ?Have you tried replication? It should give you more frequent updates.
You might want to consider using read uncommitted query because replication
also needs to make changes to your OLAP database to keep data up to date.
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:upTfU1d0EHA.3584@.TK2MSFTNGP11.phx.gbl...
> How does one implement real time reporting off of data from the OLTP
> systems. Right now we run nightly extracts and load into OLAP DBs to
> minimise locking,etc while the extracts are being run. However our
> customers
> now want to see real time data as soon as possible and we cannot give them
> access to the live OLTP systems. Are there any ways to implement this
> efficiently ?
>|||we thought about replication but cant really justify replicating each of our
OLTP dbs to serve the reporting needs besides the administration needed to
support it ,etc..
"wei xiao [MSFT]" <weix@.online.microsoft.com> wrote in message
news:Oc0vFSf0EHA.2568@.TK2MSFTNGP11.phx.gbl...
> Have you tried replication? It should give you more frequent updates.
> You might want to consider using read uncommitted query because
replication
> also needs to make changes to your OLAP database to keep data up to date.
> --
> Wei Xiao [MSFT]
> SQL Server Storage Engine Development
> http://weblogs.asp.net/weix
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:upTfU1d0EHA.3584@.TK2MSFTNGP11.phx.gbl...
them[vbcol=seagreen]
>