New Role Permissions

Hi,
I have installed RS in a production environment successfully. I then added a
user into the windows registry. I can access all 'tool bar' options like
'Upload Report' as an administrator on the localhost, but when I access RS by
the new role I have created I only get the almost blank 'home' page. I have
given the new role user every permission in RS via site wide configuration
settings ect., but I still don't get the upload option and other two options
on the 'tool bar'. What do Ineed to do to give the new user adminstration
wide access in RS, but not an administrator in windows.
ThanksYou need to set item-level permissions for that user.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Quinton" <Quinton@.discussions.microsoft.com> wrote in message
news:3BCBB0BF-D591-4189-9FB1-877599C85422@.microsoft.com...
> Hi,
> I have installed RS in a production environment successfully. I then added
> a
> user into the windows registry. I can access all 'tool bar' options like
> 'Upload Report' as an administrator on the localhost, but when I access RS
> by
> the new role I have created I only get the almost blank 'home' page. I
> have
> given the new role user every permission in RS via site wide configuration
> settings ect., but I still don't get the upload option and other two
> options
> on the 'tool bar'. What do Ineed to do to give the new user adminstration
> wide access in RS, but not an administrator in windows.
> Thanks|||Hi,
Thanks - but I must be a thick head, as the new user does not have any items
to set permissions on. Do you mean that as administrator I create a directory
and then set item level permissions on that for the new user?
Thnks,
Quinton
"Lev Semenets [MSFT]" wrote:
> You need to set item-level permissions for that user.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Quinton" <Quinton@.discussions.microsoft.com> wrote in message
> news:3BCBB0BF-D591-4189-9FB1-877599C85422@.microsoft.com...
> > Hi,
> > I have installed RS in a production environment successfully. I then added
> > a
> > user into the windows registry. I can access all 'tool bar' options like
> > 'Upload Report' as an administrator on the localhost, but when I access RS
> > by
> > the new role I have created I only get the almost blank 'home' page. I
> > have
> > given the new role user every permission in RS via site wide configuration
> > settings ect., but I still don't get the upload option and other two
> > options
> > on the 'tool bar'. What do Ineed to do to give the new user adminstration
> > wide access in RS, but not an administrator in windows.
> >
> > Thanks
>
>|||Yes.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Quinton" <Quinton@.discussions.microsoft.com> wrote in message
news:902431F4-EBAE-4F44-A22A-4D33A68F2893@.microsoft.com...
> Hi,
> Thanks - but I must be a thick head, as the new user does not have any
> items
> to set permissions on. Do you mean that as administrator I create a
> directory
> and then set item level permissions on that for the new user?
> Thnks,
> Quinton
> "Lev Semenets [MSFT]" wrote:
>> You need to set item-level permissions for that user.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Quinton" <Quinton@.discussions.microsoft.com> wrote in message
>> news:3BCBB0BF-D591-4189-9FB1-877599C85422@.microsoft.com...
>> > Hi,
>> > I have installed RS in a production environment successfully. I then
>> > added
>> > a
>> > user into the windows registry. I can access all 'tool bar' options
>> > like
>> > 'Upload Report' as an administrator on the localhost, but when I access
>> > RS
>> > by
>> > the new role I have created I only get the almost blank 'home' page. I
>> > have
>> > given the new role user every permission in RS via site wide
>> > configuration
>> > settings ect., but I still don't get the upload option and other two
>> > options
>> > on the 'tool bar'. What do Ineed to do to give the new user
>> > adminstration
>> > wide access in RS, but not an administrator in windows.
>> >
>> > Thanks
>>|||Thanks again Lev,
... but that didn't work, the new user that I added in the 'users' group in
windows still didn't get any tabs (content/properties) or any of the other
stuff needed to upload reports. I decided to cheat and just add my user into
the Administrators group. This worked, but, when I tried to add a data source
I get the error 'The underlying connection was closed: Could not establish
trust relationship with remote server.' I did try to create a connection with
every type of credentials.
This is my 4th installation of RS, the configurations of this installation
are:
Windows server 2003.
Reports/ReportServer are on a different drive to SQL instance.
SQL data on a different drive again.
Any ideas'
Quinton
"Lev Semenets [MSFT]" wrote:
> Yes.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Quinton" <Quinton@.discussions.microsoft.com> wrote in message
> news:902431F4-EBAE-4F44-A22A-4D33A68F2893@.microsoft.com...
> > Hi,
> >
> > Thanks - but I must be a thick head, as the new user does not have any
> > items
> > to set permissions on. Do you mean that as administrator I create a
> > directory
> > and then set item level permissions on that for the new user?
> >
> > Thnks,
> > Quinton
> >
> > "Lev Semenets [MSFT]" wrote:
> >
> >> You need to set item-level permissions for that user.
> >>
> >> --
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >> "Quinton" <Quinton@.discussions.microsoft.com> wrote in message
> >> news:3BCBB0BF-D591-4189-9FB1-877599C85422@.microsoft.com...
> >> > Hi,
> >> > I have installed RS in a production environment successfully. I then
> >> > added
> >> > a
> >> > user into the windows registry. I can access all 'tool bar' options
> >> > like
> >> > 'Upload Report' as an administrator on the localhost, but when I access
> >> > RS
> >> > by
> >> > the new role I have created I only get the almost blank 'home' page. I
> >> > have
> >> > given the new role user every permission in RS via site wide
> >> > configuration
> >> > settings ect., but I still don't get the upload option and other two
> >> > options
> >> > on the 'tool bar'. What do Ineed to do to give the new user
> >> > adminstration
> >> > wide access in RS, but not an administrator in windows.
> >> >
> >> > Thanks
> >>
> >>
> >>
>
>

