Database

IMAGE IN SQL REPORTING SERVICES

3-Dec-08 7:20

Ben Fair wrote:
That's an intriguing idea

My thoughts exactly Smile | :)

Previously I've done the same thing a bit differently, but now with 2008 it's easy and efficient.

The need to optimize rises from a bad design.My articles[^]

member272-Dec-08 1:02

member27

2-Dec-08 1:02

HI ALL,

Iam using sql reporting services ,i want to keep image from database

I kept IMAGE AND KEPT THE DATASOURCE FIELD AS (EX PHOTO_LOCATION)
IN THAT PHOTO_LOCATION FIELD IAM HAVING IMAGE NAME ..

(I ALSO KET THE IMAGE LOCATION IN TAT FILED AND CHECKED ,BUT IMAGE IS NOT COIMG)

WHEN I RUN THE REPORT IMAGE IS NOT VISIBLE ONLY TAT BLANK IMAGE IS COMING .I ALSO KEPT THE MIMET TYPE CORRECTLY

Re: IMAGE IN SQL REPORTING SERVICES

ChandraRam2-Dec-08 2:14

ChandraRam

2-Dec-08 2:14

cbenan wrote:
IN THAT PHOTO_LOCATION FIELD IAM HAVING IMAGE NAME ..

do you mean the image's file name?

You need to store the actual image in your database, and then use it in your report. Google for how to store images in a database - I'm sure you will find a large number of hits on CP too.

Using all caps in a message is the equivalent of shouting

Re: IMAGE IN SQL REPORTING SERVICES

member272-Dec-08 4:45

member27

2-Dec-08 4:45

ok...i hvae image path also in my database ..i gvae that field and checked ..but also it is not wrking

Re: IMAGE IN SQL REPORTING SERVICES

Ben Fair3-Dec-08 4:02

Ben Fair

3-Dec-08 4:02

I believe there is a property of the image that can be set to 'External' that allows you to use the value to refer to a location; however, this may only work with a URL location or perhaps in UNC format. Sorry, but I don't recall the name of the property off-hand.

Keep It Simple Stupid! (KISS)

OleDb?

dec821-Dec-08 20:03

dec82

1-Dec-08 20:03

Anyone have simple source code to work with OleDb database such as write data into table?
thanks

Ashfield1-Dec-08 21:20

Ashfield

1-Dec-08 21:20

There are loads of examples on CP and Google. Its quicker to go to google and type "OleDb insert" than it is to post your question here and wait for an answer. If you want to make a living as a developer then remember google is your friend.

Bob
Ashfield Consultants Ltd

Wendelius1-Dec-08 23:20

1-Dec-08 23:20

Ashfield wrote:
Its quicker to go to google and type "OleDb insert"

Had to try: approximately 252 000 hits.

The need to optimize rises from a bad design.My articles[^]

Paul Conrad2-Dec-08 5:58

Paul Conrad

2-Dec-08 5:58

Mika Wendelius wrote:

Had to try: approximately 252 000 hits.

There is bound to be something very good in all of that Smile | :)

"The clue train passed his station without stopping." - John Simmons / outlaw programmer

"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon

"Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham

Wendelius2-Dec-08 6:09

is it possible to handle two transaction using DTC?

2-Dec-08 6:09

I would guess so Smile | :)

The need to optimize rises from a bad design.My articles[^]

paresh_joe1-Dec-08 19:57

paresh_joe

1-Dec-08 19:57

I am interested in knowing whether it is possible to coordinate two database transaction using Distributed Transaction Coordinator (MSDTC).

Any reference would be good.

Thanks,
Perry Smile | :)

Re: is it possible to handle two transaction using DTC? [modified]

Wendelius1-Dec-08 23:15

Is it possible for triggers not to execute when the performance is poor?

1-Dec-08 23:15

paresh_joe wrote:
whether it is possible to coordinate two database transaction using Distributed Transaction Coordinator

Could you clarify this with a scenario.

The need to optimize rises from a bad design.My articles[^]

modified on Tuesday, December 2, 2008 5:48 AM

Rafferty Uy1-Dec-08 16:42

Re: Is it possible for triggers not to execute when the performance is poor?

1-Dec-08 16:42

Hello,

Some quick questions to help me in my investigation...

Is it possible for triggers not to execute when the performance is poor?

The scenario is this, we have a trigger on table A that copies data to table B whenever an insert/update is done on table A.
However, when we were having performance problems with the server, it seems like the trigger did not execute. This looks like the case because the data was successfully inserted in table A but it is not found in table B.

What could have been the problem?

