The SBS 2003 server is blue screening. The client has not done any backup in
several months. I have pluged in another HDD, installed Standard 2003 and
then reconnected the old HDD as a second drive. All the data from the old HDD
is now visible and accessible. I can now comfortably recover all their data
except SQL database. Is there any way? Please help. Thanks in advance.
Chris
You might be able to attach the database files to the new installation. Read about sp_attach_db.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
> The SBS 2003 server is blue screening. The client has not done any backup in
> several months. I have pluged in another HDD, installed Standard 2003 and
> then reconnected the old HDD as a second drive. All the data from the old HDD
> is now visible and accessible. I can now comfortably recover all their data
> except SQL database. Is there any way? Please help. Thanks in advance.
> Chris
|||Tibor Im curious about your response. You say he "might" be able to attach,
what circumstances make this possible?
"Tibor Karaszi" wrote:
> You might be able to attach the database files to the new installation. Read about sp_attach_db.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
>
|||As long as there was no physical damage to the data or log files it should
work. When it attaches it will go thru recovery and roll forward or back as
needed to make the db consistent.
Andrew J. Kelly SQL MVP
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...[vbcol=seagreen]
> Tibor Im curious about your response. You say he "might" be able to
> attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
|||> Tibor Im curious about your response. You say he "might" be able to attach,
> what circumstances make this possible?
Below is a quote from Books Online (2000) , sp_attach_db
"sp_attach_db should only be executed on databases that were previously detached from the database
server using an explicit sp_detach_db operation. "
We see posts almost here daily about "... crash ... attach... doesn't work". Granted, many of these
deleted the log file as well, but still. I like to play safe. Yes, I'd appreciate if MS would
provide a technical elaboration about specifically when attach work and when it doesn't. But without
such, I feel that BOL is the one to trust. Especially based on the posts we see here. Even if attach
(without detach) work in 99.99 % of the cases, it isn't good enough for me. Without knowing why it
won't work, I can't trust it. :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...[vbcol=seagreen]
> Tibor Im curious about your response. You say he "might" be able to attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
Showing posts with label sbs. Show all posts
Showing posts with label sbs. Show all posts
Friday, February 24, 2012
database recovery
The SBS 2003 server is blue screening. The client has not done any backup in
several months. I have pluged in another HDD, installed Standard 2003 and
then reconnected the old HDD as a second drive. All the data from the old HD
D
is now visible and accessible. I can now comfortably recover all their data
except SQL database. Is there any way? Please help. Thanks in advance.
ChrisYou might be able to attach the database files to the new installation. Read
about sp_attach_db.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
> The SBS 2003 server is blue screening. The client has not done any backup
in
> several months. I have pluged in another HDD, installed Standard 2003 and
> then reconnected the old HDD as a second drive. All the data from the old
HDD
> is now visible and accessible. I can now comfortably recover all their dat
a
> except SQL database. Is there any way? Please help. Thanks in advance.
> Chris|||Tibor Im curious about your response. You say he "might" be able to attach,
what circumstances make this possible?
"Tibor Karaszi" wrote:
> You might be able to attach the database files to the new installation. Re
ad about sp_attach_db.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
>|||As long as there was no physical damage to the data or log files it should
work. When it attaches it will go thru recovery and roll forward or back as
needed to make the db consistent.
Andrew J. Kelly SQL MVP
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...[vbcol=seagreen]
> Tibor Im curious about your response. You say he "might" be able to
> attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>|||> Tibor Im curious about your response. You say he "might" be able to attach,">
> what circumstances make this possible?
Below is a quote from Books Online (2000) , sp_attach_db
"sp_attach_db should only be executed on databases that were previously deta
ched from the database
server using an explicit sp_detach_db operation. "
We see posts almost here daily about "... crash ... attach... doesn't work".
Granted, many of these
deleted the log file as well, but still. I like to play safe. Yes, I'd appre
ciate if MS would
provide a technical elaboration about specifically when attach work and when
it doesn't. But without
such, I feel that BOL is the one to trust. Especially based on the posts we
see here. Even if attach
(without detach) work in 99.99 % of the cases, it isn't good enough for me.
Without knowing why it
won't work, I can't trust it. :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...[vbcol=seagreen]
> Tibor Im curious about your response. You say he "might" be able to attach
,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>
several months. I have pluged in another HDD, installed Standard 2003 and
then reconnected the old HDD as a second drive. All the data from the old HD
D
is now visible and accessible. I can now comfortably recover all their data
except SQL database. Is there any way? Please help. Thanks in advance.
ChrisYou might be able to attach the database files to the new installation. Read
about sp_attach_db.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
> The SBS 2003 server is blue screening. The client has not done any backup
in
> several months. I have pluged in another HDD, installed Standard 2003 and
> then reconnected the old HDD as a second drive. All the data from the old
HDD
> is now visible and accessible. I can now comfortably recover all their dat
a
> except SQL database. Is there any way? Please help. Thanks in advance.
> Chris|||Tibor Im curious about your response. You say he "might" be able to attach,
what circumstances make this possible?
"Tibor Karaszi" wrote:
> You might be able to attach the database files to the new installation. Re
ad about sp_attach_db.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
>|||As long as there was no physical damage to the data or log files it should
work. When it attaches it will go thru recovery and roll forward or back as
needed to make the db consistent.
Andrew J. Kelly SQL MVP
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...[vbcol=seagreen]
> Tibor Im curious about your response. You say he "might" be able to
> attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>|||> Tibor Im curious about your response. You say he "might" be able to attach,">
> what circumstances make this possible?
Below is a quote from Books Online (2000) , sp_attach_db
"sp_attach_db should only be executed on databases that were previously deta
ched from the database
server using an explicit sp_detach_db operation. "
We see posts almost here daily about "... crash ... attach... doesn't work".
Granted, many of these
deleted the log file as well, but still. I like to play safe. Yes, I'd appre
ciate if MS would
provide a technical elaboration about specifically when attach work and when
it doesn't. But without
such, I feel that BOL is the one to trust. Especially based on the posts we
see here. Even if attach
(without detach) work in 99.99 % of the cases, it isn't good enough for me.
Without knowing why it
won't work, I can't trust it. :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...[vbcol=seagreen]
> Tibor Im curious about your response. You say he "might" be able to attach
,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>
database recovery
The SBS 2003 server is blue screening. The client has not done any backup in
several months. I have pluged in another HDD, installed Standard 2003 and
then reconnected the old HDD as a second drive. All the data from the old HDD
is now visible and accessible. I can now comfortably recover all their data
except SQL database. Is there any way? Please help. Thanks in advance.
ChrisYou might be able to attach the database files to the new installation. Read about sp_attach_db.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
> The SBS 2003 server is blue screening. The client has not done any backup in
> several months. I have pluged in another HDD, installed Standard 2003 and
> then reconnected the old HDD as a second drive. All the data from the old HDD
> is now visible and accessible. I can now comfortably recover all their data
> except SQL database. Is there any way? Please help. Thanks in advance.
> Chris|||Tibor Im curious about your response. You say he "might" be able to attach,
what circumstances make this possible?
"Tibor Karaszi" wrote:
> You might be able to attach the database files to the new installation. Read about sp_attach_db.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
> > The SBS 2003 server is blue screening. The client has not done any backup in
> > several months. I have pluged in another HDD, installed Standard 2003 and
> > then reconnected the old HDD as a second drive. All the data from the old HDD
> > is now visible and accessible. I can now comfortably recover all their data
> > except SQL database. Is there any way? Please help. Thanks in advance.
> >
> > Chris
>|||As long as there was no physical damage to the data or log files it should
work. When it attaches it will go thru recovery and roll forward or back as
needed to make the db consistent.
--
Andrew J. Kelly SQL MVP
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...
> Tibor Im curious about your response. You say he "might" be able to
> attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>> You might be able to attach the database files to the new installation.
>> Read about sp_attach_db.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
>> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
>> > The SBS 2003 server is blue screening. The client has not done any
>> > backup in
>> > several months. I have pluged in another HDD, installed Standard 2003
>> > and
>> > then reconnected the old HDD as a second drive. All the data from the
>> > old HDD
>> > is now visible and accessible. I can now comfortably recover all their
>> > data
>> > except SQL database. Is there any way? Please help. Thanks in advance.
>> >
>> > Chris
>>|||> Tibor Im curious about your response. You say he "might" be able to attach,
> what circumstances make this possible?
Below is a quote from Books Online (2000) , sp_attach_db
"sp_attach_db should only be executed on databases that were previously detached from the database
server using an explicit sp_detach_db operation. "
We see posts almost here daily about "... crash ... attach... doesn't work". Granted, many of these
deleted the log file as well, but still. I like to play safe. Yes, I'd appreciate if MS would
provide a technical elaboration about specifically when attach work and when it doesn't. But without
such, I feel that BOL is the one to trust. Especially based on the posts we see here. Even if attach
(without detach) work in 99.99 % of the cases, it isn't good enough for me. Without knowing why it
won't work, I can't trust it. :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...
> Tibor Im curious about your response. You say he "might" be able to attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>> You might be able to attach the database files to the new installation. Read about sp_attach_db.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
>> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
>> > The SBS 2003 server is blue screening. The client has not done any backup in
>> > several months. I have pluged in another HDD, installed Standard 2003 and
>> > then reconnected the old HDD as a second drive. All the data from the old HDD
>> > is now visible and accessible. I can now comfortably recover all their data
>> > except SQL database. Is there any way? Please help. Thanks in advance.
>> >
>> > Chris
>>
several months. I have pluged in another HDD, installed Standard 2003 and
then reconnected the old HDD as a second drive. All the data from the old HDD
is now visible and accessible. I can now comfortably recover all their data
except SQL database. Is there any way? Please help. Thanks in advance.
ChrisYou might be able to attach the database files to the new installation. Read about sp_attach_db.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
> The SBS 2003 server is blue screening. The client has not done any backup in
> several months. I have pluged in another HDD, installed Standard 2003 and
> then reconnected the old HDD as a second drive. All the data from the old HDD
> is now visible and accessible. I can now comfortably recover all their data
> except SQL database. Is there any way? Please help. Thanks in advance.
> Chris|||Tibor Im curious about your response. You say he "might" be able to attach,
what circumstances make this possible?
"Tibor Karaszi" wrote:
> You might be able to attach the database files to the new installation. Read about sp_attach_db.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
> > The SBS 2003 server is blue screening. The client has not done any backup in
> > several months. I have pluged in another HDD, installed Standard 2003 and
> > then reconnected the old HDD as a second drive. All the data from the old HDD
> > is now visible and accessible. I can now comfortably recover all their data
> > except SQL database. Is there any way? Please help. Thanks in advance.
> >
> > Chris
>|||As long as there was no physical damage to the data or log files it should
work. When it attaches it will go thru recovery and roll forward or back as
needed to make the db consistent.
--
Andrew J. Kelly SQL MVP
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...
> Tibor Im curious about your response. You say he "might" be able to
> attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>> You might be able to attach the database files to the new installation.
>> Read about sp_attach_db.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
>> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
>> > The SBS 2003 server is blue screening. The client has not done any
>> > backup in
>> > several months. I have pluged in another HDD, installed Standard 2003
>> > and
>> > then reconnected the old HDD as a second drive. All the data from the
>> > old HDD
>> > is now visible and accessible. I can now comfortably recover all their
>> > data
>> > except SQL database. Is there any way? Please help. Thanks in advance.
>> >
>> > Chris
>>|||> Tibor Im curious about your response. You say he "might" be able to attach,
> what circumstances make this possible?
Below is a quote from Books Online (2000) , sp_attach_db
"sp_attach_db should only be executed on databases that were previously detached from the database
server using an explicit sp_detach_db operation. "
We see posts almost here daily about "... crash ... attach... doesn't work". Granted, many of these
deleted the log file as well, but still. I like to play safe. Yes, I'd appreciate if MS would
provide a technical elaboration about specifically when attach work and when it doesn't. But without
such, I feel that BOL is the one to trust. Especially based on the posts we see here. Even if attach
(without detach) work in 99.99 % of the cases, it isn't good enough for me. Without knowing why it
won't work, I can't trust it. :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...
> Tibor Im curious about your response. You say he "might" be able to attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>> You might be able to attach the database files to the new installation. Read about sp_attach_db.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
>> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
>> > The SBS 2003 server is blue screening. The client has not done any backup in
>> > several months. I have pluged in another HDD, installed Standard 2003 and
>> > then reconnected the old HDD as a second drive. All the data from the old HDD
>> > is now visible and accessible. I can now comfortably recover all their data
>> > except SQL database. Is there any way? Please help. Thanks in advance.
>> >
>> > Chris
>>
Sunday, February 19, 2012
Database problems
I have an SBS 2003 Premium server. There is an SQL and a Universe database
on this server. Every morning the database services seem to hang. When I try
and manually restart them, I get the following error message.
An error 1053 (The service did not respond to the start or control request
in a timely fashion.) occurred while performing this service operation on
the SQLServerAgent service.
Also the Universe Resource Service - same error.
If I reboot the server, everything is fine.
How can I resolve this problem?Hi,
Check the Memory usage during this situation. If the memory is fully
occupaid then ,Can you make the memory parameter static for SQL Server. I
feel that this is due to resource contension.
Thanks
Hari
MCDBA
"Peter Downes" <pjtdownes@.hotmail.com> wrote in message
news:c6la2k$1lue$1@.newsreader02.ops.uunet.co.za...
> I have an SBS 2003 Premium server. There is an SQL and a Universe database
> on this server. Every morning the database services seem to hang. When I
try
> and manually restart them, I get the following error message.
> An error 1053 (The service did not respond to the start or control request
> in a timely fashion.) occurred while performing this service operation on
> the SQLServerAgent service.
> Also the Universe Resource Service - same error.
> If I reboot the server, everything is fine.
> How can I resolve this problem?
>|||I am not sure exactly when it falls over. It is sometime in the night. There
do not seem to be any errors that correspond in the event log.
We are running backups and virus scans in the evening. With backups disabled
problem still occurs.
I have 1.5G RAM in this machine. I can capture memory usage to a log file
through Performance Monitor tonight. How would I make the memory parameter
for the SQL static?
Is it possible that the Universe and SQL are affected by the same problem?
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:OwSaA6DLEHA.1416@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Check the Memory usage during this situation. If the memory is fully
> occupaid then ,Can you make the memory parameter static for SQL Server. I
> feel that this is due to resource contension.
> Thanks
> Hari
> MCDBA
>
> "Peter Downes" <pjtdownes@.hotmail.com> wrote in message
> news:c6la2k$1lue$1@.newsreader02.ops.uunet.co.za...
> > I have an SBS 2003 Premium server. There is an SQL and a Universe
database
> > on this server. Every morning the database services seem to hang. When I
> try
> > and manually restart them, I get the following error message.
> >
> > An error 1053 (The service did not respond to the start or control
request
> > in a timely fashion.) occurred while performing this service operation
on
> > the SQLServerAgent service.
> >
> > Also the Universe Resource Service - same error.
> >
> > If I reboot the server, everything is fine.
> >
> > How can I resolve this problem?
> >
> >
>|||Couple of Ideas...
1. Run a performance logger on the server to see what
resources are low.
2. Put a trace on SQL Server to see when it stops
3. Check the server logs and see if they have errors
4. If you can manage it get some down time on your server
then execute each job separately till you find the one
that causes the error.
To configure the memory
1. Go to EA
2. Right click on your server
3. Select 'properties'
4. Select memory
5. The rest you can guess ;)
Personally I think Hari is correct, it is memory
J
>--Original Message--
>I am not sure exactly when it falls over. It is sometime
in the night. There
>do not seem to be any errors that correspond in the event
log.
>We are running backups and virus scans in the evening.
With backups disabled
>problem still occurs.
>I have 1.5G RAM in this machine. I can capture memory
usage to a log file
>through Performance Monitor tonight. How would I make the
memory parameter
>for the SQL static?
>Is it possible that the Universe and SQL are affected by
the same problem?
>
>"Hari" <hari_prasad_k@.hotmail.com> wrote in message
>news:OwSaA6DLEHA.1416@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> Check the Memory usage during this situation. If the
memory is fully
>> occupaid then ,Can you make the memory parameter static
for SQL Server. I
>> feel that this is due to resource contension.
>> Thanks
>> Hari
>> MCDBA
>>
>> "Peter Downes" <pjtdownes@.hotmail.com> wrote in message
>> news:c6la2k$1lue$1@.newsreader02.ops.uunet.co.za...
>> > I have an SBS 2003 Premium server. There is an SQL
and a Universe
>database
>> > on this server. Every morning the database services
seem to hang. When I
>> try
>> > and manually restart them, I get the following error
message.
>> >
>> > An error 1053 (The service did not respond to the
start or control
>request
>> > in a timely fashion.) occurred while performing this
service operation
>on
>> > the SQLServerAgent service.
>> >
>> > Also the Universe Resource Service - same error.
>> >
>> > If I reboot the server, everything is fine.
>> >
>> > How can I resolve this problem?
>> >
>> >
>>
>
>.
>
on this server. Every morning the database services seem to hang. When I try
and manually restart them, I get the following error message.
An error 1053 (The service did not respond to the start or control request
in a timely fashion.) occurred while performing this service operation on
the SQLServerAgent service.
Also the Universe Resource Service - same error.
If I reboot the server, everything is fine.
How can I resolve this problem?Hi,
Check the Memory usage during this situation. If the memory is fully
occupaid then ,Can you make the memory parameter static for SQL Server. I
feel that this is due to resource contension.
Thanks
Hari
MCDBA
"Peter Downes" <pjtdownes@.hotmail.com> wrote in message
news:c6la2k$1lue$1@.newsreader02.ops.uunet.co.za...
> I have an SBS 2003 Premium server. There is an SQL and a Universe database
> on this server. Every morning the database services seem to hang. When I
try
> and manually restart them, I get the following error message.
> An error 1053 (The service did not respond to the start or control request
> in a timely fashion.) occurred while performing this service operation on
> the SQLServerAgent service.
> Also the Universe Resource Service - same error.
> If I reboot the server, everything is fine.
> How can I resolve this problem?
>|||I am not sure exactly when it falls over. It is sometime in the night. There
do not seem to be any errors that correspond in the event log.
We are running backups and virus scans in the evening. With backups disabled
problem still occurs.
I have 1.5G RAM in this machine. I can capture memory usage to a log file
through Performance Monitor tonight. How would I make the memory parameter
for the SQL static?
Is it possible that the Universe and SQL are affected by the same problem?
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:OwSaA6DLEHA.1416@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Check the Memory usage during this situation. If the memory is fully
> occupaid then ,Can you make the memory parameter static for SQL Server. I
> feel that this is due to resource contension.
> Thanks
> Hari
> MCDBA
>
> "Peter Downes" <pjtdownes@.hotmail.com> wrote in message
> news:c6la2k$1lue$1@.newsreader02.ops.uunet.co.za...
> > I have an SBS 2003 Premium server. There is an SQL and a Universe
database
> > on this server. Every morning the database services seem to hang. When I
> try
> > and manually restart them, I get the following error message.
> >
> > An error 1053 (The service did not respond to the start or control
request
> > in a timely fashion.) occurred while performing this service operation
on
> > the SQLServerAgent service.
> >
> > Also the Universe Resource Service - same error.
> >
> > If I reboot the server, everything is fine.
> >
> > How can I resolve this problem?
> >
> >
>|||Couple of Ideas...
1. Run a performance logger on the server to see what
resources are low.
2. Put a trace on SQL Server to see when it stops
3. Check the server logs and see if they have errors
4. If you can manage it get some down time on your server
then execute each job separately till you find the one
that causes the error.
To configure the memory
1. Go to EA
2. Right click on your server
3. Select 'properties'
4. Select memory
5. The rest you can guess ;)
Personally I think Hari is correct, it is memory
J
>--Original Message--
>I am not sure exactly when it falls over. It is sometime
in the night. There
>do not seem to be any errors that correspond in the event
log.
>We are running backups and virus scans in the evening.
With backups disabled
>problem still occurs.
>I have 1.5G RAM in this machine. I can capture memory
usage to a log file
>through Performance Monitor tonight. How would I make the
memory parameter
>for the SQL static?
>Is it possible that the Universe and SQL are affected by
the same problem?
>
>"Hari" <hari_prasad_k@.hotmail.com> wrote in message
>news:OwSaA6DLEHA.1416@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> Check the Memory usage during this situation. If the
memory is fully
>> occupaid then ,Can you make the memory parameter static
for SQL Server. I
>> feel that this is due to resource contension.
>> Thanks
>> Hari
>> MCDBA
>>
>> "Peter Downes" <pjtdownes@.hotmail.com> wrote in message
>> news:c6la2k$1lue$1@.newsreader02.ops.uunet.co.za...
>> > I have an SBS 2003 Premium server. There is an SQL
and a Universe
>database
>> > on this server. Every morning the database services
seem to hang. When I
>> try
>> > and manually restart them, I get the following error
message.
>> >
>> > An error 1053 (The service did not respond to the
start or control
>request
>> > in a timely fashion.) occurred while performing this
service operation
>on
>> > the SQLServerAgent service.
>> >
>> > Also the Universe Resource Service - same error.
>> >
>> > If I reboot the server, everything is fine.
>> >
>> > How can I resolve this problem?
>> >
>> >
>>
>
>.
>
Database problems
I have an SBS 2003 Premium server. There is an SQL and a Universe database
on this server. Every morning the database services seem to hang. When I try
and manually restart them, I get the following error message.
An error 1053 (The service did not respond to the start or control request
in a timely fashion.) occurred while performing this service operation on
the SQLServerAgent service.
Also the Universe Resource Service - same error.
If I reboot the server, everything is fine.
How can I resolve this problem?
Hi,
Check the Memory usage during this situation. If the memory is fully
occupaid then ,Can you make the memory parameter static for SQL Server. I
feel that this is due to resource contension.
Thanks
Hari
MCDBA
"Peter Downes" <pjtdownes@.hotmail.com> wrote in message
news:c6la2k$1lue$1@.newsreader02.ops.uunet.co.za...
> I have an SBS 2003 Premium server. There is an SQL and a Universe database
> on this server. Every morning the database services seem to hang. When I
try
> and manually restart them, I get the following error message.
> An error 1053 (The service did not respond to the start or control request
> in a timely fashion.) occurred while performing this service operation on
> the SQLServerAgent service.
> Also the Universe Resource Service - same error.
> If I reboot the server, everything is fine.
> How can I resolve this problem?
>
|||I am not sure exactly when it falls over. It is sometime in the night. There
do not seem to be any errors that correspond in the event log.
We are running backups and virus scans in the evening. With backups disabled
problem still occurs.
I have 1.5G RAM in this machine. I can capture memory usage to a log file
through Performance Monitor tonight. How would I make the memory parameter
for the SQL static?
Is it possible that the Universe and SQL are affected by the same problem?
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:OwSaA6DLEHA.1416@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Hi,
> Check the Memory usage during this situation. If the memory is fully
> occupaid then ,Can you make the memory parameter static for SQL Server. I
> feel that this is due to resource contension.
> Thanks
> Hari
> MCDBA
>
> "Peter Downes" <pjtdownes@.hotmail.com> wrote in message
> news:c6la2k$1lue$1@.newsreader02.ops.uunet.co.za...
database[vbcol=seagreen]
> try
request[vbcol=seagreen]
on
>
|||Couple of Ideas...
1. Run a performance logger on the server to see what
resources are low.
2. Put a trace on SQL Server to see when it stops
3. Check the server logs and see if they have errors
4. If you can manage it get some down time on your server
then execute each job separately till you find the one
that causes the error.
To configure the memory
1. Go to EA
2. Right click on your server
3. Select 'properties'
4. Select memory
5. The rest you can guess ;)
Personally I think Hari is correct, it is memory
J
>--Original Message--
>I am not sure exactly when it falls over. It is sometime
in the night. There
>do not seem to be any errors that correspond in the event
log.
>We are running backups and virus scans in the evening.
With backups disabled
>problem still occurs.
>I have 1.5G RAM in this machine. I can capture memory
usage to a log file
>through Performance Monitor tonight. How would I make the
memory parameter
>for the SQL static?
>Is it possible that the Universe and SQL are affected by
the same problem?[vbcol=seagreen]
>
>"Hari" <hari_prasad_k@.hotmail.com> wrote in message
>news:OwSaA6DLEHA.1416@.TK2MSFTNGP09.phx.gbl...
memory is fully[vbcol=seagreen]
for SQL Server. I[vbcol=seagreen]
and a Universe[vbcol=seagreen]
>database
seem to hang. When I[vbcol=seagreen]
message.[vbcol=seagreen]
start or control[vbcol=seagreen]
>request
service operation
>on
>
>.
>
on this server. Every morning the database services seem to hang. When I try
and manually restart them, I get the following error message.
An error 1053 (The service did not respond to the start or control request
in a timely fashion.) occurred while performing this service operation on
the SQLServerAgent service.
Also the Universe Resource Service - same error.
If I reboot the server, everything is fine.
How can I resolve this problem?
Hi,
Check the Memory usage during this situation. If the memory is fully
occupaid then ,Can you make the memory parameter static for SQL Server. I
feel that this is due to resource contension.
Thanks
Hari
MCDBA
"Peter Downes" <pjtdownes@.hotmail.com> wrote in message
news:c6la2k$1lue$1@.newsreader02.ops.uunet.co.za...
> I have an SBS 2003 Premium server. There is an SQL and a Universe database
> on this server. Every morning the database services seem to hang. When I
try
> and manually restart them, I get the following error message.
> An error 1053 (The service did not respond to the start or control request
> in a timely fashion.) occurred while performing this service operation on
> the SQLServerAgent service.
> Also the Universe Resource Service - same error.
> If I reboot the server, everything is fine.
> How can I resolve this problem?
>
|||I am not sure exactly when it falls over. It is sometime in the night. There
do not seem to be any errors that correspond in the event log.
We are running backups and virus scans in the evening. With backups disabled
problem still occurs.
I have 1.5G RAM in this machine. I can capture memory usage to a log file
through Performance Monitor tonight. How would I make the memory parameter
for the SQL static?
Is it possible that the Universe and SQL are affected by the same problem?
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:OwSaA6DLEHA.1416@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Hi,
> Check the Memory usage during this situation. If the memory is fully
> occupaid then ,Can you make the memory parameter static for SQL Server. I
> feel that this is due to resource contension.
> Thanks
> Hari
> MCDBA
>
> "Peter Downes" <pjtdownes@.hotmail.com> wrote in message
> news:c6la2k$1lue$1@.newsreader02.ops.uunet.co.za...
database[vbcol=seagreen]
> try
request[vbcol=seagreen]
on
>
|||Couple of Ideas...
1. Run a performance logger on the server to see what
resources are low.
2. Put a trace on SQL Server to see when it stops
3. Check the server logs and see if they have errors
4. If you can manage it get some down time on your server
then execute each job separately till you find the one
that causes the error.
To configure the memory
1. Go to EA
2. Right click on your server
3. Select 'properties'
4. Select memory
5. The rest you can guess ;)
Personally I think Hari is correct, it is memory
J
>--Original Message--
>I am not sure exactly when it falls over. It is sometime
in the night. There
>do not seem to be any errors that correspond in the event
log.
>We are running backups and virus scans in the evening.
With backups disabled
>problem still occurs.
>I have 1.5G RAM in this machine. I can capture memory
usage to a log file
>through Performance Monitor tonight. How would I make the
memory parameter
>for the SQL static?
>Is it possible that the Universe and SQL are affected by
the same problem?[vbcol=seagreen]
>
>"Hari" <hari_prasad_k@.hotmail.com> wrote in message
>news:OwSaA6DLEHA.1416@.TK2MSFTNGP09.phx.gbl...
memory is fully[vbcol=seagreen]
for SQL Server. I[vbcol=seagreen]
and a Universe[vbcol=seagreen]
>database
seem to hang. When I[vbcol=seagreen]
message.[vbcol=seagreen]
start or control[vbcol=seagreen]
>request
service operation
>on
>
>.
>
Database problems
I have an SBS 2003 Premium server. There is an SQL and a Universe database
on this server. Every morning the database services seem to hang. When I try
and manually restart them, I get the following error message.
An error 1053 (The service did not respond to the start or control request
in a timely fashion.) occurred while performing this service operation on
the SQLServerAgent service.
Also the Universe Resource Service - same error.
If I reboot the server, everything is fine.
How can I resolve this problem?Hi,
Check the Memory usage during this situation. If the memory is fully
occupaid then ,Can you make the memory parameter static for SQL Server. I
feel that this is due to resource contension.
Thanks
Hari
MCDBA
"Peter Downes" <pjtdownes@.hotmail.com> wrote in message
news:c6la2k$1lue$1@.newsreader02.ops.uunet.co.za...
> I have an SBS 2003 Premium server. There is an SQL and a Universe database
> on this server. Every morning the database services seem to hang. When I
try
> and manually restart them, I get the following error message.
> An error 1053 (The service did not respond to the start or control request
> in a timely fashion.) occurred while performing this service operation on
> the SQLServerAgent service.
> Also the Universe Resource Service - same error.
> If I reboot the server, everything is fine.
> How can I resolve this problem?
>|||I am not sure exactly when it falls over. It is sometime in the night. There
do not seem to be any errors that correspond in the event log.
We are running backups and virus scans in the evening. With backups disabled
problem still occurs.
I have 1.5G RAM in this machine. I can capture memory usage to a log file
through Performance Monitor tonight. How would I make the memory parameter
for the SQL static?
Is it possible that the Universe and SQL are affected by the same problem?
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:OwSaA6DLEHA.1416@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Check the Memory usage during this situation. If the memory is fully
> occupaid then ,Can you make the memory parameter static for SQL Server. I
> feel that this is due to resource contension.
> Thanks
> Hari
> MCDBA
>
> "Peter Downes" <pjtdownes@.hotmail.com> wrote in message
> news:c6la2k$1lue$1@.newsreader02.ops.uunet.co.za...
database[vbcol=seagreen]
> try
request[vbcol=seagreen]
on[vbcol=seagreen]
>|||Couple of Ideas...
1. Run a performance logger on the server to see what
resources are low.
2. Put a trace on SQL Server to see when it stops
3. Check the server logs and see if they have errors
4. If you can manage it get some down time on your server
then execute each job separately till you find the one
that causes the error.
To configure the memory
1. Go to EA
2. Right click on your server
3. Select 'properties'
4. Select memory
5. The rest you can guess ;)
Personally I think Hari is correct, it is memory
J
>--Original Message--
>I am not sure exactly when it falls over. It is sometime
in the night. There
>do not seem to be any errors that correspond in the event
log.
>We are running backups and virus scans in the evening.
With backups disabled
>problem still occurs.
>I have 1.5G RAM in this machine. I can capture memory
usage to a log file
>through Performance Monitor tonight. How would I make the
memory parameter
>for the SQL static?
>Is it possible that the Universe and SQL are affected by
the same problem?
>
>"Hari" <hari_prasad_k@.hotmail.com> wrote in message
>news:OwSaA6DLEHA.1416@.TK2MSFTNGP09.phx.gbl...
memory is fully[vbcol=seagreen]
for SQL Server. I[vbcol=seagreen]
and a Universe[vbcol=seagreen]
>database
seem to hang. When I[vbcol=seagreen]
message.[vbcol=seagreen]
start or control[vbcol=seagreen]
>request
service operation[vbcol=seagreen]
>on
>
>.
>
on this server. Every morning the database services seem to hang. When I try
and manually restart them, I get the following error message.
An error 1053 (The service did not respond to the start or control request
in a timely fashion.) occurred while performing this service operation on
the SQLServerAgent service.
Also the Universe Resource Service - same error.
If I reboot the server, everything is fine.
How can I resolve this problem?Hi,
Check the Memory usage during this situation. If the memory is fully
occupaid then ,Can you make the memory parameter static for SQL Server. I
feel that this is due to resource contension.
Thanks
Hari
MCDBA
"Peter Downes" <pjtdownes@.hotmail.com> wrote in message
news:c6la2k$1lue$1@.newsreader02.ops.uunet.co.za...
> I have an SBS 2003 Premium server. There is an SQL and a Universe database
> on this server. Every morning the database services seem to hang. When I
try
> and manually restart them, I get the following error message.
> An error 1053 (The service did not respond to the start or control request
> in a timely fashion.) occurred while performing this service operation on
> the SQLServerAgent service.
> Also the Universe Resource Service - same error.
> If I reboot the server, everything is fine.
> How can I resolve this problem?
>|||I am not sure exactly when it falls over. It is sometime in the night. There
do not seem to be any errors that correspond in the event log.
We are running backups and virus scans in the evening. With backups disabled
problem still occurs.
I have 1.5G RAM in this machine. I can capture memory usage to a log file
through Performance Monitor tonight. How would I make the memory parameter
for the SQL static?
Is it possible that the Universe and SQL are affected by the same problem?
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:OwSaA6DLEHA.1416@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Check the Memory usage during this situation. If the memory is fully
> occupaid then ,Can you make the memory parameter static for SQL Server. I
> feel that this is due to resource contension.
> Thanks
> Hari
> MCDBA
>
> "Peter Downes" <pjtdownes@.hotmail.com> wrote in message
> news:c6la2k$1lue$1@.newsreader02.ops.uunet.co.za...
database[vbcol=seagreen]
> try
request[vbcol=seagreen]
on[vbcol=seagreen]
>|||Couple of Ideas...
1. Run a performance logger on the server to see what
resources are low.
2. Put a trace on SQL Server to see when it stops
3. Check the server logs and see if they have errors
4. If you can manage it get some down time on your server
then execute each job separately till you find the one
that causes the error.
To configure the memory
1. Go to EA
2. Right click on your server
3. Select 'properties'
4. Select memory
5. The rest you can guess ;)
Personally I think Hari is correct, it is memory
J
>--Original Message--
>I am not sure exactly when it falls over. It is sometime
in the night. There
>do not seem to be any errors that correspond in the event
log.
>We are running backups and virus scans in the evening.
With backups disabled
>problem still occurs.
>I have 1.5G RAM in this machine. I can capture memory
usage to a log file
>through Performance Monitor tonight. How would I make the
memory parameter
>for the SQL static?
>Is it possible that the Universe and SQL are affected by
the same problem?
>
>"Hari" <hari_prasad_k@.hotmail.com> wrote in message
>news:OwSaA6DLEHA.1416@.TK2MSFTNGP09.phx.gbl...
memory is fully[vbcol=seagreen]
for SQL Server. I[vbcol=seagreen]
and a Universe[vbcol=seagreen]
>database
seem to hang. When I[vbcol=seagreen]
message.[vbcol=seagreen]
start or control[vbcol=seagreen]
>request
service operation[vbcol=seagreen]
>on
>
>.
>
Subscribe to:
Posts (Atom)