Showing posts with label drive. Show all posts
Showing posts with label drive. Show all posts

Sunday, March 25, 2012

Can't attach db - says read-only

Hi all,
SQL novice here.
I had a SQL Server 2000 machine that died, but it had some
data I need, so i pulled the drive, found the SQL data folder
and copied it to a network location.
On my SQL Server 2003 machine runnig SQL Server Express, I
right click on Databases, select Attach, point to the database
I want, and the process fials saying the data is read-only, make
it read write and try again.
Problem is, the files are not read-only. I checked and reset
them several times, and each attempt fails with the same message.
How can I attach this database to my sql server?
Thanks,
kpg
There is a article on Microsoft's web site that briefly discusses this issue
on SQL 2005 Express:
http://msdn2.microsoft.com/en-us/library/bb264564.aspx
If you've already checked the permissions on the file, see if you can check
the permissions you have on the database server and folder where the file is
being written to. Your permissions may be different than what they were on
the original DB server.
"kpg*" wrote:

> Hi all,
> SQL novice here.
> I had a SQL Server 2000 machine that died, but it had some
> data I need, so i pulled the drive, found the SQL data folder
> and copied it to a network location.
> On my SQL Server 2003 machine runnig SQL Server Express, I
> right click on Databases, select Attach, point to the database
> I want, and the process fials saying the data is read-only, make
> it read write and try again.
> Problem is, the files are not read-only. I checked and reset
> them several times, and each attempt fails with the same message.
> How can I attach this database to my sql server?
> Thanks,
> kpg
>
|||> There is a article on Microsoft's web site that briefly discusses this
> issue on SQL 2005 Express:
> http://msdn2.microsoft.com/en-us/library/bb264564.aspx
> If you've already checked the permissions on the file, see if you can
> check the permissions you have on the database server and folder where
> the file is being written to. Your permissions may be different than
> what they were on the original DB server.
Thank you * 100!
I copied the db file into the data folder of the sql 2005 instance
and yes, I was able to attach it. So it was a folder permission
issue.
Thanks again!
kpg
sql

Can't attach db - says read-only

Hi all,
SQL novice here.
I had a SQL Server 2000 machine that died, but it had some
data I need, so i pulled the drive, found the SQL data folder
and copied it to a network location.
On my SQL Server 2003 machine runnig SQL Server Express, I
right click on Databases, select Attach, point to the database
I want, and the process fials saying the data is read-only, make
it read write and try again.
Problem is, the files are not read-only. I checked and reset
them several times, and each attempt fails with the same message.
How can I attach this database to my sql server?
Thanks,
kpgThere is a article on Microsoft's web site that briefly discusses this issue
on SQL 2005 Express:
http://msdn2.microsoft.com/en-us/library/bb264564.aspx
If you've already checked the permissions on the file, see if you can check
the permissions you have on the database server and folder where the file is
being written to. Your permissions may be different than what they were on
the original DB server.
"kpg*" wrote:
> Hi all,
> SQL novice here.
> I had a SQL Server 2000 machine that died, but it had some
> data I need, so i pulled the drive, found the SQL data folder
> and copied it to a network location.
> On my SQL Server 2003 machine runnig SQL Server Express, I
> right click on Databases, select Attach, point to the database
> I want, and the process fials saying the data is read-only, make
> it read write and try again.
> Problem is, the files are not read-only. I checked and reset
> them several times, and each attempt fails with the same message.
> How can I attach this database to my sql server?
> Thanks,
> kpg
>|||> There is a article on Microsoft's web site that briefly discusses this
> issue on SQL 2005 Express:
> http://msdn2.microsoft.com/en-us/library/bb264564.aspx
> If you've already checked the permissions on the file, see if you can
> check the permissions you have on the database server and folder where
> the file is being written to. Your permissions may be different than
> what they were on the original DB server.
Thank you * 100!
I copied the db file into the data folder of the sql 2005 instance
and yes, I was able to attach it. So it was a folder permission
issue.
Thanks again!
kpg

Can't attach db - says read-only