New Production Server - Orphaned Users

Hi,
I have to move 5 databases from an old production server to a new production
server.
Old Production Server: Win 2K Server, SQL 2000 SP2
New Production Server:Win 2K3 Server, SQL 2000 SP4
I am creating the new server from scratch. Since I can't run SQL Server SP2
on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
I backed up system databases on Old Production server and restored them on
Staging and applied SP4 to the Staging server. Then I backed up system
databases on Staging and restored them on New Production Server since both o
f
them are now at the same Service Pack Level. I have to do it this way to
avoid applying SP4 directly to the old Production server.
Then I detached and attached the User databases on the New Production server
from Old Production server. My question is - would I still have orphaned
users? Thanks in advance.If I followed your chain correctly, you basically took your system databases
from a to b to c. Then
you take your user databases from a to c. This should mean that the logins e
xists with correct SID -
i.e., no orphaned users.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new producti
on
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server SP
2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both
of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production serv
er
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.|||Hi
http://dimantdatabasesolutions.blog...on.
html
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new
> production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server
> SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both
> of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production
> server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.

New Production Server - Orphaned Users

Hi,
I have to move 5 databases from an old production server to a new production
server.
Old Production Server: Win 2K Server, SQL 2000 SP2
New Production Server:Win 2K3 Server, SQL 2000 SP4
I am creating the new server from scratch. Since I can't run SQL Server SP2
on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
I backed up system databases on Old Production server and restored them on
Staging and applied SP4 to the Staging server. Then I backed up system
databases on Staging and restored them on New Production Server since both of
them are now at the same Service Pack Level. I have to do it this way to
avoid applying SP4 directly to the old Production server.
Then I detached and attached the User databases on the New Production server
from Old Production server. My question is - would I still have orphaned
users? Thanks in advance.
If I followed your chain correctly, you basically took your system databases from a to b to c. Then
you take your user databases from a to c. This should mean that the logins exists with correct SID -
i.e., no orphaned users.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.
|||Hi
http://dimantdatabasesolutions.blogspot.com/2007/04/sql-or-windows-authentication.html
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new
> production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server
> SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both
> of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production
> server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.

New Production Server - Orphaned Users

Hi,
I have to move 5 databases from an old production server to a new production
server.
Old Production Server: Win 2K Server, SQL 2000 SP2
New Production Server:Win 2K3 Server, SQL 2000 SP4
I am creating the new server from scratch. Since I can't run SQL Server SP2
on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
I backed up system databases on Old Production server and restored them on
Staging and applied SP4 to the Staging server. Then I backed up system
databases on Staging and restored them on New Production Server since both of
them are now at the same Service Pack Level. I have to do it this way to
avoid applying SP4 directly to the old Production server.
Then I detached and attached the User databases on the New Production server
from Old Production server. My question is - would I still have orphaned
users? Thanks in advance.If I followed your chain correctly, you basically took your system databases from a to b to c. Then
you take your user databases from a to c. This should mean that the logins exists with correct SID -
i.e., no orphaned users.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.|||Hi
http://dimantdatabasesolutions.blogspot.com/2007/04/sql-or-windows-authentication.html
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new
> production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server
> SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both
> of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production
> server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.

New Instance

We have a production server on SQL 2000. We have one default instance on it. Is it possible for us to add a new instance at this point now or is that someting we can do only in the initial stage when we are installing for the first time.
Thanks for your help in advance.You can re-run the install to create a new named instance. Note that everything that I have heard says that this should not be done on production servers. It is primarily intended (as I understand) for development and testing environments.

