remotely attached DB ends up readonly .. why oh why oh why ..

I have what seems like a commonish problem.
I have copied my database (mdf and logfile) to a remote XP desktop machine
... when using SQL server managment express tool when I try to attach the
DB it ends up readonly.
The file permissions are not set to read only (a problem I have read)
And I've done this shrink-detach-transfer-attach with various versions of
this database at least 20 times in the last week.
But not now it would seem.
The strange thing is that if I drop this database into the sql server default
'data' directory it works fine.
This doesnt explain why the second database that sits in the original 'destination'
directory attaches just fine.
I am utterly confused - traps for new players I guess.
---
[Sam Samson] - There is no greater folly than fixed price quoting.Sam
On the source machine, did you issue sp_detach the database? Take a look at
ALTER DATABASE... SET READ_WRITE option if I remember well
"Sam Samson" <nospamsam@.nospam.com.au> wrote in message
news:ece03a7894c38c9b916d29dee90@.news.microsoft.com...
>I have what seems like a commonish problem.
> I have copied my database (mdf and logfile) to a remote XP desktop machine
> ... when using SQL server managment express tool when I try to attach the
> DB it ends up readonly.
> The file permissions are not set to read only (a problem I have read) And
> I've done this shrink-detach-transfer-attach with various versions of this
> database at least 20 times in the last week.
> But not now it would seem.
> The strange thing is that if I drop this database into the sql server
> default 'data' directory it works fine.
> This doesnt explain why the second database that sits in the original
> 'destination' directory attaches just fine.
> I am utterly confused - traps for new players I guess.
> ---
> [Sam Samson] - There is no greater folly than fixed price quoting.
>
>

Remote login to MSDE 2000 (Desktop)

My question is, is it possible to connect to an SQL database using the MSDE 2000 SP3a edition over the internet? And if so, how do I set it up? Thank you in advance.::My question is, is it possible to connect to an SQL database using the MSDE 2000 SP3a
::edition over the internet?

Yes.

::And if so, how do I set it up?

You mean after making sure you can connect to the server from the internet, having a firewall in place etc.?

Not at all. There is nothing left to configure after this.

EVERY MSDE installation automatically accepts connections from the network, and guess what - the internet is just a network.

Remote Desktop: Losing credentials ...

Hi,

I've experienced a problem (bug?) when deploying reports to the report server. My users kept complaining about losing authentication to reports when I deploy a new report. I found the problem but don't understand why this is happening. My collegue developped the earliest reports and loggs in with a different user on Remote Desktop to develop the reports. When the report is deployed, the datasources are deployed also.

Now when I log in on Remote Desktop with another user then my collegue and open the same report project, and check out the datasources, the credentials are gone ... ?!? So when I deploy a report the datasource with the empty credentials are deployed too, wich causes all the authentication problems.

My Question: How comes I can't see the user credentials my collegue filled in? When I open the report project the credentials are gone. I log out, my collegue loggs in, and the credentials are back

I suppose this has something to do with Remote Desktop and the users connecting to it?

Thanks in advance!

Nobody?|||I believe Visual Studio stores the data source credentials in a user specific data file (<projectname>.rptproj.user). This is by design, so that one developer cannot "borrow" another developer's credentials. However, if you are using shared data sources, there is a simple workaround. Make sure that the OverwriteDataSources property in the Project Properties is set to FALSE. This way, shared data sources are only deployed if they don't already exist. On the first deployment, you may have the update the data source on the server, but subsequent report deployments will not overwrite it.|||

Hi jwelch,

Thanks for the explanation. Your solution will probably prevent anything like this happening ever again.

Respect! ;-)

|||Can you mark the response as an answer? It helps others who encounter the same problems find solutions more easily.

Remote Desktop

I have msde 2000 installed by one of my applications and
every time i access my pc via Remote Desktop, the msde
initializes? When I'm at my pc locally, it is not an
issue.
What is Remote Desktop doing that is causing this
behaviour and how can i get it to stop?
thanks in advance
jo
Hi Joann,
If you have installed SP3 on MSDE, the network access is
disabled by default (libraries are disabled by default) Windows XP SP2
firewall also blocks any MSSQL services from listening on the network.
It is mentioned as DISABLENETWORKPROTOCOLS switch in the readme
file. You have to enable net libraries.
See these articles:
http://support.microsoft.com/default...b;en-us;841249
http://support.microsoft.com/default...b;en-us;814130
Magy
"Joann" wrote:

