Confusion over datasets, lists, first(

I'm trying to build a report in VS2005. The main dataset (DSCases) for
the report is just "Select * from LawCases where Docket = ?"
It should only return one case. So I dragged a few fields onto the
report body, and VS kept making the expression First(Fields!...)
instead of just Fields!. I don't know why but I don't know much about
SSRS so that isn't too surprising.
I used a list with that dataset as the DataSetName and then I could
get rid of the Firsts. Fine.
However I need some other tables mixed in, so I created another
dataset DSAttorneys (Select * from LawCasesAttorney where Docket = ?),
which should get me the various attorneys who worked on the case. Then
I added a list inside the main list, set the DataSetName to the
DSAttorneys, and VS insists on using First again. And, indeed, I do
get the first attorney, but I need them all. It won't compile without
the First though.
I hoped that the inside list would understand that it would repeat
those fields for each record. I looked at filters and grouping but
can't get it to work as I expect.
Do I need to use subreports instead of a list?As you saw you can't just put a field on the layout surface. It has to be
bound to a list or a table. If you know there is only going to be one record
returned then drag and drop the fields and use the First aggregate. Then
drag the list over (or the table object, whichever works best). Otherwise
use a subreport.
What is happening is RS does not know it is a single row, how can it. So for
a list within a list it would need to be joining the data (like a
master-detail). For instance a list of orders and a list of items for each
order. When you do a 1 to many or a 1 to 1 you need to use subreports.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"dgk" <dgk@.somewhere.com> wrote in message
news:0i3pr39o6so20jdih2k8p1lrbpsep6mt37@.4ax.com...
> I'm trying to build a report in VS2005. The main dataset (DSCases) for
> the report is just "Select * from LawCases where Docket = ?"
> It should only return one case. So I dragged a few fields onto the
> report body, and VS kept making the expression First(Fields!...)
> instead of just Fields!. I don't know why but I don't know much about
> SSRS so that isn't too surprising.
> I used a list with that dataset as the DataSetName and then I could
> get rid of the Firsts. Fine.
> However I need some other tables mixed in, so I created another
> dataset DSAttorneys (Select * from LawCasesAttorney where Docket = ?),
> which should get me the various attorneys who worked on the case. Then
> I added a list inside the main list, set the DataSetName to the
> DSAttorneys, and VS insists on using First again. And, indeed, I do
> get the first attorney, but I need them all. It won't compile without
> the First though.
> I hoped that the inside list would understand that it would repeat
> those fields for each record. I looked at filters and grouping but
> can't get it to work as I expect.
> Do I need to use subreports instead of a list?|||On Wed, 20 Feb 2008 15:06:49 -0600, "Bruce L-C [MVP]"
<bruce_lcNOSPAM@.hotmail.com> wrote:
>As you saw you can't just put a field on the layout surface. It has to be
>bound to a list or a table. If you know there is only going to be one record
>returned then drag and drop the fields and use the First aggregate. Then
>drag the list over (or the table object, whichever works best). Otherwise
>use a subreport.
>What is happening is RS does not know it is a single row, how can it. So for
>a list within a list it would need to be joining the data (like a
>master-detail). For instance a list of orders and a list of items for each
>order. When you do a 1 to many or a 1 to 1 you need to use subreports.
Thanks. There will be quite a few different detail records for each
master (at least four other tables) so I can't even think of how to
join them all. Subreports certainly seems the way to go. I'll give it
a shot.

Confused about MSDE installation

I needed to distribute the MSDE components to the computers that use my
software so I decided to build a setup program using InstallShield that
included the MSDE files.
After I ran the installation, I noticed that the setup created a folder on
my computer using the MSDE instance name I told the setup program to used
prefixed by a "$" character. So the folder created for an instance named
such as MACHOGRANDE was "C:\Program Files\Microsoft SQL
Server\MSSQL$MACHOGRANDE"
After noticing that, I went on to explore this folder and notice that it had
a bunch of files in it, I was surprised to see that one of the files was
named sqlservr.exe! It almost looked like the installation of my MSDE
instance was like a totally independent sql server installation! Like if it
had nothing to do with the other MSDE instance I had running. I doubt this
is the case since I am pretty sure there must be a gazzilion other files
installed on the computer that are sheared by all the database that use the
MSDE engine.
So my question is,
1. Why did the instance of MSDE crated all of this extra files (such as
sqlservr.exe)? Instead of simply created the ldf and mdf files like a
regular SQL server database? Aren't the MSDE and SQL server supposed to be
the same thing?
2. Also is there a special reason for the "$" character"?
ThanksRene,
what happened is actually exactly what should happen. If you install a
new (named)instance it will always be installed in a folder like
MSSQL$Instancename. It doesn't even matter if you use MSDE or any other
SQL Server edition. A new instance includes it's own sqlserver.exe and
is basically a new installation of the SQL Server engine.
If you just wanted to add a new database you could have done so in your
existing SQLServer installation.
>2. Also is there a special reason for the "$" character"?
I have no idea why MS uses $, probably someone at MS thought this makes
it easier to see that your dealing with a named instance.
M|||Thanks Markus,
If you don't mind, could you tell me if MSDE suffers from the same security
issues as the regular SQL Server?
For example, if a security vulnerability was found in SQL Server where the
server could be exploited by a hacker from the Internet, will I also have
the same problem with the MSDE instance? Or do MSDE instances only run
locally therefore its immune to those types of attacks?
Thanks.
"MarkusB" <m.bohse@.quest-consultants.com> wrote in message
news:1126682536.660588.222940@.f14g2000cwb.googlegroups.com...
> Rene,
> what happened is actually exactly what should happen. If you install a
> new (named)instance it will always be installed in a folder like
> MSSQL$Instancename. It doesn't even matter if you use MSDE or any other
> SQL Server edition. A new instance includes it's own sqlserver.exe and
> is basically a new installation of the SQL Server engine.
> If you just wanted to add a new database you could have done so in your
> existing SQLServer installation.
> I have no idea why MS uses $, probably someone at MS thought this makes
> it easier to see that your dealing with a named instance.
> M
>|||Hi Rene,
Welcome to use MSDN Managed Newsgroup!
I have noticed you posted a duplicated post in the
microsoft.public.sqlserver.msde. To keep the integrity of newsgroup, I will
reply and follow up in that post. Thank you for your patience and
cooperation.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||"Rene" <nospam@.nospam.com> wrote in message
news:O73fJRQuFHA.3452@.TK2MSFTNGP14.phx.gbl...
> Thanks Markus,
> If you don't mind, could you tell me if MSDE suffers from the same
> security issues as the regular SQL Server?
> For example, if a security vulnerability was found in SQL Server where the
> server could be exploited by a hacker from the Internet, will I also have
> the same problem with the MSDE instance? Or do MSDE instances only run
> locally therefore its immune to those types of attacks?
>
MSDE is SQL Server, but in order to reduce the possibility that widely
dispersed MSDE machines could be vulnerable to a network attack, network
connectivity is off my default in MSDE (and its sucessor SQL 2005 Express
Edition).
See
[url]http://support.microsoft.com/? kbid=814130#XSLTH5167121121120121120120[
/url]
David

