Showing posts with label alli. Show all posts
Showing posts with label alli. Show all posts

Friday, February 17, 2012

Effects of using Transaction in SP on Performance?

Hi All;
I have a web application which is being used at large scale and there are
upto 10,000 entries per day. Currently, there is no Begin Tran/Commit
Tran/Rollback Tran and b/c of that we found some data corruption. Now, I
changed all the transactional Stored Procedure and used Transaction into
them. Now, I am thinking about the performance of the application when I use
d
Transaction into Stored Procedures which are being used by each user very
frequently. Transaction Lock the objects which might hurt the application
performance. Please, comments on it and should I use Transaction now or not?
Thanks.
Essa, M. Mughal
Software Developer
CanadaYou should DEFINITELY use transactions. Performance penalty or not. There
is no choice here. Data integrity is, by far, the MOST IMPORTANT THING IN A
DATABASE. Sorry for the all caps, but I had to drive it home. Do not
sacrifice your data quality. Otherwise there is very little reason to even
be using a database.
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
--
"Essa" <essamughal@.hotmail.com> wrote in message
news:46BFC928-7375-47ED-AA79-73FE92A45843@.microsoft.com...
> Hi All;
> I have a web application which is being used at large scale and there are
> upto 10,000 entries per day. Currently, there is no Begin Tran/Commit
> Tran/Rollback Tran and b/c of that we found some data corruption. Now, I
> changed all the transactional Stored Procedure and used Transaction into
> them. Now, I am thinking about the performance of the application when I
used
> Transaction into Stored Procedures which are being used by each user very
> frequently. Transaction Lock the objects which might hurt the application
> performance. Please, comments on it and should I use Transaction now or
not?
> Thanks.
> --
> Essa, M. Mughal
> Software Developer
> Canada|||Hi Adam;
Thanks for your strong recommendataion. I really appreciate your way of
conveying me the importance of Data. I have already changed all the
transactional stored procedure but I was just wondering so now I'll go live
with them and then see what happens. I hope nothing will happen but it will
increase data integrity.
Thanks
"Adam Machanic" wrote:

> You should DEFINITELY use transactions. Performance penalty or not. Ther
e
> is no choice here. Data integrity is, by far, the MOST IMPORTANT THING IN
A
> DATABASE. Sorry for the all caps, but I had to drive it home. Do not
> sacrifice your data quality. Otherwise there is very little reason to eve
n
> be using a database.
>
> --
> Adam Machanic
> SQL Server MVP
> http://www.datamanipulation.net
> --
>
> "Essa" <essamughal@.hotmail.com> wrote in message
> news:46BFC928-7375-47ED-AA79-73FE92A45843@.microsoft.com...
> used
> not?
>
>

Effects of using Transaction in SP on Performance?

Hi All;
I have a web application which is being used at large scale and there are
upto 10,000 entries per day. Currently, there is no Begin Tran/Commit
Tran/Rollback Tran and b/c of that we found some data corruption. Now, I
changed all the transactional Stored Procedure and used Transaction into
them. Now, I am thinking about the performance of the application when I used
Transaction into Stored Procedures which are being used by each user very
frequently. Transaction Lock the objects which might hurt the application
performance. Please, comments on it and should I use Transaction now or not?
Thanks.
Essa, M. Mughal
Software Developer
Canada
You should DEFINITELY use transactions. Performance penalty or not. There
is no choice here. Data integrity is, by far, the MOST IMPORTANT THING IN A
DATABASE. Sorry for the all caps, but I had to drive it home. Do not
sacrifice your data quality. Otherwise there is very little reason to even
be using a database.
Adam Machanic
SQL Server MVP
http://www.datamanipulation.net
"Essa" <essamughal@.hotmail.com> wrote in message
news:46BFC928-7375-47ED-AA79-73FE92A45843@.microsoft.com...
> Hi All;
> I have a web application which is being used at large scale and there are
> upto 10,000 entries per day. Currently, there is no Begin Tran/Commit
> Tran/Rollback Tran and b/c of that we found some data corruption. Now, I
> changed all the transactional Stored Procedure and used Transaction into
> them. Now, I am thinking about the performance of the application when I
used
> Transaction into Stored Procedures which are being used by each user very
> frequently. Transaction Lock the objects which might hurt the application
> performance. Please, comments on it and should I use Transaction now or
not?
> Thanks.
> --
> Essa, M. Mughal
> Software Developer
> Canada
|||Hi Adam;
Thanks for your strong recommendataion. I really appreciate your way of
conveying me the importance of Data. I have already changed all the
transactional stored procedure but I was just wondering so now I'll go live
with them and then see what happens. I hope nothing will happen but it will
increase data integrity.
Thanks
"Adam Machanic" wrote:

> You should DEFINITELY use transactions. Performance penalty or not. There
> is no choice here. Data integrity is, by far, the MOST IMPORTANT THING IN A
> DATABASE. Sorry for the all caps, but I had to drive it home. Do not
> sacrifice your data quality. Otherwise there is very little reason to even
> be using a database.
>
> --
> Adam Machanic
> SQL Server MVP
> http://www.datamanipulation.net
> --
>
> "Essa" <essamughal@.hotmail.com> wrote in message
> news:46BFC928-7375-47ED-AA79-73FE92A45843@.microsoft.com...
> used
> not?
>
>

Wednesday, February 15, 2012

Edition Question for Analysis Services

Hi All

I come with Oracle background and we are planning to use SQL Server 2000 Analysis Services for OLAP.

Brief background on our app: The largest of our fact tables has about 500,000 rows per month. We plan to store three years worth of data. We will have other smaller cubes that we will have to build in addition to this. The source data will come from Oracle tables.

I am struggling to decide between the two SQL Server editions (Standard and Enterprise). I'm highlighting the things that I need some help with in order to make the decision:

Memory Limitation
------
Standard Edition only supports up to 2GB. Considering relatively large cube size (is it?), is this a limitation in our case?

Calcualted Cells (only in Enterprise Edition)
------
I didn't fully understand this one in the documentation, not having spent a lot of time. We do have a number of calculations such as the Revenue/Expense, Margin calculations, etc. Is this an important feature that I should consider?

Partitions:
----
I doubt that we will be partitioning across multiple servers (may not need distributed partioning, linked cubes). However, within a single database/instance, do I have the option to partition the cube (does it help to do so for cube manageability) if I went with Standard Edition? Also, given the large fact tables, I may want to incrementally add monthly data to the cube. Would it help to partition the cube in this case and, do I need Enterprise Edition for this?

HTTP Internet Support: (Enterprise Edition only)
-------
I would think that the HTTP access is applicable to intranet applications (ours is one). Does this support in Enterprise Edition automatically means that the data is available for analysis over the web? What tool would I use to access the data (other than the third party tools such as Crystal Analysis, Brio, etc)? I am trying to see what this means and how this relates to my decision on Std Vs Enterprise Editions.

I really appreciate any input you may have on this.

Thanks in advance
Murthy JarugumilliI would suggest to adopt Enterprise Edition as you already know the limitaitons of Standard edition.

In general Standard edition is used as a database server for a small workgroup or department.