Showing posts with label named. Show all posts
Showing posts with label named. Show all posts

Thursday, March 22, 2012

bug?: two shared data sources, one update effects the other

Is this a bug? I have two shared data sources (one points to a production
server, the other points to a development server). One is named MyDB.rdl, the
other is named MyDBDev.rdl. Both of these are SQL Server data sources, and
they use a specific username and password.
I'm using Visual Studio 2003 as my development environment.
Here's the bug. If I change the username or password for one of the data
sources, it updates the other data sources as well. If I change the username
on the MyDB.rdl datasource from Fred to Jill, the MyDBDev.rdl datasource is
changed as well!!
Is this a known bug, or am I doing something wrong? Is there a workaround?
Thanks,
MarcShared data source file would have extention .rds
Could you please provide more details?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"mhf" <mhf@.discussions.microsoft.com> wrote in message
news:2CABBB0A-9C90-48F5-A94B-9A1E1A0DE9E7@.microsoft.com...
> Is this a bug? I have two shared data sources (one points to a production
> server, the other points to a development server). One is named MyDB.rdl,
> the
> other is named MyDBDev.rdl. Both of these are SQL Server data sources, and
> they use a specific username and password.
> I'm using Visual Studio 2003 as my development environment.
> Here's the bug. If I change the username or password for one of the data
> sources, it updates the other data sources as well. If I change the
> username
> on the MyDB.rdl datasource from Fred to Jill, the MyDBDev.rdl datasource
> is
> changed as well!!
> Is this a known bug, or am I doing something wrong? Is there a workaround?
> Thanks,
> Marc|||Lev,
Thanks for the reply. Yes, I mistyped there, I meant to day .rds files. The
two shared data source files have an extension of .rds and when I change one
(in Visual Studio) it modifies both of them. The SQL login name and passwords
are not stored in the .rds file, so I don't see the actual change persisted
there. I'm not sure where the changes are actually stored.
"Lev Semenets [MSFT]" wrote:
> Shared data source file would have extention .rds
> Could you please provide more details?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "mhf" <mhf@.discussions.microsoft.com> wrote in message
> news:2CABBB0A-9C90-48F5-A94B-9A1E1A0DE9E7@.microsoft.com...
> > Is this a bug? I have two shared data sources (one points to a production
> > server, the other points to a development server). One is named MyDB.rdl,
> > the
> > other is named MyDBDev.rdl. Both of these are SQL Server data sources, and
> > they use a specific username and password.
> >
> > I'm using Visual Studio 2003 as my development environment.
> >
> > Here's the bug. If I change the username or password for one of the data
> > sources, it updates the other data sources as well. If I change the
> > username
> > on the MyDB.rdl datasource from Fred to Jill, the MyDBDev.rdl datasource
> > is
> > changed as well!!
> >
> > Is this a known bug, or am I doing something wrong? Is there a workaround?
> >
> > Thanks,
> >
> > Marc
>
>|||Would you email those .rds files to me?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"mhf" <mhf@.discussions.microsoft.com> wrote in message
news:530A9866-1EEC-4CAB-B44A-CD199B3BBD10@.microsoft.com...
> Lev,
> Thanks for the reply. Yes, I mistyped there, I meant to day .rds files.
> The
> two shared data source files have an extension of .rds and when I change
> one
> (in Visual Studio) it modifies both of them. The SQL login name and
> passwords
> are not stored in the .rds file, so I don't see the actual change
> persisted
> there. I'm not sure where the changes are actually stored.
>
> "Lev Semenets [MSFT]" wrote:
>> Shared data source file would have extention .rds
>> Could you please provide more details?
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "mhf" <mhf@.discussions.microsoft.com> wrote in message
>> news:2CABBB0A-9C90-48F5-A94B-9A1E1A0DE9E7@.microsoft.com...
>> > Is this a bug? I have two shared data sources (one points to a
>> > production
>> > server, the other points to a development server). One is named
>> > MyDB.rdl,
>> > the
>> > other is named MyDBDev.rdl. Both of these are SQL Server data sources,
>> > and
>> > they use a specific username and password.
>> >
>> > I'm using Visual Studio 2003 as my development environment.
>> >
>> > Here's the bug. If I change the username or password for one of the
>> > data
>> > sources, it updates the other data sources as well. If I change the
>> > username
>> > on the MyDB.rdl datasource from Fred to Jill, the MyDBDev.rdl
>> > datasource
>> > is
>> > changed as well!!
>> >
>> > Is this a known bug, or am I doing something wrong? Is there a
>> > workaround?
>> >
>> > Thanks,
>> >
>> > Marc
>>

Friday, February 10, 2012

Both versions of SQL Server on one server