Regards,

Hugh Scott

Originally posted by anu
We have a production server on SQL 2000. We have one default instance on it. Is it possible for us to add a new instance at this point now or is that someting we can do only in the initial stage when we are installing for the first time.

Thanks for your help in advance.|||Thank you!!

New Datawarehouse

What is the best way to set up a datawarehouse? Do I use replication or dts
packages or what? What I need to do is archive production data every two
weeks to this datawarehouse. Then I will need to be able to query the
archive data. What is the best way to do this? And how do I go about doing
it?
Thanks in advance for the help.
Dave
> What is the best way to set up a datawarehouse? Do I use replication or
dts
> packages or what? What I need to do is archive production data every two
> weeks to this datawarehouse.
DTS seems more appropriate in this scenario.

> Then I will need to be able to query the
> archive data. What is the best way to do this? And how do I go about doing
> it?
DW is usually 1st step - next step are OLAP cubes. Do please read more on
OLAP in Books OnLine, I guess this is what you need.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com

New datawarehouse

What is the best way to set up a datwarehouse? Do I use replication or dts
packages or what? What I need to do is archive production data every two
weeks to this datawarehouse. Then I will need to be able to query the
archive data. What is the best way to do this? And how do I go about doing
it?
Thanks in advance for the help.
DaveDave,
Surprising that you didn't seem to spark a lively conversation on this
question.
If you really need a DW then the right answer is to take a long term
approach and design an enterprise level data warehouse where the
organization can go to analyze data from a single perspective that has been
defined, researched, tested, and authorized by the business as the single
point of truth. Sounds like a lot of work? Well perhaps what you are
really needing is a reporting operational data store, ODS. This is a common
starting point of a DW. There are many reasons for needing a reporting ODS.
Adhoc queries are contending with transactional inserts/updates
The OLTP is slowly down due to volume of data and the OLTP doesn't need the
old data
Queries are too slow against the OLTP normalized schema
Queries are to hard for users to create against the complex OLTP schema.
An assumption here is that archive means copy and remove. If you are
intending to remove the data from the OLTP then replication is out as a
solution.
Based on the limited information provided and not knowing budget or skill
levels, I would recommend:
Buying a separate SQL server
Defining an easier/faster schema for the data your users need (Star or just
denormalized and use surrogate keys)
Depending on skill level, budget, and transformation complexity use TSQL,
DTS, or a third party ETL tool to extract, transform, load, and purge the
incremental data
Be careful of updates and deletes as the source system may not clearly
indicate them in the schema
The usual system development life cycle and operational techniques and
should be applied.
Good luck,
Danny
"Dave Mortenson" <dmortenson@.ident.com> wrote in message
news:OXrlm7ByEHA.1396@.tk2msftngp13.phx.gbl...
> What is the best way to set up a datwarehouse? Do I use replication or dts
> packages or what? What I need to do is archive production data every two
> weeks to this datawarehouse. Then I will need to be able to query the
> archive data. What is the best way to do this? And how do I go about doing
> it?
> Thanks in advance for the help.
>
> Dave
>

New Datawarehouse

What is the best way to set up a datawarehouse? Do I use replication or dts
packages or what? What I need to do is archive production data every two
weeks to this datawarehouse. Then I will need to be able to query the
archive data. What is the best way to do this? And how do I go about doing
it?
Thanks in advance for the help.
Dave> What is the best way to set up a datawarehouse? Do I use replication or
dts
> packages or what? What I need to do is archive production data every two
> weeks to this datawarehouse.
DTS seems more appropriate in this scenario.

> Then I will need to be able to query the
> archive data. What is the best way to do this? And how do I go about doing
> it?
DW is usually 1st step - next step are OLAP cubes. Do please read more on
OLAP in Books OnLine, I guess this is what you need.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com

New datawarehouse