Hi all,
SQL novice here.
I had a SQL Server 2000 machine that died, but it had some
data I need, so i pulled the drive, found the SQL data folder
and copied it to a network location.
On my SQL Server 2003 machine runnig SQL Server Express, I
right click on Databases, select Attach, point to the database
I want, and the process fials saying the data is read-only, make
it read write and try again.
Problem is, the files are not read-only. I checked and reset
them several times, and each attempt fails with the same message.
How can I attach this database to my sql server?
Thanks,
kpgThere is a article on Microsoft's web site that briefly discusses this issue
on SQL 2005 Express:
http://msdn2.microsoft.com/en-us/library/bb264564.aspx
If you've already checked the permissions on the file, see if you can check
the permissions you have on the database server and folder where the file is
being written to. Your permissions may be different than what they were on
the original DB server.
"kpg*" wrote:

> Hi all,
> SQL novice here.
> I had a SQL Server 2000 machine that died, but it had some
> data I need, so i pulled the drive, found the SQL data folder
> and copied it to a network location.
> On my SQL Server 2003 machine runnig SQL Server Express, I
> right click on Databases, select Attach, point to the database
> I want, and the process fials saying the data is read-only, make
> it read write and try again.
> Problem is, the files are not read-only. I checked and reset
> them several times, and each attempt fails with the same message.
> How can I attach this database to my sql server?
> Thanks,
> kpg
>|||> There is a article on Microsoft's web site that briefly discusses this
> issue on SQL 2005 Express:
> http://msdn2.microsoft.com/en-us/library/bb264564.aspx
> If you've already checked the permissions on the file, see if you can
> check the permissions you have on the database server and folder where
> the file is being written to. Your permissions may be different than
> what they were on the original DB server.
Thank you * 100!
I copied the db file into the data folder of the sql 2005 instance
and yes, I was able to attach it. So it was a folder permission
issue.
Thanks again!
kpg

Tuesday, March 20, 2012

can't access server

Hi, I'm having problem with a workstation connecting to the Server's SQL
Server. The workstation can access the server's hard drive via share and
TCP/IP seems to be working. But the workstation just can't access the
server.
how to tack it down? Thanks.
Hi
What is the error message?
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"js" <js@.someone.com> wrote in message
news:uzlVHEDLFHA.3628@.TK2MSFTNGP10.phx.gbl...
> Hi, I'm having problem with a workstation connecting to the Server's SQL
> Server. The workstation can access the server's hard drive via share and
> TCP/IP seems to be working. But the workstation just can't access the
> server.
> how to tack it down? Thanks.
>
|||Thanks Mike,
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:eD0%23SeHLFHA.2716@.TK2MSFTNGP15.phx.gbl...
> Hi
> What is the error message?
Error: SQL server does not exist or access denied.
It works local, but not trying to connect from another computer.
And I found there are two instance of sql server.
how to check it out? thanks.
sql

can't access server

Hi, I'm having problem with a workstation connecting to the Server's SQL
Server. The workstation can access the server's hard drive via share and
TCP/IP seems to be working. But the workstation just can't access the
server.
how to tack it down? Thanks.Hi
What is the error message?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"js" <js@.someone.com> wrote in message
news:uzlVHEDLFHA.3628@.TK2MSFTNGP10.phx.gbl...
> Hi, I'm having problem with a workstation connecting to the Server's SQL
> Server. The workstation can access the server's hard drive via share and
> TCP/IP seems to be working. But the workstation just can't access the
> server.
> how to tack it down? Thanks.
>|||Thanks Mike,
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:eD0%23SeHLFHA.2716@.TK2MSFTNGP15.phx.gbl...
> Hi
> What is the error message?
Error: SQL server does not exist or access denied.
It works local, but not trying to connect from another computer.
And I found there are two instance of sql server.
how to check it out? thanks.

Sunday, March 11, 2012

Cannot View My Database Diagrams

