Imbricated transactions

Is it possible to start a transaction inside another transaction ?
Should I specify a particular isolation level ?
Any ideas or tricks are welcome.
ThanXYes you can have nested transactions.

When I have complex work to perform or cascading delets, I set IMPLICIT_TRANSACTIONS to on and then manage commits/rollbacks myself. Otherwise I stick to AUTOCOMMIT.

I would encourage you to look up "transactions, described" in Books On Line.

Images on a report

I am trying to put an image behind a textbox. It's one of those rounded rectangles and the effect I'm after is that the text looks like it is inside a nice rectangle graphic. It looks fine in preview mode, but when I deploy the report the text is below the image and not 'inside' it.
What am I doing wrong?
Thanks

dear,

What is the source of the image.

I mean from database,or web or Disk.

HTH

from

sufian

|||The image is embedded into the report - it resides on the disk of the server.
I've got round the problem to an extent by making a textbox, typing the text and then setting a background image that is exactly the same size as the textbox, but if you get the textbox slightly too big or small, it either cuts a bit off or repeats (I could switch off the repeat I s'pose).|||

Dear,

Set the backgroundrepeat option to norepeat.

HTH

from

sufian

Images inside a literal

I am displaying the output from a Report inside a literal. Everything
is OK, except the images are not displaying. Is there anything special
I have to do?
When using preview or the MS Sample Report Viewer Control, the images
appear.
I cannot use the Report Viewer Control as I need to pass XML to the
report, not a server side data source.
Can someone help?
Matt...As you probably know, there three types of getting imager into report:
1) From database â'it is not you case
2) Embedded into the report application
3) URL to the image â' this one you may try.
Regards, ProJester,
MSN Programmer.
"mtatro@.direcsoft.com" wrote:
> I am displaying the output from a Report inside a literal. Everything
> is OK, except the images are not displaying. Is there anything special
> I have to do?
> When using preview or the MS Sample Report Viewer Control, the images
> appear.
> I cannot use the Report Viewer Control as I need to pass XML to the
> report, not a server side data source.
> Can someone help?
> Matt...
>|||How can I get the Embedded option to work?
Matt...

Image Server Database

I am a semi-experienced DBA, but have some questions regarding the
storage of images inside of SQL Server (which I have never done before).
I am researching to pros and cons of storing images inside of SQL
Server verses a file server and DB combination (storing the file paths
in SQL). There is a push from my management to store all the images
within a very large database, but something is telling me that it's not
the best way to do it. Unfortunately, I don't have any concrete
experience/evidence to push in one direction verses another.
We are talking about the storage/cataloging of around 4 million images.
Our current image server is file-based and is around 1 tera in size.
The idea of moving all this into a large SQL Server database raises
allot of concern for me.
I guess I would just like some feed-back from others that may have
experience using SQL Server to house a large amount of images. I would
also like to hear if anyone may have pros/cons to one concept verses
another. Any help would be greatly appreciated.
http://www.aspfaq.com/show.asp?id=2149
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
"Justin Furch" <jlf@.anon.com> wrote in message
news:%23iW9Zu0wEHA.1512@.TK2MSFTNGP12.phx.gbl...
> I am a semi-experienced DBA, but have some questions regarding the
> storage of images inside of SQL Server (which I have never done before).
> I am researching to pros and cons of storing images inside of SQL
> Server verses a file server and DB combination (storing the file paths
> in SQL). There is a push from my management to store all the images
> within a very large database, but something is telling me that it's not
> the best way to do it. Unfortunately, I don't have any concrete
> experience/evidence to push in one direction verses another.
> We are talking about the storage/cataloging of around 4 million images.
> Our current image server is file-based and is around 1 tera in size.
> The idea of moving all this into a large SQL Server database raises
> allot of concern for me.
> I guess I would just like some feed-back from others that may have
> experience using SQL Server to house a large amount of images. I would
> also like to hear if anyone may have pros/cons to one concept verses
> another. Any help would be greatly appreciated.
|||Hello Justin,
We used to have lot of Contracts that needed to be scanned in the insurance
application
and we used FileNET imaging server.
Gopi
"Justin Furch" <jlf@.anon.com> wrote in message
news:%23iW9Zu0wEHA.1512@.TK2MSFTNGP12.phx.gbl...
>I am a semi-experienced DBA, but have some questions regarding the storage
>of images inside of SQL Server (which I have never done before). I am
>researching to pros and cons of storing images inside of SQL Server verses
>a file server and DB combination (storing the file paths in SQL). There is
>a push from my management to store all the images within a very large
>database, but something is telling me that it's not the best way to do it.
>Unfortunately, I don't have any concrete experience/evidence to push in one
>direction verses another.
> We are talking about the storage/cataloging of around 4 million images.
> Our current image server is file-based and is around 1 tera in size. The
> idea of moving all this into a large SQL Server database raises allot of
> concern for me.
> I guess I would just like some feed-back from others that may have
> experience using SQL Server to house a large amount of images. I would
> also like to hear if anyone may have pros/cons to one concept verses
> another. Any help would be greatly appreciated.

