Bar Chart - Bar Width

Does RS provide help specifying the width of a Bar in a Simple Bar Chart ?
Right now, it creates even sized bar for a given size of a Chart.
p.s. I've already applied SP1 (jfyi) -- which allows me to color code
individual bar appearing on the Chart (I must say, that is really GOOD!!)
Thanks.See related post:
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=8eda1408-dffc-459e-8cb3-c52e718c2358&sloc=en-us.
--
Ravi Mumulla (Microsoft)
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kam" <Kam@.discussions.microsoft.com> wrote in message
news:E81BF3CB-27A6-46F7-9A13-61C6B5D4FA0B@.microsoft.com...
> Does RS provide help specifying the width of a Bar in a Simple Bar Chart ?
> Right now, it creates even sized bar for a given size of a Chart.
> p.s. I've already applied SP1 (jfyi) -- which allows me to color code
> individual bar appearing on the Chart (I must say, that is really GOOD!!)
> Thanks.sql

Bad Practice: Calling Views From w/in Stored Procs

In general, is it bad practice to call a view from w/in a stored proc?
Some sites imply that SQL server creates two connections thereby
straining system resources that much more, some sites claim it doesn't.There is no penalty to using a view, whether inside a stored procedure
or not. There is no second connection from using a view.
If you have a source that actually says that, I would be concerned
about counting on that source for information.
Roy Harvey
Beacon Falls, CT
On 2 May 2006 10:45:32 -0700, "roy.@.nderson@.gm@.il.com"
<roy.anderson@.gmail.com> wrote:

>In general, is it bad practice to call a view from w/in a stored proc?
>Some sites imply that SQL server creates two connections thereby
>straining system resources that much more, some sites claim it doesn't.|||> Some sites imply that SQL server creates two connections thereby
> straining system resources that much more
Can you reference such a site / source?
A

Bad Design?

Table A
[ID] [SalesmanEmail] [SalesmanName]
Table B
[ID] [QuoteNo] [SalesmanID]
Table C
[ID] [Product] [QuoteNo]

Program A creates the records for Table C. In the process it reads from Table A and Table B.

Program B reads record from Table C. Program B now needs [SalesmanEmail] field.

The suggestion is to add [SalesmanEmail] to Table C. Is this good or bad design?Select TableA.SalesmanEmail From TableA Where TableA.ID In (Select Distinct TableB.SalesmanID From TableB Where TableB.ID = whatever);|||That's how I suggested we do it, however the "senior" programmer was the one who asked me to write out SalesmanEmail directly into Table C.

I tried to explain to him that if there were ever any modifications to SalesmanEmail in Table A or to SalesManID in Table B, every record I wrote in Table C would now be invalid because we wrote it to a column instead of doing a lookup, but he still didn't get what I meant. And his method also wastes DB space by storing the same field in multiple tables.|||The suggestion to put the salesman's email address into Table C violates the Second Normal Form of database normalization. It belongs solely in Table A.

Terri|||:: Table C violates the Second Normal Form of database normalization.

Is that a misdeameanor or felony? or does the SQL cop just write you a ticket?

j/k. :)

Yeah, I just gave a query example how you don't need to add a new field if it's already in another.|||But he would probably be more comforted to see:

SELECT
 TableC.Product,
 TableC.QuoteNo,
 TableA.SalesmanName,
 TableA.SalesmanEmail
FROM
 TableC
INNER JOIN
 TableB ON TableB.QuoteNo = TableC.QuoteNo
INNER JOIN
 TableA ON TableA.SalesmanID = TableB.SalesmanID

;-)

Terri
PS - I think the penalty is pocket protector removal

Backup-only ID

I have a stored procedure that I use to execute database backups. It delete
s
old backup files and then creates the full backups of all the databases.
I want to create an ID that can only execute this procedure. I tried
creating a SQL ID with execute permission on this SP and then put the ID in
the db_backupoperator role in each database. But I keep running into
permission issues.
Any suggestions?What issues are you running into? Give specific examples and error messages
.
MeanOldDBA
derrickleggett@.hotmail.com
http://weblogs.sqlteam.com/derrickl
When life gives you a lemon, fire the DBA.
"Stephanie" wrote:

> I have a stored procedure that I use to execute database backups. It dele
tes
> old backup files and then creates the full backups of all the databases.
> I want to create an ID that can only execute this procedure. I tried
> creating a SQL ID with execute permission on this SP and then put the ID i
n
> the db_backupoperator role in each database. But I keep running into
> permission issues.
> Any suggestions?
>