> I have msde 2000 installed by one of my applications and
> every time i access my pc via Remote Desktop, the msde
> initializes? When I'm at my pc locally, it is not an
> issue.
> What is Remote Desktop doing that is causing this
> behaviour and how can i get it to stop?
> thanks in advance
> jo
>
>

Remote Desktop

Hi,
When I go to restore db in SQL 2000 using 'Remote Desktop' I can only see local drives and not mapped drives. When I go physically to the computer I can see the local and mapped drives when trying to restore db. This leads me to belive it is a 'Remote D
esktop' issue.
Any suggestions?
Thanks in advance
stonehead,
Why not just use Enterprise Manager, or even better, Query Analyzer from
your client workstation to do the restore? Do you need to use Remote
Desktop? Do you have a roaming profile on the domain? If you map the drives
using Remote Desktop, log off and then log on again, do they still
disappear?
When restoring over the network, you should always use a UNC name anyway, as
this reduces exposure to bugs. Mapped drive letters can change, or even
disappear. Try using a UNC name, i.e.
\\servername\share\folder\file
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"stonehead" <anonymous@.discussions.microsoft.com> wrote in message
news:9261C67A-2A59-452B-9129-FEF7DADC6EC9@.microsoft.com...
> Hi,
> When I go to restore db in SQL 2000 using 'Remote Desktop' I can only see
local drives and not mapped drives. When I go physically to the computer I
can see the local and mapped drives when trying to restore db. This leads
me to belive it is a 'Remote Desktop' issue.
> Any suggestions?
> Thanks in advance

Remote Desktop

Hi,
When I go to restore db in SQL 2000 using 'Remote Desktop' I can only see lo
cal drives and not mapped drives. When I go physically to the computer I ca
n see the local and mapped drives when trying to restore db. This leads me
to belive it is a 'Remote D
esktop' issue.
Any suggestions?
Thanks in advancestonehead,
Why not just use Enterprise Manager, or even better, Query Analyzer from
your client workstation to do the restore? Do you need to use Remote
Desktop? Do you have a roaming profile on the domain? If you map the drives
using Remote Desktop, log off and then log on again, do they still
disappear?
When restoring over the network, you should always use a UNC name anyway, as
this reduces exposure to bugs. Mapped drive letters can change, or even
disappear. Try using a UNC name, i.e.
\\servername\share\folder\file
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"stonehead" <anonymous@.discussions.microsoft.com> wrote in message
news:9261C67A-2A59-452B-9129-FEF7DADC6EC9@.microsoft.com...
> Hi,
> When I go to restore db in SQL 2000 using 'Remote Desktop' I can only see
local drives and not mapped drives. When I go physically to the computer I
can see the local and mapped drives when trying to restore db. This leads
me to belive it is a 'Remote Desktop' issue.
> Any suggestions?
> Thanks in advance

Remote Desktop

Hi
When I go to restore db in SQL 2000 using 'Remote Desktop' I can only see local drives and not mapped drives. When I go physically to the computer I can see the local and mapped drives when trying to restore db. This leads me to belive it is a 'Remote Desktop' issue
Any suggestions
Thanks in advancestonehead,
Why not just use Enterprise Manager, or even better, Query Analyzer from
your client workstation to do the restore? Do you need to use Remote
Desktop? Do you have a roaming profile on the domain? If you map the drives
using Remote Desktop, log off and then log on again, do they still
disappear?
When restoring over the network, you should always use a UNC name anyway, as
this reduces exposure to bugs. Mapped drive letters can change, or even
disappear. Try using a UNC name, i.e.
\\servername\share\folder\file
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"stonehead" <anonymous@.discussions.microsoft.com> wrote in message
news:9261C67A-2A59-452B-9129-FEF7DADC6EC9@.microsoft.com...
> Hi,
> When I go to restore db in SQL 2000 using 'Remote Desktop' I can only see
local drives and not mapped drives. When I go physically to the computer I
can see the local and mapped drives when trying to restore db. This leads
me to belive it is a 'Remote Desktop' issue.
> Any suggestions?
> Thanks in advance