DataSet Problems

Hi,
We have noticed a problem with following:
1. creating a new report
2. adding a DataSet which pulls from a shared data source and displays
information correctly
3. choosing 'Save' and not pulling the fields into the layout form
When we open the report again the dataset is there but all references to the
table we selected are gone.
Is this supposed to happen? We have tried this on 2 separate installations,
one with SP2 and one without.
Any suggestions?Sometimes RS does not recognize that anything has changed in the data tab
and does not save. Just go to the layout tab and click on save all and you
will be good to go.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"KDogg" <KDogg@.discussions.microsoft.com> wrote in message
news:B3D6B39F-12D0-4F95-A998-1CF4A83B231F@.microsoft.com...
> Hi,
> We have noticed a problem with following:
> 1. creating a new report
> 2. adding a DataSet which pulls from a shared data source and displays
> information correctly
> 3. choosing 'Save' and not pulling the fields into the layout form
> When we open the report again the dataset is there but all references to
> the
> table we selected are gone.
> Is this supposed to happen? We have tried this on 2 separate
> installations,
> one with SP2 and one without.
> Any suggestions?|||Bruce - Thank you, that worked! Would this be fixed in a future release?
Although we were working on a small dataset I would hate to have lost
development time on a larger query?!
"Bruce L-C [MVP]" wrote:
> Sometimes RS does not recognize that anything has changed in the data tab
> and does not save. Just go to the layout tab and click on save all and you
> will be good to go.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "KDogg" <KDogg@.discussions.microsoft.com> wrote in message
> news:B3D6B39F-12D0-4F95-A998-1CF4A83B231F@.microsoft.com...
> > Hi,
> > We have noticed a problem with following:
> > 1. creating a new report
> > 2. adding a DataSet which pulls from a shared data source and displays
> > information correctly
> > 3. choosing 'Save' and not pulling the fields into the layout form
> > When we open the report again the dataset is there but all references to
> > the
> > table we selected are gone.
> > Is this supposed to happen? We have tried this on 2 separate
> > installations,
> > one with SP2 and one without.
> >
> > Any suggestions?
>
>|||I have no idea. I have lost work so I do this compulsively now. I'll
probably keep doing it when the bug no longer exists.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"KDogg" <KDogg@.discussions.microsoft.com> wrote in message
news:DC256683-1D12-4C55-B578-8A4440F1B41E@.microsoft.com...
> Bruce - Thank you, that worked! Would this be fixed in a future release?
> Although we were working on a small dataset I would hate to have lost
> development time on a larger query?!
> "Bruce L-C [MVP]" wrote:
>> Sometimes RS does not recognize that anything has changed in the data tab
>> and does not save. Just go to the layout tab and click on save all and
>> you
>> will be good to go.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "KDogg" <KDogg@.discussions.microsoft.com> wrote in message
>> news:B3D6B39F-12D0-4F95-A998-1CF4A83B231F@.microsoft.com...
>> > Hi,
>> > We have noticed a problem with following:
>> > 1. creating a new report
>> > 2. adding a DataSet which pulls from a shared data source and displays
>> > information correctly
>> > 3. choosing 'Save' and not pulling the fields into the layout form
>> > When we open the report again the dataset is there but all references
>> > to
>> > the
>> > table we selected are gone.
>> > Is this supposed to happen? We have tried this on 2 separate
>> > installations,
>> > one with SP2 and one without.
>> >
>> > Any suggestions?
>>

Databases on different storage

I am newbie in SQL server and have one, maybe dumb question.
I have SQL2000 cluster on Windows 2003 with shared storage on SAN.
Cluster operates with one database only.
I need to temporary attach second database to SQL server, but problem is
that I do not have enought free space on shared storage to place both
databases. It is possible to attach another database in cluster
environment from local one node drive ? No fail-over needed. Problem is
that SQL server in cluster see only shared drives. It should look like
one database in cluster environment and one in not.
Maybe with two instances or virtual servers ?
Thanx.
Short answer is no.
Longer explanation is that in a cluster, all SQL data files must be on a
cluster disk resource that the SQL server is dependant on. YOu cannot use
local storage in a SQL 2000 cluster implementation.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"zycha" <zycha@.NOT_FOR_SPAM.COM> wrote in message
news:OnDuY9v8EHA.2196@.TK2MSFTNGP11.phx.gbl...
> I am newbie in SQL server and have one, maybe dumb question.
> I have SQL2000 cluster on Windows 2003 with shared storage on SAN.
> Cluster operates with one database only.
> I need to temporary attach second database to SQL server, but problem is
> that I do not have enought free space on shared storage to place both
> databases. It is possible to attach another database in cluster
> environment from local one node drive ? No fail-over needed. Problem is
> that SQL server in cluster see only shared drives. It should look like
> one database in cluster environment and one in not.
> Maybe with two instances or virtual servers ?
> Thanx.
|||Hello.
It may be possible to use a mount point. I've done this with two shared physical disk resources that were in the same resource group. That is: I created a folder in a formatted partition on physical disk 1 (let's call it "I:\NDF") and mounted a formatted partition from physical disk 2 on I:\NDF.
I was able to create SQL server data files on the mounted volume, even though the physical disk resource (2) was not in the SQL server resource dependancy list. Apparently SQL server doesn't know that the filesystem has a mount point, but why would it care?
Now, I'm not sure if it will work with a "local" disk, but you may try if you are feeling adventurous. Also, this was on Win2KAS, not 2.003K
Interestingly, and despite warnings against doing this (warnings which I did not read until after it had been operational in a production environment for months), the SQL server worked fine and even went through failovers without a hitch.
It will definitely not survive a failover if you use a local disk, however.
Anyway, I would not normally "suggest" doing this, because it is not supported, but it may be a viable option if you just need a few rows out of a table somewhere.
Goog Luck
jg|||Geoff N. Hiten wrote:
> Short answer is no.
> Longer explanation is that in a cluster, all SQL data files must be on a
> cluster disk resource that the SQL server is dependant on. YOu cannot use
> local storage in a SQL 2000 cluster implementation.
>
thanx