Confused about MSDE installation

I needed to distribute the MSDE components to the computers that use my
software so I decided to build a setup program using InstallShield that
included the MSDE files.
After I ran the installation, I noticed that the setup created a folder on
my computer using the MSDE instance name I told the setup program to used
prefixed by a "$" character. So the folder created for an instance named
such as MACHOGRANDE was "C:\Program Files\Microsoft SQL
Server\MSSQL$MACHOGRANDE"
After noticing that, I went on to explore this folder and notice that it had
a bunch of files in it, I was surprised to see that one of the files was
named sqlservr.exe! It almost looked like the installation of my MSDE
instance was like a totally independent sql server installation! Like if it
had nothing to do with the other MSDE instance I had running. I doubt this
is the case since I am pretty sure there must be a gazzilion other files
installed on the computer that are sheared by all the database that use the
MSDE engine.
So my question is,
1. Why did the instance of MSDE crated all of this extra files (such as
sqlservr.exe)? Instead of simply created the ldf and mdf files like a
regular SQL server database? Aren't the MSDE and SQL server supposed to be
the same thing?
2. Also is there a special reason for the "$" character"?
Thanks
Rene,
what happened is actually exactly what should happen. If you install a
new (named)instance it will always be installed in a folder like
MSSQL$Instancename. It doesn't even matter if you use MSDE or any other
SQL Server edition. A new instance includes it's own sqlserver.exe and
is basically a new installation of the SQL Server engine.
If you just wanted to add a new database you could have done so in your
existing SQLServer installation.
>2. Also is there a special reason for the "$" character"?
I have no idea why MS uses $, probably someone at MS thought this makes
it easier to see that your dealing with a named instance.
M
|||Thanks Markus,
If you don't mind, could you tell me if MSDE suffers from the same security
issues as the regular SQL Server?
For example, if a security vulnerability was found in SQL Server where the
server could be exploited by a hacker from the Internet, will I also have
the same problem with the MSDE instance? Or do MSDE instances only run
locally therefore its immune to those types of attacks?
Thanks.
"MarkusB" <m.bohse@.quest-consultants.com> wrote in message
news:1126682536.660588.222940@.f14g2000cwb.googlegr oups.com...
> Rene,
> what happened is actually exactly what should happen. If you install a
> new (named)instance it will always be installed in a folder like
> MSSQL$Instancename. It doesn't even matter if you use MSDE or any other
> SQL Server edition. A new instance includes it's own sqlserver.exe and
> is basically a new installation of the SQL Server engine.
> If you just wanted to add a new database you could have done so in your
> existing SQLServer installation.
> I have no idea why MS uses $, probably someone at MS thought this makes
> it easier to see that your dealing with a named instance.
> M
>
|||Hi Rene,
Welcome to use MSDN Managed Newsgroup!
I have noticed you posted a duplicated post in the
microsoft.public.sqlserver.msde. To keep the integrity of newsgroup, I will
reply and follow up in that post. Thank you for your patience and
cooperation.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||"Rene" <nospam@.nospam.com> wrote in message
news:O73fJRQuFHA.3452@.TK2MSFTNGP14.phx.gbl...
> Thanks Markus,
> If you don't mind, could you tell me if MSDE suffers from the same
> security issues as the regular SQL Server?
> For example, if a security vulnerability was found in SQL Server where the
> server could be exploited by a hacker from the Internet, will I also have
> the same problem with the MSDE instance? Or do MSDE instances only run
> locally therefore its immune to those types of attacks?
>
MSDE is SQL Server, but in order to reduce the possibility that widely
dispersed MSDE machines could be vulnerable to a network attack, network
connectivity is off my default in MSDE (and its sucessor SQL 2005 Express
Edition).
See
http://support.microsoft.com/?kbid=8...21120121120120
David

