I've got a Sql Server (2000) that is struggling with disk i/o issues
(particularly write). I noticed this in my error log:
The SQL Server cannot obtain a LOCK resource at this time. Rerun your
statement when there are fewer active users or ask the system administrator
to check the SQL Server lock and memory configuration..
Isn't this usually RAM related? Or could it be related somehow to the disk
i/o issues as well?
It could be memory but it's hard to say without more info.
You should also check your lock configurations with:
sp_configure 'show advanced options',1
Reconfigure
exec sp_configure 'locks'
to see if you have a value of 0.
You can also execute sp_lock to monitor the number of locks,
lock resources on the server.
-Sue
On Mon, 7 Nov 2005 12:58:08 -0800, CLM
<CLM@.discussions.microsoft.com> wrote:
>I've got a Sql Server (2000) that is struggling with disk i/o issues
>(particularly write). I noticed this in my error log:
>The SQL Server cannot obtain a LOCK resource at this time. Rerun your
>statement when there are fewer active users or ask the system administrator
>to check the SQL Server lock and memory configuration..
>Isn't this usually RAM related? Or could it be related somehow to the disk
>i/o issues as well?
Showing posts with label disk. Show all posts
Showing posts with label disk. Show all posts
Wednesday, March 28, 2012
Lock Resource
I've got a Sql Server (2000) that is struggling with disk i/o issues
(particularly write). I noticed this in my error log:
The SQL Server cannot obtain a LOCK resource at this time. Rerun your
statement when there are fewer active users or ask the system administrator
to check the SQL Server lock and memory configuration..
Isn't this usually RAM related? Or could it be related somehow to the disk
i/o issues as well?It could be memory but it's hard to say without more info.
You should also check your lock configurations with:
sp_configure 'show advanced options',1
Reconfigure
exec sp_configure 'locks'
to see if you have a value of 0.
You can also execute sp_lock to monitor the number of locks,
lock resources on the server.
-Sue
On Mon, 7 Nov 2005 12:58:08 -0800, CLM
<CLM@.discussions.microsoft.com> wrote:
>I've got a Sql Server (2000) that is struggling with disk i/o issues
>(particularly write). I noticed this in my error log:
>The SQL Server cannot obtain a LOCK resource at this time. Rerun your
>statement when there are fewer active users or ask the system administrator
>to check the SQL Server lock and memory configuration..
>Isn't this usually RAM related? Or could it be related somehow to the disk
>i/o issues as well?
(particularly write). I noticed this in my error log:
The SQL Server cannot obtain a LOCK resource at this time. Rerun your
statement when there are fewer active users or ask the system administrator
to check the SQL Server lock and memory configuration..
Isn't this usually RAM related? Or could it be related somehow to the disk
i/o issues as well?It could be memory but it's hard to say without more info.
You should also check your lock configurations with:
sp_configure 'show advanced options',1
Reconfigure
exec sp_configure 'locks'
to see if you have a value of 0.
You can also execute sp_lock to monitor the number of locks,
lock resources on the server.
-Sue
On Mon, 7 Nov 2005 12:58:08 -0800, CLM
<CLM@.discussions.microsoft.com> wrote:
>I've got a Sql Server (2000) that is struggling with disk i/o issues
>(particularly write). I noticed this in my error log:
>The SQL Server cannot obtain a LOCK resource at this time. Rerun your
>statement when there are fewer active users or ask the system administrator
>to check the SQL Server lock and memory configuration..
>Isn't this usually RAM related? Or could it be related somehow to the disk
>i/o issues as well?
Lock Resource
I've got a Sql Server (2000) that is struggling with disk i/o issues
(particularly write). I noticed this in my error log:
The SQL Server cannot obtain a LOCK resource at this time. Rerun your
statement when there are fewer active users or ask the system administrator
to check the SQL Server lock and memory configuration..
Isn't this usually RAM related? Or could it be related somehow to the disk
i/o issues as well?It could be memory but it's hard to say without more info.
You should also check your lock configurations with:
sp_configure 'show advanced options',1
Reconfigure
exec sp_configure 'locks'
to see if you have a value of 0.
You can also execute sp_lock to monitor the number of locks,
lock resources on the server.
-Sue
On Mon, 7 Nov 2005 12:58:08 -0800, CLM
<CLM@.discussions.microsoft.com> wrote:
>I've got a Sql Server (2000) that is struggling with disk i/o issues
>(particularly write). I noticed this in my error log:
>The SQL Server cannot obtain a LOCK resource at this time. Rerun your
>statement when there are fewer active users or ask the system administrator
>to check the SQL Server lock and memory configuration..
>Isn't this usually RAM related? Or could it be related somehow to the disk
>i/o issues as well?
(particularly write). I noticed this in my error log:
The SQL Server cannot obtain a LOCK resource at this time. Rerun your
statement when there are fewer active users or ask the system administrator
to check the SQL Server lock and memory configuration..
Isn't this usually RAM related? Or could it be related somehow to the disk
i/o issues as well?It could be memory but it's hard to say without more info.
You should also check your lock configurations with:
sp_configure 'show advanced options',1
Reconfigure
exec sp_configure 'locks'
to see if you have a value of 0.
You can also execute sp_lock to monitor the number of locks,
lock resources on the server.
-Sue
On Mon, 7 Nov 2005 12:58:08 -0800, CLM
<CLM@.discussions.microsoft.com> wrote:
>I've got a Sql Server (2000) that is struggling with disk i/o issues
>(particularly write). I noticed this in my error log:
>The SQL Server cannot obtain a LOCK resource at this time. Rerun your
>statement when there are fewer active users or ask the system administrator
>to check the SQL Server lock and memory configuration..
>Isn't this usually RAM related? Or could it be related somehow to the disk
>i/o issues as well?
Monday, March 19, 2012
Location for audit logs?
Hi,
I saw in this or the SQL Server Security news group that it's recommended to
store auditing logs on an unused disk drive because auditing logs could grow
wildly. But based on this article
http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx,
SQL Server doesn't let you log auditable events to an alternative location.
<QUOTE>After you enable C2 auditing for the default database or for an
instance, the database server will log all activity to the data directory
that you specified during the installation process. (SQL Server doesn't let
you log auditable events to an alternative location.) This directory holds
the databases that SQL Server initially created. This directory is also the
default location for all new databases and their transaction log
files.</QUOTE>
Now I'm confused. I have data/transaction logs on one drive, I'm planning
to add additional disk drive specifically for auditing. Is it possible to
direct auditing logs to the new drive?
Thanks,
Bing
Hi Bing
"bing" wrote:
> Hi,
> I saw in this or the SQL Server Security news group that it's recommended to
> store auditing logs on an unused disk drive because auditing logs could grow
> wildly. But based on this article
> http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx,
> SQL Server doesn't let you log auditable events to an alternative location.
>
> <QUOTE>After you enable C2 auditing for the default database or for an
> instance, the database server will log all activity to the data directory
> that you specified during the installation process. (SQL Server doesn't let
> you log auditable events to an alternative location.) This directory holds
> the databases that SQL Server initially created. This directory is also the
> default location for all new databases and their transaction log
> files.</QUOTE>
> Now I'm confused. I have data/transaction logs on one drive, I'm planning
> to add additional disk drive specifically for auditing. Is it possible to
> direct auditing logs to the new drive?
> Thanks,
> Bing
If you change the default data and log directories in the Database
properties task in Enterprise Manager on the properties page of the instance
(right click) do new audit files get created their (you may need to restart)?
If not you can move the databases away from this location using
sp_detach_db/sp_attach_db or backup/restore see
http://support.microsoft.com/kb/314546. When you do the initial install, the
default location is the system disc e.g. C:\Program Files\Microsoft SQL
Server... this should be changed as filling up the system disc with audit
logs will make the system unusable.
You can move system databases (possibly to different spindles!) as well as
user databases http://support.microsoft.com/kb/224071/ and using different
discs for full text catalogs will also be a way of improving performance
http://support.microsoft.com/kb/240867/ Database data files and log files
should be on separate drive arrays as they perform different types of I/O
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlIObasics.mspx
You should also consider what RAID level and resilience you require for
these disc subsystems.
John
I saw in this or the SQL Server Security news group that it's recommended to
store auditing logs on an unused disk drive because auditing logs could grow
wildly. But based on this article
http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx,
SQL Server doesn't let you log auditable events to an alternative location.
<QUOTE>After you enable C2 auditing for the default database or for an
instance, the database server will log all activity to the data directory
that you specified during the installation process. (SQL Server doesn't let
you log auditable events to an alternative location.) This directory holds
the databases that SQL Server initially created. This directory is also the
default location for all new databases and their transaction log
files.</QUOTE>
Now I'm confused. I have data/transaction logs on one drive, I'm planning
to add additional disk drive specifically for auditing. Is it possible to
direct auditing logs to the new drive?
Thanks,
Bing
Hi Bing
"bing" wrote:
> Hi,
> I saw in this or the SQL Server Security news group that it's recommended to
> store auditing logs on an unused disk drive because auditing logs could grow
> wildly. But based on this article
> http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx,
> SQL Server doesn't let you log auditable events to an alternative location.
>
> <QUOTE>After you enable C2 auditing for the default database or for an
> instance, the database server will log all activity to the data directory
> that you specified during the installation process. (SQL Server doesn't let
> you log auditable events to an alternative location.) This directory holds
> the databases that SQL Server initially created. This directory is also the
> default location for all new databases and their transaction log
> files.</QUOTE>
> Now I'm confused. I have data/transaction logs on one drive, I'm planning
> to add additional disk drive specifically for auditing. Is it possible to
> direct auditing logs to the new drive?
> Thanks,
> Bing
If you change the default data and log directories in the Database
properties task in Enterprise Manager on the properties page of the instance
(right click) do new audit files get created their (you may need to restart)?
If not you can move the databases away from this location using
sp_detach_db/sp_attach_db or backup/restore see
http://support.microsoft.com/kb/314546. When you do the initial install, the
default location is the system disc e.g. C:\Program Files\Microsoft SQL
Server... this should be changed as filling up the system disc with audit
logs will make the system unusable.
You can move system databases (possibly to different spindles!) as well as
user databases http://support.microsoft.com/kb/224071/ and using different
discs for full text catalogs will also be a way of improving performance
http://support.microsoft.com/kb/240867/ Database data files and log files
should be on separate drive arrays as they perform different types of I/O
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlIObasics.mspx
You should also consider what RAID level and resilience you require for
these disc subsystems.
John
Location for audit logs?
Hi,
I saw in this or the SQL Server Security news group that it's recommended to
store auditing logs on an unused disk drive because auditing logs could grow
wildly. But based on this article
http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx,
SQL Server doesn't let you log auditable events to an alternative location.
<QUOTE>After you enable C2 auditing for the default database or for an
instance, the database server will log all activity to the data directory
that you specified during the installation process. (SQL Server doesn't let
you log auditable events to an alternative location.) This directory holds
the databases that SQL Server initially created. This directory is also the
default location for all new databases and their transaction log
files.</QUOTE>
Now I'm confused. I have data/transaction logs on one drive, I'm planning
to add additional disk drive specifically for auditing. Is it possible to
direct auditing logs to the new drive?
Thanks,
BingHi Bing
"bing" wrote:
> Hi,
> I saw in this or the SQL Server Security news group that it's recommended to
> store auditing logs on an unused disk drive because auditing logs could grow
> wildly. But based on this article
> http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx,
> SQL Server doesn't let you log auditable events to an alternative location.
>
> <QUOTE>After you enable C2 auditing for the default database or for an
> instance, the database server will log all activity to the data directory
> that you specified during the installation process. (SQL Server doesn't let
> you log auditable events to an alternative location.) This directory holds
> the databases that SQL Server initially created. This directory is also the
> default location for all new databases and their transaction log
> files.</QUOTE>
> Now I'm confused. I have data/transaction logs on one drive, I'm planning
> to add additional disk drive specifically for auditing. Is it possible to
> direct auditing logs to the new drive?
> Thanks,
> Bing
If you change the default data and log directories in the Database
properties task in Enterprise Manager on the properties page of the instance
(right click) do new audit files get created their (you may need to restart)?
If not you can move the databases away from this location using
sp_detach_db/sp_attach_db or backup/restore see
http://support.microsoft.com/kb/314546. When you do the initial install, the
default location is the system disc e.g. C:\Program Files\Microsoft SQL
Server... this should be changed as filling up the system disc with audit
logs will make the system unusable.
You can move system databases (possibly to different spindles!) as well as
user databases http://support.microsoft.com/kb/224071/ and using different
discs for full text catalogs will also be a way of improving performance
http://support.microsoft.com/kb/240867/ Database data files and log files
should be on separate drive arrays as they perform different types of I/O
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlIObasics.mspx
You should also consider what RAID level and resilience you require for
these disc subsystems.
John
I saw in this or the SQL Server Security news group that it's recommended to
store auditing logs on an unused disk drive because auditing logs could grow
wildly. But based on this article
http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx,
SQL Server doesn't let you log auditable events to an alternative location.
<QUOTE>After you enable C2 auditing for the default database or for an
instance, the database server will log all activity to the data directory
that you specified during the installation process. (SQL Server doesn't let
you log auditable events to an alternative location.) This directory holds
the databases that SQL Server initially created. This directory is also the
default location for all new databases and their transaction log
files.</QUOTE>
Now I'm confused. I have data/transaction logs on one drive, I'm planning
to add additional disk drive specifically for auditing. Is it possible to
direct auditing logs to the new drive?
Thanks,
BingHi Bing
"bing" wrote:
> Hi,
> I saw in this or the SQL Server Security news group that it's recommended to
> store auditing logs on an unused disk drive because auditing logs could grow
> wildly. But based on this article
> http://www.microsoft.com/technet/security/prodtech/sqlserver/sql2kaud.mspx,
> SQL Server doesn't let you log auditable events to an alternative location.
>
> <QUOTE>After you enable C2 auditing for the default database or for an
> instance, the database server will log all activity to the data directory
> that you specified during the installation process. (SQL Server doesn't let
> you log auditable events to an alternative location.) This directory holds
> the databases that SQL Server initially created. This directory is also the
> default location for all new databases and their transaction log
> files.</QUOTE>
> Now I'm confused. I have data/transaction logs on one drive, I'm planning
> to add additional disk drive specifically for auditing. Is it possible to
> direct auditing logs to the new drive?
> Thanks,
> Bing
If you change the default data and log directories in the Database
properties task in Enterprise Manager on the properties page of the instance
(right click) do new audit files get created their (you may need to restart)?
If not you can move the databases away from this location using
sp_detach_db/sp_attach_db or backup/restore see
http://support.microsoft.com/kb/314546. When you do the initial install, the
default location is the system disc e.g. C:\Program Files\Microsoft SQL
Server... this should be changed as filling up the system disc with audit
logs will make the system unusable.
You can move system databases (possibly to different spindles!) as well as
user databases http://support.microsoft.com/kb/224071/ and using different
discs for full text catalogs will also be a way of improving performance
http://support.microsoft.com/kb/240867/ Database data files and log files
should be on separate drive arrays as they perform different types of I/O
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlIObasics.mspx
You should also consider what RAID level and resilience you require for
these disc subsystems.
John
Location for audit logs?
Hi,
I saw in this or the SQL Server Security news group that it's recommended to
store auditing logs on an unused disk drive because auditing logs could grow
wildly. But based on this article
http://www.microsoft.com/technet/se.../sql2kaud.mspx,
SQL Server doesn't let you log auditable events to an alternative location.
<QUOTE>After you enable C2 auditing for the default database or for an
instance, the database server will log all activity to the data directory
that you specified during the installation process. (SQL Server doesn't let
you log auditable events to an alternative location.) This directory holds
the databases that SQL Server initially created. This directory is also the
default location for all new databases and their transaction log
files.</QUOTE>
Now I'm confused. I have data/transaction logs on one drive, I'm planning
to add additional disk drive specifically for auditing. Is it possible to
direct auditing logs to the new drive?
Thanks,
BingHi Bing
"bing" wrote:
> Hi,
> I saw in this or the SQL Server Security news group that it's recommended
to
> store auditing logs on an unused disk drive because auditing logs could gr
ow
> wildly. But based on this article
> If you change the default data and log directories in the Databaseproperties task in Enterprise Manager on the properties page of the instance(right click) do new audit files get created their (you may need to restart)?If not you can move the databases away from this location usingsp_detach_db/sp_attach_db or backup/restore see[url]http://support.microsoft.com/kb/314546." target="_blank">http://www.microsoft.com/technet/se...com/kb/314546. When you do the initial install, the
default location is the system disc e.g. C:\Program Files\Microsoft SQL
Server... this should be changed as filling up the system disc with audit
logs will make the system unusable.
You can move system databases (possibly to different spindles!) as well as
user databases http://support.microsoft.com/kb/224071/ and using different
discs for full text catalogs will also be a way of improving performance
http://support.microsoft.com/kb/240867/ Database data files and log files
should be on separate drive arrays as they perform different types of I/O
[url]http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlIObasics.mspx[/u
rl]
You should also consider what RAID level and resilience you require for
these disc subsystems.
John
I saw in this or the SQL Server Security news group that it's recommended to
store auditing logs on an unused disk drive because auditing logs could grow
wildly. But based on this article
http://www.microsoft.com/technet/se.../sql2kaud.mspx,
SQL Server doesn't let you log auditable events to an alternative location.
<QUOTE>After you enable C2 auditing for the default database or for an
instance, the database server will log all activity to the data directory
that you specified during the installation process. (SQL Server doesn't let
you log auditable events to an alternative location.) This directory holds
the databases that SQL Server initially created. This directory is also the
default location for all new databases and their transaction log
files.</QUOTE>
Now I'm confused. I have data/transaction logs on one drive, I'm planning
to add additional disk drive specifically for auditing. Is it possible to
direct auditing logs to the new drive?
Thanks,
BingHi Bing
"bing" wrote:
> Hi,
> I saw in this or the SQL Server Security news group that it's recommended
to
> store auditing logs on an unused disk drive because auditing logs could gr
ow
> wildly. But based on this article
> If you change the default data and log directories in the Databaseproperties task in Enterprise Manager on the properties page of the instance(right click) do new audit files get created their (you may need to restart)?If not you can move the databases away from this location usingsp_detach_db/sp_attach_db or backup/restore see[url]http://support.microsoft.com/kb/314546." target="_blank">http://www.microsoft.com/technet/se...com/kb/314546. When you do the initial install, the
default location is the system disc e.g. C:\Program Files\Microsoft SQL
Server... this should be changed as filling up the system disc with audit
logs will make the system unusable.
You can move system databases (possibly to different spindles!) as well as
user databases http://support.microsoft.com/kb/224071/ and using different
discs for full text catalogs will also be a way of improving performance
http://support.microsoft.com/kb/240867/ Database data files and log files
should be on separate drive arrays as they perform different types of I/O
[url]http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlIObasics.mspx[/u
rl]
You should also consider what RAID level and resilience you require for
these disc subsystems.
John
Friday, February 24, 2012
Local drive doesn't appear more !
Hi,
I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
partitions (C, D, E). This happened unexpectedly when I was deleting a
database.
I can see normally the letter E in windows explorer, but it doesn't appear
and permit me more create a database em that letter.
Any idea ?
Regards,
Vitor Mauricio
Check file permissions to ensure the SQL Server service account has full
permissions to the root folder.
Hope this helps.
Dan Guzman
SQL Server MVP
"Vitor Mauricio de N. Silva" <vitor_mauricio@.hotmail.com> wrote in message
news:e4yjo36ZEHA.3112@.tk2msftngp13.phx.gbl...
> Hi,
> I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
> partitions (C, D, E). This happened unexpectedly when I was deleting a
> database.
> I can see normally the letter E in windows explorer, but it doesn't appear
> and permit me more create a database em that letter.
> Any idea ?
> Regards,
> Vitor Mauricio
>
|||Vitor,
Adding to Dan's post, deleting a database would not have done anything
to your partitions, or your file system security settings. This would
have been a separate operation.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Dan Guzman wrote:
> Check file permissions to ensure the SQL Server service account has full
> permissions to the root folder.
>
|||Check event viewer for any information on this behaviour.
--
Satya SKJ
"Vitor Mauricio de N. Silva" wrote:
> Hi,
> I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
> partitions (C, D, E). This happened unexpectedly when I was deleting a
> database.
> I can see normally the letter E in windows explorer, but it doesn't appear
> and permit me more create a database em that letter.
> Any idea ?
> Regards,
> Vitor Mauricio
>
>
|||All,
I check the file permission and everything is ok. In the event viewer I
cant see any error.
I never see this before, but the problems continue.
Thanks in advance for any suggestions,
Vitor Mauricio
"Vitor Mauricio de N. Silva" <vitor_mauricio@.hotmail.com> wrote in message
news:e4yjo36ZEHA.3112@.tk2msftngp13.phx.gbl...
> Hi,
> I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
> partitions (C, D, E). This happened unexpectedly when I was deleting a
> database.
> I can see normally the letter E in windows explorer, but it doesn't appear
> and permit me more create a database em that letter.
> Any idea ?
> Regards,
> Vitor Mauricio
>
I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
partitions (C, D, E). This happened unexpectedly when I was deleting a
database.
I can see normally the letter E in windows explorer, but it doesn't appear
and permit me more create a database em that letter.
Any idea ?
Regards,
Vitor Mauricio
Check file permissions to ensure the SQL Server service account has full
permissions to the root folder.
Hope this helps.
Dan Guzman
SQL Server MVP
"Vitor Mauricio de N. Silva" <vitor_mauricio@.hotmail.com> wrote in message
news:e4yjo36ZEHA.3112@.tk2msftngp13.phx.gbl...
> Hi,
> I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
> partitions (C, D, E). This happened unexpectedly when I was deleting a
> database.
> I can see normally the letter E in windows explorer, but it doesn't appear
> and permit me more create a database em that letter.
> Any idea ?
> Regards,
> Vitor Mauricio
>
|||Vitor,
Adding to Dan's post, deleting a database would not have done anything
to your partitions, or your file system security settings. This would
have been a separate operation.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Dan Guzman wrote:
> Check file permissions to ensure the SQL Server service account has full
> permissions to the root folder.
>
|||Check event viewer for any information on this behaviour.
--
Satya SKJ
"Vitor Mauricio de N. Silva" wrote:
> Hi,
> I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
> partitions (C, D, E). This happened unexpectedly when I was deleting a
> database.
> I can see normally the letter E in windows explorer, but it doesn't appear
> and permit me more create a database em that letter.
> Any idea ?
> Regards,
> Vitor Mauricio
>
>
|||All,
I check the file permission and everything is ok. In the event viewer I
cant see any error.
I never see this before, but the problems continue.
Thanks in advance for any suggestions,
Vitor Mauricio
"Vitor Mauricio de N. Silva" <vitor_mauricio@.hotmail.com> wrote in message
news:e4yjo36ZEHA.3112@.tk2msftngp13.phx.gbl...
> Hi,
> I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
> partitions (C, D, E). This happened unexpectedly when I was deleting a
> database.
> I can see normally the letter E in windows explorer, but it doesn't appear
> and permit me more create a database em that letter.
> Any idea ?
> Regards,
> Vitor Mauricio
>
Local drive doesn't appear more !
Hi,
I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
partitions (C, D, E). This happened unexpectedly when I was deleting a
database.
I can see normally the letter E in windows explorer, but it doesn't appear
and permit me more create a database em that letter.
Any idea ?
Regards,
Vitor MauricioCheck file permissions to ensure the SQL Server service account has full
permissions to the root folder.
Hope this helps.
Dan Guzman
SQL Server MVP
"Vitor Mauricio de N. Silva" <vitor_mauricio@.hotmail.com> wrote in message
news:e4yjo36ZEHA.3112@.tk2msftngp13.phx.gbl...
> Hi,
> I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
> partitions (C, D, E). This happened unexpectedly when I was deleting a
> database.
> I can see normally the letter E in windows explorer, but it doesn't appear
> and permit me more create a database em that letter.
> Any idea ?
> Regards,
> Vitor Mauricio
>|||Vitor,
Adding to Dan's post, deleting a database would not have done anything
to your partitions, or your file system security settings. This would
have been a separate operation.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Dan Guzman wrote:
> Check file permissions to ensure the SQL Server service account has full
> permissions to the root folder.
>|||Check event viewer for any information on this behaviour.
--
--
Satya SKJ
"Vitor Mauricio de N. Silva" wrote:
> Hi,
> I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
> partitions (C, D, E). This happened unexpectedly when I was deleting a
> database.
> I can see normally the letter E in windows explorer, but it doesn't appear
> and permit me more create a database em that letter.
> Any idea ?
> Regards,
> Vitor Mauricio
>
>|||All,
I check the file permission and everything is ok. In the event viewer I
cant see any error.
I never see this before, but the problems continue.
Thanks in advance for any suggestions,
Vitor Mauricio
"Vitor Mauricio de N. Silva" <vitor_mauricio@.hotmail.com> wrote in message
news:e4yjo36ZEHA.3112@.tk2msftngp13.phx.gbl...
> Hi,
> I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
> partitions (C, D, E). This happened unexpectedly when I was deleting a
> database.
> I can see normally the letter E in windows explorer, but it doesn't appear
> and permit me more create a database em that letter.
> Any idea ?
> Regards,
> Vitor Mauricio
>
I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
partitions (C, D, E). This happened unexpectedly when I was deleting a
database.
I can see normally the letter E in windows explorer, but it doesn't appear
and permit me more create a database em that letter.
Any idea ?
Regards,
Vitor MauricioCheck file permissions to ensure the SQL Server service account has full
permissions to the root folder.
Hope this helps.
Dan Guzman
SQL Server MVP
"Vitor Mauricio de N. Silva" <vitor_mauricio@.hotmail.com> wrote in message
news:e4yjo36ZEHA.3112@.tk2msftngp13.phx.gbl...
> Hi,
> I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
> partitions (C, D, E). This happened unexpectedly when I was deleting a
> database.
> I can see normally the letter E in windows explorer, but it doesn't appear
> and permit me more create a database em that letter.
> Any idea ?
> Regards,
> Vitor Mauricio
>|||Vitor,
Adding to Dan's post, deleting a database would not have done anything
to your partitions, or your file system security settings. This would
have been a separate operation.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Dan Guzman wrote:
> Check file permissions to ensure the SQL Server service account has full
> permissions to the root folder.
>|||Check event viewer for any information on this behaviour.
--
--
Satya SKJ
"Vitor Mauricio de N. Silva" wrote:
> Hi,
> I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
> partitions (C, D, E). This happened unexpectedly when I was deleting a
> database.
> I can see normally the letter E in windows explorer, but it doesn't appear
> and permit me more create a database em that letter.
> Any idea ?
> Regards,
> Vitor Mauricio
>
>|||All,
I check the file permission and everything is ok. In the event viewer I
cant see any error.
I never see this before, but the problems continue.
Thanks in advance for any suggestions,
Vitor Mauricio
"Vitor Mauricio de N. Silva" <vitor_mauricio@.hotmail.com> wrote in message
news:e4yjo36ZEHA.3112@.tk2msftngp13.phx.gbl...
> Hi,
> I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
> partitions (C, D, E). This happened unexpectedly when I was deleting a
> database.
> I can see normally the letter E in windows explorer, but it doesn't appear
> and permit me more create a database em that letter.
> Any idea ?
> Regards,
> Vitor Mauricio
>
Local drive doesn't appear more !
Hi,
I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
partitions (C, D, E). This happened unexpectedly when I was deleting a
database.
I can see normally the letter E in windows explorer, but it doesn't appear
and permit me more create a database em that letter.
Any idea ?
Regards,
Vitor MauricioCheck file permissions to ensure the SQL Server service account has full
permissions to the root folder.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Vitor Mauricio de N. Silva" <vitor_mauricio@.hotmail.com> wrote in message
news:e4yjo36ZEHA.3112@.tk2msftngp13.phx.gbl...
> Hi,
> I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
> partitions (C, D, E). This happened unexpectedly when I was deleting a
> database.
> I can see normally the letter E in windows explorer, but it doesn't appear
> and permit me more create a database em that letter.
> Any idea ?
> Regards,
> Vitor Mauricio
>|||Vitor,
Adding to Dan's post, deleting a database would not have done anything
to your partitions, or your file system security settings. This would
have been a separate operation.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Dan Guzman wrote:
> Check file permissions to ensure the SQL Server service account has full
> permissions to the root folder.
>|||All,
I check the file permission and everything is ok. In the event viewer I
can´t see any error.
I never see this before, but the problems continue.
Thanks in advance for any suggestions,
Vitor Mauricio
"Vitor Mauricio de N. Silva" <vitor_mauricio@.hotmail.com> wrote in message
news:e4yjo36ZEHA.3112@.tk2msftngp13.phx.gbl...
> Hi,
> I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
> partitions (C, D, E). This happened unexpectedly when I was deleting a
> database.
> I can see normally the letter E in windows explorer, but it doesn't appear
> and permit me more create a database em that letter.
> Any idea ?
> Regards,
> Vitor Mauricio
>
I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
partitions (C, D, E). This happened unexpectedly when I was deleting a
database.
I can see normally the letter E in windows explorer, but it doesn't appear
and permit me more create a database em that letter.
Any idea ?
Regards,
Vitor MauricioCheck file permissions to ensure the SQL Server service account has full
permissions to the root folder.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Vitor Mauricio de N. Silva" <vitor_mauricio@.hotmail.com> wrote in message
news:e4yjo36ZEHA.3112@.tk2msftngp13.phx.gbl...
> Hi,
> I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
> partitions (C, D, E). This happened unexpectedly when I was deleting a
> database.
> I can see normally the letter E in windows explorer, but it doesn't appear
> and permit me more create a database em that letter.
> Any idea ?
> Regards,
> Vitor Mauricio
>|||Vitor,
Adding to Dan's post, deleting a database would not have done anything
to your partitions, or your file system security settings. This would
have been a separate operation.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Dan Guzman wrote:
> Check file permissions to ensure the SQL Server service account has full
> permissions to the root folder.
>|||All,
I check the file permission and everything is ok. In the event viewer I
can´t see any error.
I never see this before, but the problems continue.
Thanks in advance for any suggestions,
Vitor Mauricio
"Vitor Mauricio de N. Silva" <vitor_mauricio@.hotmail.com> wrote in message
news:e4yjo36ZEHA.3112@.tk2msftngp13.phx.gbl...
> Hi,
> I have a SQL Server 7.0 (SP4) with 1 phisical disk drive and 3 logical
> partitions (C, D, E). This happened unexpectedly when I was deleting a
> database.
> I can see normally the letter E in windows explorer, but it doesn't appear
> and permit me more create a database em that letter.
> Any idea ?
> Regards,
> Vitor Mauricio
>
Subscribe to:
Posts (Atom)