Increase number of process(thread)

Hello all,

A software that connects SQL Server via ODBC uses 12 process at the same
time when I look at the process info(panel). Is it possible to increase
number of process (or thread) for a specific database? Is there any
parameter?

Thanks in advance,
Do.

--
Message posted via http://www.sqlmonster.comDo Park via SQLMonster.com (forum@.nospam.SQLMonster.com) writes:
> A software that connects SQL Server via ODBC uses 12 process at the same
> time when I look at the process info(panel). Is it possible to increase
> number of process (or thread) for a specific database? Is there any
> parameter?

You can change the number of permitted connections with

sp_configure 'user connections', 100 -- 100 is an example here

This is a server-wide setting. There is no per-database setting for this
(and neither would it be really meaningful).

However, the default for this option is 0, which means that the server
configures as it goes on.

Are you getting any error messages about running out of connections?

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||
Do Park via SQLMonster.com wrote:
> Hello all,
> A software that connects SQL Server via ODBC uses 12 process at the same
> time when I look at the process info(panel). Is it possible to increase
> number of process (or thread) for a specific database? Is there any
> parameter?
> Thanks in advance,
> Do.
> --
> Message posted via http://www.sqlmonster.com

You will find that this is a programed function of the software itself,
not SQL Server.

See if there is a configuration setting you can use to adjust it.

You could also download a copy of the database monitor I have developed
which will tell you what load the software application is having on the
server. This will help determine if it is safe to up the number of
connections or not. It will also tell you if they are locking
themselves out.

You can download it from http://dbmonitor.tripod.com.

Incorrect Schedule Displayed

Hi,
I am creating a data driven subscription via code using a shared schedule
and it seems fine, but when I view the subscription in Report Manager it
shows the wrong schedule.
I have checked the MatchData field in the Subscriptions table and the
ScheduleID in the ReportSchedules table and both of these have the correct
ID.
any ideas?
thanks
MattOh, I should add that the subscription runs correctly. It just displays a
different schedule to the one I have assigned on the "Specify When the
subscription is processed." page. Note, if I set the schedule here, it
seems to remember it.
thanks again
"Matt" <NoSpam:Matthew.Moran@.Computercorp.com.au> wrote in message
news:O40uAJ2gEHA.712@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I am creating a data driven subscription via code using a shared schedule
> and it seems fine, but when I view the subscription in Report Manager it
> shows the wrong schedule.
> I have checked the MatchData field in the Subscriptions table and the
> ScheduleID in the ReportSchedules table and both of these have the correct
> ID.
> any ideas?
> thanks
> Matt
>|||Is it possible for you to share your code? You can send it directly to me
if you want and I can take a look. Just remove the online from my address.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Matt" <NoSpam:Matthew.Moran@.Computercorp.com.au> wrote in message
news:#NVQ#z2gEHA.1972@.TK2MSFTNGP09.phx.gbl...
> Oh, I should add that the subscription runs correctly. It just displays a
> different schedule to the one I have assigned on the "Specify When the
> subscription is processed." page. Note, if I set the schedule here, it
> seems to remember it.
> thanks again
>
> "Matt" <NoSpam:Matthew.Moran@.Computercorp.com.au> wrote in message
> news:O40uAJ2gEHA.712@.TK2MSFTNGP09.phx.gbl...
> > Hi,
> >
> > I am creating a data driven subscription via code using a shared
schedule
> > and it seems fine, but when I view the subscription in Report Manager it
> > shows the wrong schedule.
> >
> > I have checked the MatchData field in the Subscriptions table and the
> > ScheduleID in the ReportSchedules table and both of these have the
correct
> > ID.
> >
> > any ideas?
> >
> > thanks
> >
> > Matt
> >
> >
>

Incorrect Information in SQL Agent\Operator History

Apologies if this is in the wrong forum.

I've set up an email alert to an Operator who can only be alerted via email. When i view the history of this operator, it has a "most recent notification attempt" value against by net send and not against by e-mail. The value is the correct date of the latest email alert, but is just set against the wrong notification type.

Not a major bug for me, but does anyone else have this problem?

--

DDL statement for operator.

EXEC msdb.dbo.sp_add_operator @.name=N'Rich',

@.enabled=1,

@.weekday_pager_start_time=90000,

@.weekday_pager_end_time=180000,

@.saturday_pager_start_time=90000,

@.saturday_pager_end_time=180000,

@.sunday_pager_start_time=90000,

@.sunday_pager_end_time=180000,

@.pager_days=0,

@.email_address=N'rich@.rich.net,

@.category_name=N'[Uncategorized]'

Yup.

Same problem here.

Rob

|||

There is a hotfix for this.

I couldn't find the link, but I've been researching the hotfixes for some of the problems I've been having, and this was definately one of them.

|||

This issue still exists in SQL2005 Standard 9.00.3042.00. Its been raised as a bug (#124871) back in Feb 2006 but is still present.

Does anyone know if\when this is going to be fixed for good? I've not seen any hotfix information regarding it.

(Please move to the Tools forum)

Incorrect Information in SQL Agent\Operator History

Apologies if this is in the wrong forum.

I've set up an email alert to an Operator who can only be alerted via email. When i view the history of this operator, it has a "most recent notification attempt" value against by net send and not against by e-mail. The value is the correct date of the latest email alert, but is just set against the wrong notification type.

Not a major bug for me, but does anyone else have this problem?

--

DDL statement for operator.

EXEC msdb.dbo.sp_add_operator @.name=N'Rich',

@.enabled=1,

@.weekday_pager_start_time=90000,

@.weekday_pager_end_time=180000,

@.saturday_pager_start_time=90000,

@.saturday_pager_end_time=180000,

@.sunday_pager_start_time=90000,

@.sunday_pager_end_time=180000,

@.pager_days=0,

@.email_address=N'rich@.rich.net,

@.category_name=N'[Uncategorized]'

Yup.

Same problem here.

Rob

|||

There is a hotfix for this.

I couldn't find the link, but I've been researching the hotfixes for some of the problems I've been having, and this was definately one of them.

|||

This issue still exists in SQL2005 Standard 9.00.3042.00. Its been raised as a bug (#124871) back in Feb 2006 but is still present.

Does anyone know if\when this is going to be fixed for good? I've not seen any hotfix information regarding it.

(Please move to the Tools forum)

Incorrect Information in SQL Agent\Operator History

Apologies if this is in the wrong forum.

I've set up an email alert to an Operator who can only be alerted via email. When i view the history of this operator, it has a "most recent notification attempt" value against by net send and not against by e-mail. The value is the correct date of the latest email alert, but is just set against the wrong notification type.

Not a major bug for me, but does anyone else have this problem?

--

DDL statement for operator.

EXEC msdb.dbo.sp_add_operator @.name=N'Rich',

@.enabled=1,

@.weekday_pager_start_time=90000,

@.weekday_pager_end_time=180000,

@.saturday_pager_start_time=90000,

@.saturday_pager_end_time=180000,

@.sunday_pager_start_time=90000,

@.sunday_pager_end_time=180000,

@.pager_days=0,

@.email_address=N'rich@.rich.net,

@.category_name=N'[Uncategorized]'

Yup.

Same problem here.

Rob

|||

There is a hotfix for this.

I couldn't find the link, but I've been researching the hotfixes for some of the problems I've been having, and this was definately one of them.

|||

This issue still exists in SQL2005 Standard 9.00.3042.00. Its been raised as a bug (#124871) back in Feb 2006 but is still present.

Does anyone know if\when this is going to be fixed for good? I've not seen any hotfix information regarding it.

(Please move to the Tools forum)

incorrect format of date report parameters via datepicker

OK - truck loads of folk have reported this problem - but I cannot solve it - so apologies for repeating the question...

My SQL Server 2005 Report is developed on the same server as it is run.

I have SQL Server 2005 SP2 installed. The report language is set as en-GB.

The browser language setting is en-NZ.

The report previews fine - I pick May 22 from the picker and it appears as 22/05/2007 in the report parameter text box - which since I am in NZ is exactly as I want it.

I deploy the report - If I run it from the report manager virtual directory the date picker performs as above i.e correctly.

I run the deployed report from the report server virtual directory and here is where the problem occurs - selecting May 22 from the date picker produces 05/22/2007 in the report parameter text box and produces the error

"The value provided for the report parameter 'StartScheduledDate' is not valid for its type. (rsReportParameterTypeMismatch)"

thanks for any help here - this problem has made this a ridiculously expensive report!

honestbob wrote:

I deploy the report - If I run it from the report manager virtual directory the date picker performs as above i.e correctly.

I run the deployed report from the report server virtual directory and here is where the problem occurs

Pardon me, what's the difference between the 2 sentenses? They both sound like you run from http://localhost/Reports?

I'd suggest looking at the Regional settings in your machine, and server, to make sure they're the same

e.g. Canada default is DD/MM/YYYY, while USA default is MM/DD/YYYY

|||

bob,

what i have done with this in the past is always do a CDate() on the output of the calendar control before trying to use that output, then i can Format() it any way i like. I also found when trying to force it to a non-US date format i couldn't then use the Preview tab in the IDE to check my report, as that version of the control insists on rendering/outputting everything in US format, regardless of what culture you have your report/IE/server set to.

So in summary, i find the web version of that control works fine if you CDate everything before using it. And like the previous poster said, check the regional settings on your report server.

|||

I was having the same problem but i managed to fix it.

edit the file "ReportViewer.aspx" on the reporting services machine.

it's in the "C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer\Pages" by default,

and add the highlighted part with the desired culture value.

It solved the problem in my case.

<%@. Register TagPrefix="RS" Namespace="Microsoft.ReportingServices.WebServer" Assembly="ReportingServicesWebServer" %>

<%@. Page Language="C#" AutoEventWireup="true" Inherits="Microsoft.ReportingServices.WebServer.ReportViewerPage" Culture="pt-PT"%>

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>

<head id="headID" runat="server">

<title>Report Viewer</title>

</head>

<body style="margin: 0px; overflow: auto">

<form runat="server" ID="ReportViewerForm">

<RS:ReportViewerHost ID="ReportViewerControl" runat="server" />

</form>

</body>

</html>

Hope this will solve your problem too.

Tiago Certal

|||

yes, that solved my problem too. I, too have tried fiddling with the regional settings on the database, the server, the local, the client computers etc. I would keep having the problem in IE, but not in Firefox. Firefox was fine.

so I tried to add the culture thing in, like Tiago suggested. only problem is that I think PT is portugese, so I had to use "en-CA" instead. Which then magically made the reports displayable in IE. Thank you Tiago!

problem is that now Firefox is having the same error. WHAT IS GOING ON?

inconsistent Timeout Expired with extended SP execute

All,
I've successfully executed my extended stored proc multiple times via
the following. If I directly execute(e.g., right-click 'Execute'
within my DB editor) this stored procedure, it runs everytime and
finishes in 1-2 seconds. If I try to execute the SP via my trigger, it
returns a 'Timeout Expired' message. But - not every time. I have got
the trigger to fire the SP a few (seemingly random) times without
timing out. Any help would be fantastic...
Pre-Thanks,
sara
my SP:
ALTER procedure dbo.WriteDNFiles
as
declare @.return varchar
EXEC @.return = master.dbo.XYRunProc 'C:\WRITE_DN_FILES.exe'
my trigger:
ALTER TRIGGER TriggerEmp
ON dbo.Employees
FOR INSERT, UPDATE
AS
exec WriteDNFilesHi sara
Running a program in a trigger is not a good idea as it will prolong the
transaction and there increase contention which could possibly be what you
are experiencing. You may want to make sure that you are not having any file
access problems if two process are wanting to call the program simultanously.
Another general point is that you should change @.@.ROWCOUNT in the trigger to
see if anything has changed, if not don't call your procedure.
John
"skeddy@.gmail.com" wrote:
> All,
> I've successfully executed my extended stored proc multiple times via
> the following. If I directly execute(e.g., right-click 'Execute'
> within my DB editor) this stored procedure, it runs everytime and
> finishes in 1-2 seconds. If I try to execute the SP via my trigger, it
> returns a 'Timeout Expired' message. But - not every time. I have got
> the trigger to fire the SP a few (seemingly random) times without
> timing out. Any help would be fantastic...
> Pre-Thanks,
> sara
> my SP:
> ALTER procedure dbo.WriteDNFiles
> as
> declare @.return varchar
> EXEC @.return = master.dbo.XYRunProc 'C:\WRITE_DN_FILES.exe'
> my trigger:
> ALTER TRIGGER TriggerEmp
> ON dbo.Employees
> FOR INSERT, UPDATE
> AS
> exec WriteDNFiles
>