What is the best way to set up a datwarehouse? Do I use replication or dts
packages or what? What I need to do is archive production data every two
weeks to this datawarehouse. Then I will need to be able to query the
archive data. What is the best way to do this? And how do I go about doing
it?
Thanks in advance for the help.
Dave
Dave,
Surprising that you didn't seem to spark a lively conversation on this
question.
If you really need a DW then the right answer is to take a long term
approach and design an enterprise level data warehouse where the
organization can go to analyze data from a single perspective that has been
defined, researched, tested, and authorized by the business as the single
point of truth. Sounds like a lot of work? Well perhaps what you are
really needing is a reporting operational data store, ODS. This is a common
starting point of a DW. There are many reasons for needing a reporting ODS.
Adhoc queries are contending with transactional inserts/updates
The OLTP is slowly down due to volume of data and the OLTP doesn't need the
old data
Queries are too slow against the OLTP normalized schema
Queries are to hard for users to create against the complex OLTP schema.
An assumption here is that archive means copy and remove. If you are
intending to remove the data from the OLTP then replication is out as a
solution.
Based on the limited information provided and not knowing budget or skill
levels, I would recommend:
Buying a separate SQL server
Defining an easier/faster schema for the data your users need (Star or just
denormalized and use surrogate keys)
Depending on skill level, budget, and transformation complexity use TSQL,
DTS, or a third party ETL tool to extract, transform, load, and purge the
incremental data
Be careful of updates and deletes as the source system may not clearly
indicate them in the schema
The usual system development life cycle and operational techniques and
should be applied.
Good luck,
Danny
"Dave Mortenson" <dmortenson@.ident.com> wrote in message
news:OXrlm7ByEHA.1396@.tk2msftngp13.phx.gbl...
> What is the best way to set up a datwarehouse? Do I use replication or dts
> packages or what? What I need to do is archive production data every two
> weeks to this datawarehouse. Then I will need to be able to query the
> archive data. What is the best way to do this? And how do I go about doing
> it?
> Thanks in advance for the help.
>
> Dave
>

New Datawarehouse

What is the best way to set up a datawarehouse? Do I use replication or dts
packages or what? What I need to do is archive production data every two
weeks to this datawarehouse. Then I will need to be able to query the
archive data. What is the best way to do this? And how do I go about doing
it?
Thanks in advance for the help.
Dave> What is the best way to set up a datawarehouse? Do I use replication or
dts
> packages or what? What I need to do is archive production data every two
> weeks to this datawarehouse.
DTS seems more appropriate in this scenario.
> Then I will need to be able to query the
> archive data. What is the best way to do this? And how do I go about doing
> it?
DW is usually 1st step - next step are OLAP cubes. Do please read more on
OLAP in Books OnLine, I guess this is what you need.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com

New Database Name not visible while DSN setup

Hi,
I have taken backup(connectdb.bak) from production and
created the database in test server. For that I used
following procedure,
In sql query analyzer, I executed the following two steps
consecutively.
1. RESTORE FILELISTONLY FROM DISK = 'c:\Mssql7
\Backup\connectdb.bak'
2. RESTORE DATABASE newdb FROM DISK = 'c:\Mssql7
\Backup\connectdb.bak' WITH
MOVE 'connectdb_Data' TO 'c:\test\newdb.mdf',
MOVE 'connectdb_log' TO 'c:\test\newdb_log.ldf'
This created a new database "newdb" in test server from
the back up file connectdb.bak.
I want to connect to this database.
Now while going through SQL server DSN configuration,
there comes an option where we get the following option,
"change the default database to"
While clicking in this box,we get a drop down listing of
all the databases. Here I am stuck. Ideally the "newdb"
database which I have created from connectdb.bak file,
should be visible here so that I can choose to connect to
it. But it's not visible here and unless it's visible here
I can't do anything. The otherdatabases which were present
in the test server since beginning are visible accept this
one.
Please help. It's urgent
regards,
Vishal
Check to see if the login/user for whom you are setting up
the DSN is a user in the database that has been restored. It
sounds like they users could have been orphaned.
You can find a good article on orphaned users and
troubleshooting techniques, links to KB articles at:
http://vyaskn.tripod.com/troubleshoo...phan_users.htm
-Sue
On Thu, 1 Apr 2004 08:40:14 -0800, "vishal kumar"
<anonymous@.discussions.microsoft.com> wrote:

>Hi,
>I have taken backup(connectdb.bak) from production and
>created the database in test server. For that I used
>following procedure,
>In sql query analyzer, I executed the following two steps
>consecutively.
>1. RESTORE FILELISTONLY FROM DISK = 'c:\Mssql7
>\Backup\connectdb.bak'
>2. RESTORE DATABASE newdb FROM DISK = 'c:\Mssql7
>\Backup\connectdb.bak' WITH
>MOVE 'connectdb_Data' TO 'c:\test\newdb.mdf',
>MOVE 'connectdb_log' TO 'c:\test\newdb_log.ldf'
>This created a new database "newdb" in test server from
>the back up file connectdb.bak.
>I want to connect to this database.
>Now while going through SQL server DSN configuration,
>there comes an option where we get the following option,
>"change the default database to"
>While clicking in this box,we get a drop down listing of
>all the databases. Here I am stuck. Ideally the "newdb"
>database which I have created from connectdb.bak file,
>should be visible here so that I can choose to connect to
>it. But it's not visible here and unless it's visible here
>I can't do anything. The otherdatabases which were present
>in the test server since beginning are visible accept this
>one.
>Please help. It's urgent
>regards,
>Vishal
>
|||If this is a new serer then the user exists in the
database but not in master. You first need to create the
login. Then synch up the users with sp_change_users_login
>--Original Message--
>Check to see if the login/user for whom you are setting up
>the DSN is a user in the database that has been restored.
It
>sounds like they users could have been orphaned.
>You can find a good article on orphaned users and
>troubleshooting techniques, links to KB articles at:
>http://vyaskn.tripod.com/troubleshoo...phan_users.htm
>-Sue
>On Thu, 1 Apr 2004 08:40:14 -0800, "vishal kumar"
><anonymous@.discussions.microsoft.com> wrote:
steps
to
here
present
this
>.
>

New Database Name not visible while DSN setup

Hi,
I have taken backup(connectdb.bak) from production and
created the database in test server. For that I used
following procedure,
In sql query analyzer, I executed the following two steps
consecutively.
1. RESTORE FILELISTONLY FROM DISK = 'c:\Mssql7
\Backup\connectdb.bak'
2. RESTORE DATABASE newdb FROM DISK = 'c:\Mssql7
\Backup\connectdb.bak' WITH
MOVE 'connectdb_Data' TO 'c:\test\newdb.mdf',
MOVE 'connectdb_log' TO 'c:\test\newdb_log.ldf'
This created a new database "newdb" in test server from
the back up file connectdb.bak.
I want to connect to this database.
Now while going through SQL server DSN configuration,
there comes an option where we get the following option,
"change the default database to"
While clicking in this box,we get a drop down listing of
all the databases. Here I am stuck. Ideally the "newdb"
database which I have created from connectdb.bak file,
should be visible here so that I can choose to connect to
it. But it's not visible here and unless it's visible here
I can't do anything. The otherdatabases which were present
in the test server since beginning are visible accept this
one.
Please help. It's urgent
regards,
VishalCheck to see if the login/user for whom you are setting up
the DSN is a user in the database that has been restored. It
sounds like they users could have been orphaned.
You can find a good article on orphaned users and
troubleshooting techniques, links to KB articles at:
http://vyaskn.tripod.com/troublesho...rphan_users.htm
-Sue
On Thu, 1 Apr 2004 08:40:14 -0800, "vishal kumar"
<anonymous@.discussions.microsoft.com> wrote:

>Hi,
>I have taken backup(connectdb.bak) from production and
>created the database in test server. For that I used
>following procedure,
>In sql query analyzer, I executed the following two steps
>consecutively.
>1. RESTORE FILELISTONLY FROM DISK = 'c:\Mssql7
>\Backup\connectdb.bak'
>2. RESTORE DATABASE newdb FROM DISK = 'c:\Mssql7
>\Backup\connectdb.bak' WITH
>MOVE 'connectdb_Data' TO 'c:\test\newdb.mdf',
>MOVE 'connectdb_log' TO 'c:\test\newdb_log.ldf'
>This created a new database "newdb" in test server from
>the back up file connectdb.bak.
>I want to connect to this database.
>Now while going through SQL server DSN configuration,
>there comes an option where we get the following option,
>"change the default database to"
>While clicking in this box,we get a drop down listing of
>all the databases. Here I am stuck. Ideally the "newdb"
>database which I have created from connectdb.bak file,
>should be visible here so that I can choose to connect to
>it. But it's not visible here and unless it's visible here
>I can't do anything. The otherdatabases which were present
>in the test server since beginning are visible accept this
>one.
>Please help. It's urgent
>regards,
>Vishal
>|||If this is a new serer then the user exists in the
database but not in master. You first need to create the
login. Then synch up the users with sp_change_users_login
>--Original Message--
>Check to see if the login/user for whom you are setting up
>the DSN is a user in the database that has been restored.
It
>sounds like they users could have been orphaned.
>You can find a good article on orphaned users and
>troubleshooting techniques, links to KB articles at:
>http://vyaskn.tripod.com/troublesho...rphan_users.htm
>-Sue
>On Thu, 1 Apr 2004 08:40:14 -0800, "vishal kumar"
><anonymous@.discussions.microsoft.com> wrote:
>
steps
to
here
present
this
>.
>