Also, is it possible for the trigger to roll back the insert on table A if it fails? How can I do this?

Thank you in advance.

Rafferty

Wendelius1-Dec-08 17:46

Re: Is it possible for triggers not to execute when the performance is poor?

1-Dec-08 17:46

Rafferty Uy wrote:
Is it possible for triggers not to execute when the performance is poor?

No, unless there's a bug in SQL Server.

Rafferty Uy wrote:
is it possible for the trigger to roll back the insert on table A if it fails

Yes it is. By executing rollback statement which rolls back the entire transaction.

The need to optimize rises from a bad design.My articles[^]

Rafferty Uy1-Dec-08 18:57

Re: Is it possible for triggers not to execute when the performance is poor?

1-Dec-08 18:57

I see.

What I meant with roll back is... for example I run a stored procedure AddToTableA, which executes a trigger TableAInsertTrigger.
How can I write TableAInsertTrigger in such a way that, if it fails, it will also roll back the AddToTableA SP?

Rafferty

Wendelius1-Dec-08 20:30

Re: Is it possible for triggers not to execute when the performance is poor?

1-Dec-08 20:30

Rafferty Uy wrote:
How can I write TableAInsertTrigger in such a way that, if it fails, it will also roll back the AddToTableA SP?

Simply execute rollback as long as the operations are in the same transaction. Have a look at for example this article: http://www.codeproject.com/KB/database/sqlservertransactions.aspx[^]

The need to optimize rises from a bad design.My articles[^]

Rafferty Uy1-Dec-08 22:32

Re: Is it possible for triggers not to execute when the performance is poor?

1-Dec-08 22:32

So, if I get this correctly... for example given the following SP and Trigger

CREATE PROCEDURE AddToTableA() AS
BEGIN
    BEGIN TRANSACTION
    INSERT INTO TableA VALUES(1, 'SomeValue')
    IF (@@ERROR <> 0) GOTO ERR_HANDLER
    COMMIT TRANSACTION
    RETURN 0

    ERR_HANDLER:
    ROLLBACK TRANSACTION
END

CREATE TRIGGER TableAInsertTrigger ON TableA FOR INSERT
BEGIN
    INSERT INTO TableB (SELECT * FROM INSERTED)
    
    -- do something else here, one that causes error
END

In the above case, if I call AddToTableA() and since TableAInsertTrigger fails, it will roll back the inserts on both TableB (in the Trigger) and TableA (in the SP)?

btw, thank you for helping Smile | :)

Rafferty

Wendelius1-Dec-08 23:13

Re: Is it possible for triggers not to execute when the performance is poor?

1-Dec-08 23:13

Rafferty Uy wrote:
In the above case, if I call AddToTableA() and since TableAInsertTrigger fails, it will roll back the inserts on both TableB (in the Trigger) and TableA (in the SP)?

Yes, exactly. The insert statement in the trigger is inside the same transaction as the insert that fired the trigger. This is why if you roll back the transaction, also trigger modifications are rolled back.

It's easy to test if you create an error in the end of the trigger (for example set @variable = 1/0), you can see what happens.

Rafferty Uy wrote:
btw, thank you for helping

No problem Smile | :)

The need to optimize rises from a bad design.My articles[^]

Rafferty Uy2-Dec-08 20:28

Re: Is it possible for triggers not to execute when the performance is poor?

2-Dec-08 20:28

Thanks again!

btw, just another quick question. If I do the condition above... does it mean that the SP will no longer raise an error?

For example, if I have another SP calling AddToTableA(), and let's say that this other SP has an if...else statement depending if AddToTableA() causes an error, will AddToTableA() still return an error when it already handled the @@ERROR and executed a ROLLBACK TRANSACTION?

Rafferty

Wendelius3-Dec-08 8:03

Re: Is it possible for triggers not to execute when the performance is poor?

3-Dec-08 8:03

When you execute RAISERROR in a stored procedure, the caller will see an error as a result, regardless who is calling the block. So even if you catch the error, the RAISERROR generates a 'new' one.

If the SP has executed rollback then there's no transaction left so be sure that you don't make any modifications since they would not be part of the original transaction.

Also, if I remember correctly, you cannot execute ROLLBACK again since it would generate a different error (no transaction or such).

I think it would be good if you create a test situation and try different variations in order to find the one that suits you best.

Mika

The need to optimize rises from a bad design.My articles[^]

Rafferty Uy3-Dec-08 18:30

Re: Is it possible for triggers not to execute when the performance is poor?

3-Dec-08 18:30

okay, thanks a lot!

Rafferty

Wendelius4-Dec-08 3:49