Confused about MSDE installation

I needed to distribute the MSDE components to the computers that use my
software so I decided to build a setup program using InstallShield that
included the MSDE files.
After I ran the installation, I noticed that the setup created a folder on
my computer using the MSDE instance name I told the setup program to used
prefixed by a "$" character. So the folder created for an instance named
such as MACHOGRANDE was "C:\Program Files\Microsoft SQL
Server\MSSQL$MACHOGRANDE"
After noticing that, I went on to explore this folder and notice that it had
a bunch of files in it, I was surprised to see that one of the files was
named sqlservr.exe! It almost looked like the installation of my MSDE
instance was like a totally independent sql server installation! Like if it
had nothing to do with the other MSDE instance I had running. I doubt this
is the case since I am pretty sure there must be a gazzilion other files
installed on the computer that are sheared by all the database that use the
MSDE engine.
So my question is,
1. Why did the instance of MSDE crated all of this extra files (such as
sqlservr.exe)? Instead of simply created the ldf and mdf files like a
regular SQL server database? Aren't the MSDE and SQL server supposed to be
the same thing?
2. Also is there a special reason for the "$" character"?
ThanksRene,
what happened is actually exactly what should happen. If you install a
new (named)instance it will always be installed in a folder like
MSSQL$Instancename. It doesn't even matter if you use MSDE or any other
SQL Server edition. A new instance includes it's own sqlserver.exe and
is basically a new installation of the SQL Server engine.
If you just wanted to add a new database you could have done so in your
existing SQLServer installation.
>2. Also is there a special reason for the "$" character"?
I have no idea why MS uses $, probably someone at MS thought this makes
it easier to see that your dealing with a named instance.
M|||Thanks Markus,
If you don't mind, could you tell me if MSDE suffers from the same security
issues as the regular SQL Server?
For example, if a security vulnerability was found in SQL Server where the
server could be exploited by a hacker from the Internet, will I also have
the same problem with the MSDE instance? Or do MSDE instances only run
locally therefore its immune to those types of attacks?
Thanks.
"MarkusB" <m.bohse@.quest-consultants.com> wrote in message
news:1126682536.660588.222940@.f14g2000cwb.googlegroups.com...
> Rene,
> what happened is actually exactly what should happen. If you install a
> new (named)instance it will always be installed in a folder like
> MSSQL$Instancename. It doesn't even matter if you use MSDE or any other
> SQL Server edition. A new instance includes it's own sqlserver.exe and
> is basically a new installation of the SQL Server engine.
> If you just wanted to add a new database you could have done so in your
> existing SQLServer installation.
>>2. Also is there a special reason for the "$" character"?
> I have no idea why MS uses $, probably someone at MS thought this makes
> it easier to see that your dealing with a named instance.
> M
>|||Hi Rene,
Welcome to use MSDN Managed Newsgroup!
I have noticed you posted a duplicated post in the
microsoft.public.sqlserver.msde. To keep the integrity of newsgroup, I will
reply and follow up in that post. Thank you for your patience and
cooperation.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||"Rene" <nospam@.nospam.com> wrote in message
news:O73fJRQuFHA.3452@.TK2MSFTNGP14.phx.gbl...
> Thanks Markus,
> If you don't mind, could you tell me if MSDE suffers from the same
> security issues as the regular SQL Server?
> For example, if a security vulnerability was found in SQL Server where the
> server could be exploited by a hacker from the Internet, will I also have
> the same problem with the MSDE instance? Or do MSDE instances only run
> locally therefore its immune to those types of attacks?
>
MSDE is SQL Server, but in order to reduce the possibility that widely
dispersed MSDE machines could be vulnerable to a network attack, network
connectivity is off my default in MSDE (and its sucessor SQL 2005 Express
Edition).
See
http://support.microsoft.com/?kbid=814130#XSLTH5167121121120121120120
David