Image Server Database

I am a semi-experienced DBA, but have some questions regarding the
storage of images inside of SQL Server (which I have never done before).
I am researching to pros and cons of storing images inside of SQL
Server verses a file server and DB combination (storing the file paths
in SQL). There is a push from my management to store all the images
within a very large database, but something is telling me that it's not
the best way to do it. Unfortunately, I don't have any concrete
experience/evidence to push in one direction verses another.
We are talking about the storage/cataloging of around 4 million images.
Our current image server is file-based and is around 1 tera in size.
The idea of moving all this into a large SQL Server database raises
allot of concern for me.
I guess I would just like some feed-back from others that may have
experience using SQL Server to house a large amount of images. I would
also like to hear if anyone may have pros/cons to one concept verses
another. Any help would be greatly appreciated.
http://www.aspfaq.com/show.asp?id=2149
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
"Justin Furch" <jlf@.anon.com> wrote in message
news:%23iW9Zu0wEHA.1512@.TK2MSFTNGP12.phx.gbl...
> I am a semi-experienced DBA, but have some questions regarding the
> storage of images inside of SQL Server (which I have never done before).
> I am researching to pros and cons of storing images inside of SQL
> Server verses a file server and DB combination (storing the file paths
> in SQL). There is a push from my management to store all the images
> within a very large database, but something is telling me that it's not
> the best way to do it. Unfortunately, I don't have any concrete
> experience/evidence to push in one direction verses another.
> We are talking about the storage/cataloging of around 4 million images.
> Our current image server is file-based and is around 1 tera in size.
> The idea of moving all this into a large SQL Server database raises
> allot of concern for me.
> I guess I would just like some feed-back from others that may have
> experience using SQL Server to house a large amount of images. I would
> also like to hear if anyone may have pros/cons to one concept verses
> another. Any help would be greatly appreciated.
|||Hello Justin,
We used to have lot of Contracts that needed to be scanned in the insurance
application
and we used FileNET imaging server.
Gopi
"Justin Furch" <jlf@.anon.com> wrote in message
news:%23iW9Zu0wEHA.1512@.TK2MSFTNGP12.phx.gbl...
>I am a semi-experienced DBA, but have some questions regarding the storage
>of images inside of SQL Server (which I have never done before). I am
>researching to pros and cons of storing images inside of SQL Server verses
>a file server and DB combination (storing the file paths in SQL). There is
>a push from my management to store all the images within a very large
>database, but something is telling me that it's not the best way to do it.
>Unfortunately, I don't have any concrete experience/evidence to push in one
>direction verses another.
> We are talking about the storage/cataloging of around 4 million images.
> Our current image server is file-based and is around 1 tera in size. The
> idea of moving all this into a large SQL Server database raises allot of
> concern for me.
> I guess I would just like some feed-back from others that may have
> experience using SQL Server to house a large amount of images. I would
> also like to hear if anyone may have pros/cons to one concept verses
> another. Any help would be greatly appreciated.
sql

Image Server Database

I am a semi-experienced DBA, but have some questions regarding the
storage of images inside of SQL Server (which I have never done before).
I am researching to pros and cons of storing images inside of SQL
Server verses a file server and DB combination (storing the file paths
in SQL). There is a push from my management to store all the images
within a very large database, but something is telling me that it's not
the best way to do it. Unfortunately, I don't have any concrete
experience/evidence to push in one direction verses another.
We are talking about the storage/cataloging of around 4 million images.
Our current image server is file-based and is around 1 tera in size.
The idea of moving all this into a large SQL Server database raises
allot of concern for me.
I guess I would just like some feed-back from others that may have
experience using SQL Server to house a large amount of images. I would
also like to hear if anyone may have pros/cons to one concept verses
another. Any help would be greatly appreciated.http://www.aspfaq.com/show.asp?id=2149
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--
"Justin Furch" <jlf@.anon.com> wrote in message
news:%23iW9Zu0wEHA.1512@.TK2MSFTNGP12.phx.gbl...
> I am a semi-experienced DBA, but have some questions regarding the
> storage of images inside of SQL Server (which I have never done before).
> I am researching to pros and cons of storing images inside of SQL
> Server verses a file server and DB combination (storing the file paths
> in SQL). There is a push from my management to store all the images
> within a very large database, but something is telling me that it's not
> the best way to do it. Unfortunately, I don't have any concrete
> experience/evidence to push in one direction verses another.
> We are talking about the storage/cataloging of around 4 million images.
> Our current image server is file-based and is around 1 tera in size.
> The idea of moving all this into a large SQL Server database raises
> allot of concern for me.
> I guess I would just like some feed-back from others that may have
> experience using SQL Server to house a large amount of images. I would
> also like to hear if anyone may have pros/cons to one concept verses
> another. Any help would be greatly appreciated.|||Hello Justin,
We used to have lot of Contracts that needed to be scanned in the insurance
application
and we used FileNET imaging server.
Gopi
"Justin Furch" <jlf@.anon.com> wrote in message
news:%23iW9Zu0wEHA.1512@.TK2MSFTNGP12.phx.gbl...
>I am a semi-experienced DBA, but have some questions regarding the storage
>of images inside of SQL Server (which I have never done before). I am
>researching to pros and cons of storing images inside of SQL Server verses
>a file server and DB combination (storing the file paths in SQL). There is
>a push from my management to store all the images within a very large
>database, but something is telling me that it's not the best way to do it.
>Unfortunately, I don't have any concrete experience/evidence to push in one
>direction verses another.
> We are talking about the storage/cataloging of around 4 million images.
> Our current image server is file-based and is around 1 tera in size. The
> idea of moving all this into a large SQL Server database raises allot of
> concern for me.
> I guess I would just like some feed-back from others that may have
> experience using SQL Server to house a large amount of images. I would
> also like to hear if anyone may have pros/cons to one concept verses
> another. Any help would be greatly appreciated.

