Showing posts with label solution. Show all posts
Showing posts with label solution. Show all posts

Tuesday, March 27, 2012

Database Snapshot on SAN attached disks

Hi All

I am in process of moving a SQL 2005 solution from a development box that used local storage to UAT environment with SAN attached storage. The solution uses database snapshots

The database files are on the SAN storage but during testing I was unable to create a Database snapshot on the SAN disk. Creating snapshots on the local disk worked fine.

Is their some restriction/problem in using the database snapshot technology with SAN storage?

What edition of Sql server 2005 you have ? Database snapshot is possible only with Enterprise edition I believe
|||

SQL Server Enterprise 2005 SP2 is being used on all systems.

The snapshots are working against the local disks on the server but not against the SAN attached storage.

Regards

Nadreck

|||

Are the SAN attached drives formatted using the NTFS file system? Database Snapshots use NTFS Sparse Files for the underlying technology, and will not work under any other file system.

I have database snapshots on production clustered servers, using SAN storage, and haven't had any problems.

|||Your use of the term "SAN attached" has me wondering. There are Network Attached Storage (NAS) devices that often have their own proprietary file system and then there are Storage Area Networks (SAN) which are usually NTFS in the Windows world. Which type of storage are you referring to? Database snapshots require NTFS.
|||There is no difference between a "SAN" and a local drive to SQL, they both look like local drives. This must be a security issue on the directory.

If you are talking about a "NAS" drive, as in you access it using "\\servername\share", SQL does not support putting data/transaction files on share drives.

|||

The storage is on a true SAN with the disks attached by Fibre Channel and being presented as Local disk.

I have spoken with the SAN administrators and they have confirmed that the disks are formatted as NTFS

The error received when trying to create the sbnapshot was

Msg 1823, Level 16, State 2, Line 1

A database snapshot cannot be created because it failed to start.

Msg 5123, Level 16, State 1, Line 1

CREATE FILE encountered operating system error 5(error not found) while attempting to open or create the physical file 'filename'.

|||I think the login with which you have logged into Sql server(windows authentication) might not be having modify privilege to the folder where the Sparse file is being created ! also check if the sql service account has necessary privileges to that folder ! ! !

Thanxx
Deepak


|||

The logon accounts and service accounts both have local admin rights on the box so write permissions do not appear to be the issue. The mdf and ldf files for the database are both on SAN storage so SQL appears to have sufficient rights to write to these disks. Creating snapshots on local disk (with the same accounts) has no issue.

Obviously it may still be some permissions issue with the SAN but I cannot see any difference.

regards

Nadreck

Database Size...HELP

I am new to SQL so please forgive. I will try my best to describe my
problem. I really need a solution.
I have SQL 2000 with SP4. When I go into Enterprinse manager and right click
on my database it says that the size of the database is 62259.96 and space
available is 0.00.
There are some functions that are not working for my users and I believe
that it is due to there being no space available for the database. There is
265 GB of disk space free on the server and no disk space quotas in place.
Could someone please tell me how to make space available to my database?
Please let me know if more information is needed before anyone can give me
possible solutions.> There are some functions that are not working for my users and I believe that it is due to there
> being no space available for the database.
What do you base this on? Have the users write down the error message, also lock in the eventlog, as
SQL Server would log 1105 or 9002 messages when out of space.
In SQL Server, we pre-allocate storage. SQL Server can autogrow database files, but that comes with
a cost and sometimes it isn't fast enough so you still get out of space messages. You can expand a
database file using ALTER DATABASE command (of right-click in EM, properties).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"John Vee" <john.vee@.ole.net> wrote in message news:OXhJubjYGHA.4580@.TK2MSFTNGP03.phx.gbl...
>I am new to SQL so please forgive. I will try my best to describe my problem. I really need a
>solution.
> I have SQL 2000 with SP4. When I go into Enterprinse manager and right click on my database it
> says that the size of the database is 62259.96 and space available is 0.00.
> There are some functions that are not working for my users and I believe that it is due to there
> being no space available for the database. There is 265 GB of disk space free on the server and no
> disk space quotas in place.
> Could someone please tell me how to make space available to my database?
> Please let me know if more information is needed before anyone can give me possible solutions.
>

Sunday, March 25, 2012

Database Size...HELP

I am new to SQL so please forgive. I will try my best to describe my
problem. I really need a solution.
I have SQL 2000 with SP4. When I go into Enterprinse manager and right click
on my database it says that the size of the database is 62259.96 and space
available is 0.00.
There are some functions that are not working for my users and I believe
that it is due to there being no space available for the database. There is
265 GB of disk space free on the server and no disk space quotas in place.
Could someone please tell me how to make space available to my database?
Please let me know if more information is needed before anyone can give me
possible solutions.> There are some functions that are not working for my users and I believe that it is due to
there
> being no space available for the database.
What do you base this on? Have the users write down the error message, also
lock in the eventlog, as
SQL Server would log 1105 or 9002 messages when out of space.
In SQL Server, we pre-allocate storage. SQL Server can autogrow database fil
es, but that comes with
a cost and sometimes it isn't fast enough so you still get out of space mess
ages. You can expand a
database file using ALTER DATABASE command (of right-click in EM, properties
).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"John Vee" <john.vee@.ole.net> wrote in message news:OXhJubjYGHA.4580@.TK2MSFTNGP03.phx.gbl...

>I am new to SQL so please forgive. I will try my best to describe my proble
m. I really need a
>solution.
> I have SQL 2000 with SP4. When I go into Enterprinse manager and right cli
ck on my database it
> says that the size of the database is 62259.96 and space available is 0.00
.
> There are some functions that are not working for my users and I believe t
hat it is due to there
> being no space available for the database. There is 265 GB of disk space f
ree on the server and no
> disk space quotas in place.
> Could someone please tell me how to make space available to my database?
> Please let me know if more information is needed before anyone can give me
possible solutions.
>