Confused

I have VB. NET
I want to build SQL databases on my own PC using VB and
MSDE.
No matter how many ways I install it or passwords I use,
I just cannot get read/write access from witihn VB. I
have upsized the Northwind.mdb.
There seems to be a multidude or service packs for MSDE
and numerous ways of entering passwords.
Could osmeone please just give me a setp by step account
of installing MSDE (with all relevant switches and
passwords), getting a SQL instance on MSDE running and
visible on the manager, upsizing the access database
(with all relevant passwords - what the hell is a trusted
connection?), and then be able to create a view from the
Server Explorer in .NET.
I've been slaving over this for the past two days and
it's driving me nuts. Please help maintain my sanity.
Thanks
Guy
hi Guy,
"Guy" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:0ae801c4d89a$9e2c19b0$a401280a@.phx.gbl
> I have VB. NET
> I want to build SQL databases on my own PC using VB and
> MSDE.
> No matter how many ways I install it or passwords I use,
> I just cannot get read/write access from witihn VB. I
> have upsized the Northwind.mdb.
> There seems to be a multidude or service packs for MSDE
> and numerous ways of entering passwords.
> Could osmeone please just give me a setp by step account
> of installing MSDE (with all relevant switches and
> passwords), getting a SQL instance on MSDE running and
> visible on the manager, upsizing the access database
> (with all relevant passwords - what the hell is a trusted
> connection?), and then be able to create a view from the
> Server Explorer in .NET.
> I've been slaving over this for the past two days and
> it's driving me nuts. Please help maintain my sanity.
in order to create new objects the Windows NT login you are using when
connecting with trusted authentication must be member of the ddl_admin fixed
database role, please have a look at
http://msdn.microsoft.com/library/de...urity_6ndx.asp
for further info
as about authentication, I do think you have to understand the security
approach of SQL Server, and you can start reading at
http://msdn.microsoft.com/library/de...urity_47u6.asp
this is the first phase of the 2 levels security system of SQL Server...
again, the 1st phase is validating login to the server..
the second phase regards a database security implementation... in order to
access a specified database the simple login existance does not provide
database access, but a (database) user must be mapped to the corresponding
login (this is done on the basis of a join between the MyDb..sysusers.sid =
master..syslogins.sid )..
the 2nd phase is about verifying that at each object level (including
database, tables, views, columns, procedures and so on) the Login/User
association is permitted access to... please go on reading at
http://msdn.microsoft.com/library/de...ar_da_0n77.asp
and following chapters..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Confirming the right hyperlink