Image Server Database

I am a semi-experienced DBA, but have some questions regarding the
storage of images inside of SQL Server (which I have never done before).
I am researching to pros and cons of storing images inside of SQL
Server verses a file server and DB combination (storing the file paths
in SQL). There is a push from my management to store all the images
within a very large database, but something is telling me that it's not
the best way to do it. Unfortunately, I don't have any concrete
experience/evidence to push in one direction verses another.
We are talking about the storage/cataloging of around 4 million images.
Our current image server is file-based and is around 1 tera in size.
The idea of moving all this into a large SQL Server database raises
allot of concern for me.
I guess I would just like some feed-back from others that may have
experience using SQL Server to house a large amount of images. I would
also like to hear if anyone may have pros/cons to one concept verses
another. Any help would be greatly appreciated.http://www.aspfaq.com/show.asp?id=2149
--
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--
"Justin Furch" <jlf@.anon.com> wrote in message
news:%23iW9Zu0wEHA.1512@.TK2MSFTNGP12.phx.gbl...
> I am a semi-experienced DBA, but have some questions regarding the
> storage of images inside of SQL Server (which I have never done before).
> I am researching to pros and cons of storing images inside of SQL
> Server verses a file server and DB combination (storing the file paths
> in SQL). There is a push from my management to store all the images
> within a very large database, but something is telling me that it's not
> the best way to do it. Unfortunately, I don't have any concrete
> experience/evidence to push in one direction verses another.
> We are talking about the storage/cataloging of around 4 million images.
> Our current image server is file-based and is around 1 tera in size.
> The idea of moving all this into a large SQL Server database raises
> allot of concern for me.
> I guess I would just like some feed-back from others that may have
> experience using SQL Server to house a large amount of images. I would
> also like to hear if anyone may have pros/cons to one concept verses
> another. Any help would be greatly appreciated.|||Hello Justin,
We used to have lot of Contracts that needed to be scanned in the insurance
application
and we used FileNET imaging server.
Gopi
"Justin Furch" <jlf@.anon.com> wrote in message
news:%23iW9Zu0wEHA.1512@.TK2MSFTNGP12.phx.gbl...
>I am a semi-experienced DBA, but have some questions regarding the storage
>of images inside of SQL Server (which I have never done before). I am
>researching to pros and cons of storing images inside of SQL Server verses
>a file server and DB combination (storing the file paths in SQL). There is
>a push from my management to store all the images within a very large
>database, but something is telling me that it's not the best way to do it.
>Unfortunately, I don't have any concrete experience/evidence to push in one
>direction verses another.
> We are talking about the storage/cataloging of around 4 million images.
> Our current image server is file-based and is around 1 tera in size. The
> idea of moving all this into a large SQL Server database raises allot of
> concern for me.
> I guess I would just like some feed-back from others that may have
> experience using SQL Server to house a large amount of images. I would
> also like to hear if anyone may have pros/cons to one concept verses
> another. Any help would be greatly appreciated.

iif inside iif

I'd error message on this expression ,

It is written in hidden property of an image

Can you help me to correct it?

thanks all.

=iif(Parameters!Direction.Value = "none", True, iif(Parameters!Direction.Value = "Ascending",True,False )

You are missing a closing ")" and when comparing strings I would use the "equals" method.

Here is what the statement should be:

=iif(Parameters!Direction.Value.equals("none"), True, iif(Parameters!Direction.Value.equals("Ascending"),True,False ))