Multiple Formats...

I have a textbox that reads " Money: " and then a cash amount.... I have
formated the expression like this -
="Money: " & Format(Sum(Fields!Amount.Value),"C")
but my question is how can i get the SUM to be a different color than what
the word Money is. Currently money is defaulted to black but I want the SUM
to be green.
Any help will be greatly appreciated, thx!
--
CipherTeKST
MCSE: Security 2003, CCNA, Security+Drag two textbox and size it accordingly, put "Money" text in one text box
and the value in the other and changing the color to green.
Amarnath
"CipherTeKST" wrote:
> I have a textbox that reads " Money: " and then a cash amount.... I have
> formated the expression like this -
> ="Money: " & Format(Sum(Fields!Amount.Value),"C")
> but my question is how can i get the SUM to be a different color than what
> the word Money is. Currently money is defaulted to black but I want the SUM
> to be green.
> Any help will be greatly appreciated, thx!
> --
> CipherTeKST
> MCSE: Security 2003, CCNA, Security+

multiple database performance

I'm planning on creating multiple databases on a client because I'm storing a large amount of binary data (jpg's and pdf's) in tables and there are size limitations for a single database. So, in order to get around the size limitations, I'm just creating one database for my main tables and multiple other databases to hold the binary data.

Any performance considerations I should consider in regards to multiple databases? Any other thoughts?

Hi,

what about not storing the data in the database ? Do a quick one on this document, it has some detailed information for your design:

http://research.microsoft.com/research/pubs/view.aspx?msr_tr_id=MSR-TR-2006-45

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||First, what size limit in SQL 2005 are you trying to avoid?

Second, as someone else pointed out, saving files in the database is not a good design. The main problem is, what do you do with them once they are there? How do you get them out? The OS is much better at saving files efficiently than SQL. Creating an "index" database into the files is a much better method.

To answer your question, it depends on your design and situation. What are you going to do with the data, how do you query the databases, etc. There is very little impact in selecting data from tables in different database on the same sever.|||I think I may have posted this in the wrong group (I am actually going to use SQL Server CE), but the 2 responses were extremely helpful. Thanks!

Multiple Database hits vs Bulk Data parameters

I was curious to know if it the amount of data sent to the sql server mattered.I am working on a web application and I have three stored procedures that most likely will be called one after the other. Each procedure accepts at least 4 parameters. Instead if I create one stored procedure, then I will be passing at least 12 parameters. Some of the parameters could be quite bulky(at least 1000 characters).So which one is better, 1 stored procedure with 12 parameters or 3 stored procedures with 4 parameters each called one after the other.Thanks

For SQL Server, the cost of parsing parameters can always be ingonred compared with the cost of compiling a store procedure and producing a optimized execution plan for it.

From network I/O aspect, each execution of a stored procedure is considered as a 'batch' (batch in SQL means all data will be processed and returned at one time, which can greatly improve network performance). So if you use 3 stored procedures, you need 3 rounds; while 1 stored procedure need only 1 round.

So generally I suggest you use 1 stored procedure with 12 parameters.