Hi,
We create rdl files which contains <Hyperlink> elements. The
value for hyperlink is an expression build using report parameters,
field parameters etc and also contains calls to custom assemblies
eg : <Hyperlink>=Parameters!Param1.Value + CustomAssemblyCall + Fields!
someField.Value<Hyperlink>
When this report is rendered by HTML Rendering extension(by specifying
HTML4.0 in the format string passed to render() method) this
<Hyperlink> element is converted to href attribute of the <a> tag.
We have a scenario where we want to test whether this href url
generated is correct or no without deploying the rdl file on the
report server.
Is there any way to pass the xml file and find out what would be href
value when the <Hyperlink>
element is parsed by the report server ?
Any report server dll's which can directly be used ?
Thanks in advance,Can anyone guide me on this

configuring locks in awe system

I am running Microsoft SQL Server 2000 - 8.00.760 Enterprise Edition
on Windows 2003 Enterprise Edition (NT 5.2 Build 3790:) I have 4CPU
and 8GB of RAM. I have AWE enabled, /pae /3gb switch is on in
boot.ini, In my errorlog I have noticed few times error messages as
"The SQL Server cannot obtain a LOCK resource at this time. Rerun your
statement when there are fewer active users or ask the system
administrator to check the SQL Server lock and memory configuration..
" I haven't modified anything in sp_configure 'locks', so i am
assuming SQL server is dynamically managing the lock memory. Running
perfmon for few days I observed that Lock Requests/sec are usually few
100,000 most of the times and sometimes goes to 2+ million. However I
haven't seen Lock Memory (KB) going more than 40MB. So i wonder why am
I seeing the Error: 1204 in my sql log ? And any advise on how to
prevent it.
Thanks
Aswineeaswinee (aswinee@.yahoo.com) writes:
> I am running Microsoft SQL Server 2000 - 8.00.760 Enterprise Edition
> on Windows 2003 Enterprise Edition (NT 5.2 Build 3790:) I have 4CPU
> and 8GB of RAM. I have AWE enabled, /pae /3gb switch is on in
> boot.ini, In my errorlog I have noticed few times error messages as
> "The SQL Server cannot obtain a LOCK resource at this time. Rerun your
> statement when there are fewer active users or ask the system
> administrator to check the SQL Server lock and memory configuration..
> " I haven't modified anything in sp_configure 'locks', so i am
> assuming SQL server is dynamically managing the lock memory. Running
> perfmon for few days I observed that Lock Requests/sec are usually few
> 100,000 most of the times and sometimes goes to 2+ million. However I
> haven't seen Lock Memory (KB) going more than 40MB. So i wonder why am
> I seeing the Error: 1204 in my sql log ? And any advise on how to
> prevent it.

I guess there are two questions here:
1) is that locking frequency natural, or is there is a need to investigate
this?
2) are you really hitting hard limits of number of available locks.

I don't know what the maximum number of locks, but I expect it to be more
than two million. Then again, two million lock requests in one second,
does not tell us how many locks thar actually are in use. A lock can be
held for a short moment, or several hours (which would be due to poor
design).

But two million lock requests, or even 100000 sounds a lot to me. But if
that is a busy system it could be normal.

Since this is not really my field of expertise, so I asked in our private
MVP forum, and I got these suggestion:

few interesting points to check are:
- make sure your statistics are up to date
- you have sufficient indexes to run your query efficiently

which is pretty standard. But this is more interesting:

I'd also ask if trace flag 1211 has been set, see
http://support.microsoft.com/?kbid=323630

With 1211 set, you turn off lock escalation, and this can lead to a lot of
locks being requested.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp