I have made several posts regarding my sql2000 cpu mysteriously staying at
100% for 10 minutes at a time. Using a performance monitor, I finally
noticed that during these times there is a sql process that is blocking the
others and causing some kind of "race" condition. The blocked processes
time out, but the blocking process seems to stay blocked often until the
service is restarted. It seems like sql should not allow this. I have not
been able to find out the cause or statements that produced the problem.
The only application using the sql server is an ASP.NET application that
uses 100% stored procedures (no dynamic sql). Does anyone have any
suggestions for finding the cause of process blocking like this? Thanks.Dan,
You'd have to examine the code to determine this.
These may help:
http://www.sql-server-performance.com/sf_block_prevention.asp
and
http://www.support.microsoft.com/?id=224453
and
http://www.support.microsoft.com/?id=271509
and
http://support.microsoft.com/?id=224587
and
http://support.microsoft.com/?id=243589
and
http://support.microsoft.com/?id=243588
HTH
Jerry
"Dan English" <dan_english2@.cox.net> wrote in message
news:eUAAmR4zFHA.2960@.tk2msftngp13.phx.gbl...
>I have made several posts regarding my sql2000 cpu mysteriously staying at
>100% for 10 minutes at a time. Using a performance monitor, I finally
>noticed that during these times there is a sql process that is blocking the
>others and causing some kind of "race" condition. The blocked processes
>time out, but the blocking process seems to stay blocked often until the
>service is restarted. It seems like sql should not allow this. I have
>not been able to find out the cause or statements that produced the
>problem. The only application using the sql server is an ASP.NET
>application that uses 100% stored procedures (no dynamic sql). Does anyone
>have any suggestions for finding the cause of process blocking like this?
>Thanks.
>
Showing posts with label finally. Show all posts
Showing posts with label finally. Show all posts
Monday, March 19, 2012
Wednesday, March 7, 2012
my whole company and customer info/credit cards on the internet
I've been searching for a new ERP solution for my company for a while and I
think I've finally found the best one for us. But now I'm being cautioned
about some things so I need some good arguments about how I should setup the
database server.
The application is written in .net it is a N tiered application (I guess
that's what it's called) and it also has a tightly integrated commerce site.
The system was designed to work best with the app db and commerce db on the
same sql server. Desktop clients can connect by internet access if that
server isn't on the LAN and the website can even connect to the LAN but this
obviously wouldn't work because we're only using DSL here.
I've been cautioned that I shouldn't have internet access on my database
server. I somewhat understand the reasoning for this but to me it seems most
data is about as secure as the applications that access them in the first
place. So even if I had a state of the art network in place, a security flaw
in the app could screw me over regardless.
What is good business security practice for handling/storing sensitive
customer information on the internet and what is overkill/paranoia? This is
a serious questions so I'd appreciate not to be mocked.
I'm not a DBA so maybe I'm a little off on my terms, feel free to correct me
where I'm wrong. But it seems to me that if didn't use the same db server
for both the website and main system I'd have a lot of extra work like
replicating web data to web enabled sql server in our office and from the
"live server" on our LAN and then back again.
Thanks in advance for your advice/criticism/suggestions.
RobertForgot to mention. I was assuming to set it up like this
[dedicated sql server] - the only port enabled on this box is for mssql
would probably use a non default port
[dedicated web/email/application server] ports, email and web/ssl
(25/80/110/443)|||Normally what you do is expose the middle-tier (or even yet another system)
to the Internet, and then you only allow that system to connect to your
database server. Yes, if that system is compromised, there can also be
issues, but if you code correctly the only things exposed would be those tha
t
stored procedures or view expose. There are several good books on designing
secure web applications, so I suggest you check out your local bookstore for
one that fits your style.
"Rob" wrote:
> I've been searching for a new ERP solution for my company for a while and
I
> think I've finally found the best one for us. But now I'm being cautioned
> about some things so I need some good arguments about how I should setup t
he
> database server.
> The application is written in .net it is a N tiered application (I guess
> that's what it's called) and it also has a tightly integrated commerce sit
e.
> The system was designed to work best with the app db and commerce db on th
e
> same sql server. Desktop clients can connect by internet access if that
> server isn't on the LAN and the website can even connect to the LAN but th
is
> obviously wouldn't work because we're only using DSL here.
> I've been cautioned that I shouldn't have internet access on my database
> server. I somewhat understand the reasoning for this but to me it seems mo
st
> data is about as secure as the applications that access them in the first
> place. So even if I had a state of the art network in place, a security fl
aw
> in the app could screw me over regardless.
> What is good business security practice for handling/storing sensitive
> customer information on the internet and what is overkill/paranoia? This i
s
> a serious questions so I'd appreciate not to be mocked.
> I'm not a DBA so maybe I'm a little off on my terms, feel free to correct
me
> where I'm wrong. But it seems to me that if didn't use the same db server
> for both the website and main system I'd have a lot of extra work like
> replicating web data to web enabled sql server in our office and from the
> "live server" on our LAN and then back again.
> Thanks in advance for your advice/criticism/suggestions.
> Robert
>
>
think I've finally found the best one for us. But now I'm being cautioned
about some things so I need some good arguments about how I should setup the
database server.
The application is written in .net it is a N tiered application (I guess
that's what it's called) and it also has a tightly integrated commerce site.
The system was designed to work best with the app db and commerce db on the
same sql server. Desktop clients can connect by internet access if that
server isn't on the LAN and the website can even connect to the LAN but this
obviously wouldn't work because we're only using DSL here.
I've been cautioned that I shouldn't have internet access on my database
server. I somewhat understand the reasoning for this but to me it seems most
data is about as secure as the applications that access them in the first
place. So even if I had a state of the art network in place, a security flaw
in the app could screw me over regardless.
What is good business security practice for handling/storing sensitive
customer information on the internet and what is overkill/paranoia? This is
a serious questions so I'd appreciate not to be mocked.
I'm not a DBA so maybe I'm a little off on my terms, feel free to correct me
where I'm wrong. But it seems to me that if didn't use the same db server
for both the website and main system I'd have a lot of extra work like
replicating web data to web enabled sql server in our office and from the
"live server" on our LAN and then back again.
Thanks in advance for your advice/criticism/suggestions.
RobertForgot to mention. I was assuming to set it up like this
[dedicated sql server] - the only port enabled on this box is for mssql
would probably use a non default port
[dedicated web/email/application server] ports, email and web/ssl
(25/80/110/443)|||Normally what you do is expose the middle-tier (or even yet another system)
to the Internet, and then you only allow that system to connect to your
database server. Yes, if that system is compromised, there can also be
issues, but if you code correctly the only things exposed would be those tha
t
stored procedures or view expose. There are several good books on designing
secure web applications, so I suggest you check out your local bookstore for
one that fits your style.
"Rob" wrote:
> I've been searching for a new ERP solution for my company for a while and
I
> think I've finally found the best one for us. But now I'm being cautioned
> about some things so I need some good arguments about how I should setup t
he
> database server.
> The application is written in .net it is a N tiered application (I guess
> that's what it's called) and it also has a tightly integrated commerce sit
e.
> The system was designed to work best with the app db and commerce db on th
e
> same sql server. Desktop clients can connect by internet access if that
> server isn't on the LAN and the website can even connect to the LAN but th
is
> obviously wouldn't work because we're only using DSL here.
> I've been cautioned that I shouldn't have internet access on my database
> server. I somewhat understand the reasoning for this but to me it seems mo
st
> data is about as secure as the applications that access them in the first
> place. So even if I had a state of the art network in place, a security fl
aw
> in the app could screw me over regardless.
> What is good business security practice for handling/storing sensitive
> customer information on the internet and what is overkill/paranoia? This i
s
> a serious questions so I'd appreciate not to be mocked.
> I'm not a DBA so maybe I'm a little off on my terms, feel free to correct
me
> where I'm wrong. But it seems to me that if didn't use the same db server
> for both the website and main system I'd have a lot of extra work like
> replicating web data to web enabled sql server in our office and from the
> "live server" on our LAN and then back again.
> Thanks in advance for your advice/criticism/suggestions.
> Robert
>
>
My Very Own SOAP / Web Service Report Viewer
Well, I've finally done it! The first fully functional prototype of the
report viewer control for Reporting Services 2000 is complete. I am
working on a project that cannot wait until RS 2005, so we bit the
bullet and wrote our own component (URL access will not work for a
number of reasons).
Alon with report selection, I have implemented:
1) Parameter selection (including linked params)
2) Page navigation
3) Zooming
4) Refresh
5) Export to: PDF, Excel, CSV, TIFF, XML, MHTML
6) Printing
I have received a lot of help from the RS community, so may thanks to
those of you who frequent this group!
Kulgan.Congratulations!
I have been struggling to build one too. Would you mind sharing your
code/ideas on how to go on about it?
TIA.
Marlon
"Kulgan" <nickamckenna@.gmail.com> wrote in message
news:1121180309.308222.314710@.g43g2000cwa.googlegroups.com...
> Well, I've finally done it! The first fully functional prototype of the
> report viewer control for Reporting Services 2000 is complete. I am
> working on a project that cannot wait until RS 2005, so we bit the
> bullet and wrote our own component (URL access will not work for a
> number of reasons).
> Alon with report selection, I have implemented:
> 1) Parameter selection (including linked params)
> 2) Page navigation
> 3) Zooming
> 4) Refresh
> 5) Export to: PDF, Excel, CSV, TIFF, XML, MHTML
> 6) Printing
> I have received a lot of help from the RS community, so may thanks to
> those of you who frequent this group!
> Kulgan.
>|||Unfortunately the code belongs to the client I have done the work for,
but I will be doing an open source version shortly (when I return from
holiday in a couple of weeks).
I will keep you posted!
In the meantime, if you get stuck, email me and I'll help wherever I
can.
Cheers,
Kulgan.|||Yes, thats great! I have the exact same issue that I need to resolve, i.e.
using the viewer through SOAP. I would love to see how you did this!
"TechnoSpyke" wrote:
> Congratulations!
> I have been struggling to build one too. Would you mind sharing your
> code/ideas on how to go on about it?
> TIA.
> Marlon
> "Kulgan" <nickamckenna@.gmail.com> wrote in message
> news:1121180309.308222.314710@.g43g2000cwa.googlegroups.com...
> > Well, I've finally done it! The first fully functional prototype of the
> > report viewer control for Reporting Services 2000 is complete. I am
> > working on a project that cannot wait until RS 2005, so we bit the
> > bullet and wrote our own component (URL access will not work for a
> > number of reasons).
> >
> > Alon with report selection, I have implemented:
> >
> > 1) Parameter selection (including linked params)
> > 2) Page navigation
> > 3) Zooming
> > 4) Refresh
> > 5) Export to: PDF, Excel, CSV, TIFF, XML, MHTML
> > 6) Printing
> >
> > I have received a lot of help from the RS community, so may thanks to
> > those of you who frequent this group!
> >
> > Kulgan.
> >
>
>|||Me too.
tnx.
Tom.
report viewer control for Reporting Services 2000 is complete. I am
working on a project that cannot wait until RS 2005, so we bit the
bullet and wrote our own component (URL access will not work for a
number of reasons).
Alon with report selection, I have implemented:
1) Parameter selection (including linked params)
2) Page navigation
3) Zooming
4) Refresh
5) Export to: PDF, Excel, CSV, TIFF, XML, MHTML
6) Printing
I have received a lot of help from the RS community, so may thanks to
those of you who frequent this group!
Kulgan.Congratulations!
I have been struggling to build one too. Would you mind sharing your
code/ideas on how to go on about it?
TIA.
Marlon
"Kulgan" <nickamckenna@.gmail.com> wrote in message
news:1121180309.308222.314710@.g43g2000cwa.googlegroups.com...
> Well, I've finally done it! The first fully functional prototype of the
> report viewer control for Reporting Services 2000 is complete. I am
> working on a project that cannot wait until RS 2005, so we bit the
> bullet and wrote our own component (URL access will not work for a
> number of reasons).
> Alon with report selection, I have implemented:
> 1) Parameter selection (including linked params)
> 2) Page navigation
> 3) Zooming
> 4) Refresh
> 5) Export to: PDF, Excel, CSV, TIFF, XML, MHTML
> 6) Printing
> I have received a lot of help from the RS community, so may thanks to
> those of you who frequent this group!
> Kulgan.
>|||Unfortunately the code belongs to the client I have done the work for,
but I will be doing an open source version shortly (when I return from
holiday in a couple of weeks).
I will keep you posted!
In the meantime, if you get stuck, email me and I'll help wherever I
can.
Cheers,
Kulgan.|||Yes, thats great! I have the exact same issue that I need to resolve, i.e.
using the viewer through SOAP. I would love to see how you did this!
"TechnoSpyke" wrote:
> Congratulations!
> I have been struggling to build one too. Would you mind sharing your
> code/ideas on how to go on about it?
> TIA.
> Marlon
> "Kulgan" <nickamckenna@.gmail.com> wrote in message
> news:1121180309.308222.314710@.g43g2000cwa.googlegroups.com...
> > Well, I've finally done it! The first fully functional prototype of the
> > report viewer control for Reporting Services 2000 is complete. I am
> > working on a project that cannot wait until RS 2005, so we bit the
> > bullet and wrote our own component (URL access will not work for a
> > number of reasons).
> >
> > Alon with report selection, I have implemented:
> >
> > 1) Parameter selection (including linked params)
> > 2) Page navigation
> > 3) Zooming
> > 4) Refresh
> > 5) Export to: PDF, Excel, CSV, TIFF, XML, MHTML
> > 6) Printing
> >
> > I have received a lot of help from the RS community, so may thanks to
> > those of you who frequent this group!
> >
> > Kulgan.
> >
>
>|||Me too.
tnx.
Tom.
Subscribe to:
Posts (Atom)