I recently reinstalled Visual Studio and SQL Server 2005 Developer Edition
onto a new (larger) hard drive and so far everything has been working as
before for my database, but when I went to view my database diagrams, I am
now getting this message. I tried as the message suggested to change the
database owner, but this only results in error messages. Neither can I add
any new database diagrams.
Anyone have any ideas as to how to solve such a problem?
Thanks,
Paul
---
TITLE: Microsoft SQL Server Management Studio
--
Database diagram support objects cannot be installed because this database
does not have a valid owner. To continue, first use the Files page of the
Database Properties dialog box or the ALTER AUTHORIZATION statement to set
the database owner to a valid login, then add the database diagram support
objects.What is the compatibility mode of the database?
You can check with:
select compatibility_level
from sys.databases
where name = 'YourDatabase'
It needs to be at 90 to use the diagrams. I think this was
fixed in the service pack so the other alternative is to
apply SP1.
-Sue
On Tue, 17 Oct 2006 08:37:01 -0700, a
<a@.discussions.microsoft.com> wrote:

>I recently reinstalled Visual Studio and SQL Server 2005 Developer Edition
>onto a new (larger) hard drive and so far everything has been working as
>before for my database, but when I went to view my database diagrams, I am
>now getting this message. I tried as the message suggested to change the
>database owner, but this only results in error messages. Neither can I add
>any new database diagrams.
>Anyone have any ideas as to how to solve such a problem?
>Thanks,
>Paul
>---
>
>TITLE: Microsoft SQL Server Management Studio
>--
>Database diagram support objects cannot be installed because this database
>does not have a valid owner. To continue, first use the Files page of the
>Database Properties dialog box or the ALTER AUTHORIZATION statement to set
>the database owner to a valid login, then add the database diagram support
>objects.
>--

Tuesday, February 14, 2012

cannot see second drive??

I am running an SQL database on a win2000 server with SQL 2000 and all updat
ed service packs. I have a database that I would like to move to a second dr
ive on the same server. When I look into the database (properties\database l
ocations) I cannot see the
second drive, only the drive that SQL is installed on. The second drive is f
ormatted and data is on it already but I cannot see it when I use the browse
button from the above location. How do I see this second drive? Thanks in a
dvance for any help on thisVerify that the account that SQL Server starts under has full control of
the root of the drive. If the local system account is being used then make
sure the SYSTEM acount ahs full control.
Rand
This posting is provided "as is" with no warranties and confers no rights.

cannot see second drive??

I am running an SQL database on a win2000 server with SQL 2000 and all updated service packs. I have a database that I would like to move to a second drive on the same server. When I look into the database (properties\database locations) I cannot see the second drive, only the drive that SQL is installed on. The second drive is formatted and data is on it already but I cannot see it when I use the browse button from the above location. How do I see this second drive? Thanks in advance for any help on this
LVerify that the account that SQL Server starts under has full control of
the root of the drive. If the local system account is being used then make
sure the SYSTEM acount ahs full control.
Rand
This posting is provided "as is" with no warranties and confers no rights.

cannot see second drive??

I am running an SQL database on a win2000 server with SQL 2000 and all updated service packs. I have a database that I would like to move to a second drive on the same server. When I look into the database (properties\database locations) I cannot see the
second drive, only the drive that SQL is installed on. The second drive is formatted and data is on it already but I cannot see it when I use the browse button from the above location. How do I see this second drive? Thanks in advance for any help on this
Verify that the account that SQL Server starts under has full control of
the root of the drive. If the local system account is being used then make
sure the SYSTEM acount ahs full control.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Cannot see network drive when doing restore from disk

Hello, I recently had the PC replaced where I ran SQL Server 2005.

On the old PC I was able to backup and restore DB on a network drive L: w/o any trouble. On the new PC I reinstalled SQL Server making sure that all the settings are exactly as before. However, when I tried to restore the database, I go to "From device" -> Add file, but I do not see L: drive on the list anymore.

However, I seem to have an access to the network in general, as I can open and run sql queries that are stored on the same network drive.

I am spending the whole day comparing 2 machine setting by setting, and cannot find anything different except that the old system was running Win2000, and new one is WinXP, but I doubt that it has anything to do with it.

I also did not see any similar problem reported elsewhere.

Does anyone have any idea what to look for?

Make sure you have the drive mapped correctly on your system.

you may need to copy and paste the UNC location.

I'm not sure how it works on a local machine, but you may want to make sure the login running the SQL service has access to that network drive as well.

It would probably work better for you to just copy a backup file down from that drive to a local drive and restore from there.