Can I install SQL Server 7.0 SP2 as a Default version and
SQL Server 2000 SP3 as a named version on a WIndows 2000
SP3 server ?
We will run Connect-Care (Customer-First) Application
against SQL Server 7.0 version and Solomon 5.5 against SQL
Server 2000 version.
Anybody see any problem with this ?
Thanks for any help.
Rick,
Yep, should work fine. I have found it preferable to install SQL Server
7.0 first, then install SQL 2000 as a named instance. Remember to
configure your memory settings so that they aren't competing with each
other for RAM.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Rick wrote:
> Can I install SQL Server 7.0 SP2 as a Default version and
> SQL Server 2000 SP3 as a named version on a WIndows 2000
> SP3 server ?
> We will run Connect-Care (Customer-First) Application
> against SQL Server 7.0 version and Solomon 5.5 against SQL
> Server 2000 version.
> Anybody see any problem with this ?
> Thanks for any help.
|||I hope that installing service packs should not be a
problem....

>--Original Message--
>Rick,
>Yep, should work fine. I have found it preferable to
install SQL Server
>7.0 first, then install SQL 2000 as a named instance.
Remember to
>configure your memory settings so that they aren't
competing with each[vbcol=seagreen]
>other for RAM.
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602m.html
>
>Rick wrote:
and[vbcol=seagreen]
2000[vbcol=seagreen]
SQL
>.
>
|||Rick,
No problem! You can even have two instances of SQL Server 2000 running
at different service pack levels. (Not that you'd want to though).
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Rick wrote:[vbcol=seagreen]
> I hope that installing service packs should not be a
> problem....
>
>
> install SQL Server
>
> Remember to
>
> competing with each
>
> and
>
> 2000
>
> SQL

Both versions of SQL Server on one server

Can I install SQL Server 7.0 SP2 as a Default version and
SQL Server 2000 SP3 as a named version on a WIndows 2000
SP3 server '
We will run Connect-Care (Customer-First) Application
against SQL Server 7.0 version and Solomon 5.5 against SQL
Server 2000 version.
Anybody see any problem with this '
Thanks for any help.Check out
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/instsql/in_runsetup_0svo.asp
Peter
"Government does not solve problems; it subsidizes them."
Ronald Reagan
>--Original Message--
>Can I install SQL Server 7.0 SP2 as a Default version and
>SQL Server 2000 SP3 as a named version on a WIndows 2000
>SP3 server '
>We will run Connect-Care (Customer-First) Application
>against SQL Server 7.0 version and Solomon 5.5 against
SQL
>Server 2000 version.
>Anybody see any problem with this '
>Thanks for any help.
>.
>|||Rick,
Yep, should work fine. I have found it preferable to install SQL Server
7.0 first, then install SQL 2000 as a named instance. Remember to
configure your memory settings so that they aren't competing with each
other for RAM.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Rick wrote:
> Can I install SQL Server 7.0 SP2 as a Default version and
> SQL Server 2000 SP3 as a named version on a WIndows 2000
> SP3 server '
> We will run Connect-Care (Customer-First) Application
> against SQL Server 7.0 version and Solomon 5.5 against SQL
> Server 2000 version.
> Anybody see any problem with this '
> Thanks for any help.|||I hope that installing service packs should not be a
problem....
>--Original Message--
>Rick,
>Yep, should work fine. I have found it preferable to
install SQL Server
>7.0 first, then install SQL 2000 as a named instance.
Remember to
>configure your memory settings so that they aren't
competing with each
>other for RAM.
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602m.html
>
>Rick wrote:
>> Can I install SQL Server 7.0 SP2 as a Default version
and
>> SQL Server 2000 SP3 as a named version on a WIndows
2000
>> SP3 server '
>> We will run Connect-Care (Customer-First) Application
>> against SQL Server 7.0 version and Solomon 5.5 against
SQL
>> Server 2000 version.
>> Anybody see any problem with this '
>> Thanks for any help.
>.
>|||Rick,
No problem! You can even have two instances of SQL Server 2000 running
at different service pack levels. (Not that you'd want to though).
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Rick wrote:
> I hope that installing service packs should not be a
> problem....
>
>>--Original Message--
>>Rick,
>>Yep, should work fine. I have found it preferable to
> install SQL Server
>>7.0 first, then install SQL 2000 as a named instance.
> Remember to
>>configure your memory settings so that they aren't
> competing with each
>>other for RAM.
>>--
>>Mark Allison, SQL Server MVP
>>http://www.markallison.co.uk
>>Looking for a SQL Server replication book?
>>http://www.nwsu.com/0974973602m.html
>>
>>Rick wrote:
>>Can I install SQL Server 7.0 SP2 as a Default version
> and
>>SQL Server 2000 SP3 as a named version on a WIndows
> 2000
>>SP3 server '
>>We will run Connect-Care (Customer-First) Application
>>against SQL Server 7.0 version and Solomon 5.5 against
> SQL
>>Server 2000 version.
>>Anybody see any problem with this '
>>Thanks for any help.
>>.