connection pooling

Hello, I would like to keep my connection from RS to database open all the
time.. I noticed that when I try to render a report for the first time
(called from .aspx page ) it takes a few seconds before it actually executes.
Each report rendered shortly after comes back in no time. I understand this
is related to how connection pooling is being handled.
Could someone please explain how exactly it works. I have a site that
doesn't have much activity, but when someone goes and tries to render report,
I don't want them to get wrong impression that it is slow. I would like to
keep connection between RS and the database alive all the time.. Is that
possible?
Regards,You are seeing an issue with IIS and RS (RS is an asp.net application). This
pause has nothing to do with connection pooling.
There is one solution that people have tried but for whatever reason it did
not do it for me. So I'll tell you what has been said is the solution and
then I'll tell you my hack.
Solution via a poster named Chris:
>>>>>>>>
If you are running Windows 2003 server for your IIS reportserver, then this
is a simple issue - I'll explain what happens:
The report service engine, once it is idle for more than the default 20
minutes, the worker process is shutdown.
This is controlled by IIS.
Open up the Internet Information Services (IIS) Manager
Expand the server node then the application pools.
On my IIS machine, I created an application pool dedicated to the
reportserver & reportmanager virtual webs.
But anyways, for the application pool that the reportserver is pointing to
if you left everything to their defaults will be the DefaultAppPool.
Right click the default app pool and select properties.
There are two things that are checked by default - On the recycling tab
there is a checkbox for recycling worker processes - it is currently set to
1740 minutes (29 hours). Leave it.
The other one is on the performance tab - which is the one you are
interested in changing...
See the "Idle Timeout" section and increase the number of minutes to be 8
hours a typical working day - 8*60 = 480 minutes.
Next, to be sure the "morning person" that runs the first report doesn't get
the delay, set up a schedule for either a dummy or adhoc report to fire off
like at 6am so that the report component worker processes get loaded.
I hope this helps you.
There is no need to have a report fire off every minute to keep things
alive - it is just that the report service was "unloaded" and needed to load
back up.
>>>>>>>>>>>>>>>>>>>
OK, I still ended up doing my hack.
Take a simple report (or make one), set the autorefresh (report->properties)
to 300 seconds. Open this report up and just leave it up. Every five minutes
it will run. This will prevent the problem you are seeing.
I have reports in a folder other people don't use but you could also create
a report just for this and hide it in list view so others don't run it.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lucjan" <Lucjan@.discussions.microsoft.com> wrote in message
news:D2AF4C54-2224-4FF5-8112-F0C8960420BC@.microsoft.com...
> Hello, I would like to keep my connection from RS to database open all the
> time.. I noticed that when I try to render a report for the first time
> (called from .aspx page ) it takes a few seconds before it actually
> executes.
> Each report rendered shortly after comes back in no time. I understand
> this
> is related to how connection pooling is being handled.
> Could someone please explain how exactly it works. I have a site that
> doesn't have much activity, but when someone goes and tries to render
> report,
> I don't want them to get wrong impression that it is slow. I would like to
> keep connection between RS and the database alive all the time.. Is that
> possible?
> Regards,
>
>

Connection Leak

Hi,
I have troubles with a threaded application on W2003 server. It
seems to leave open connections behind time to time, it sums to hundreds over
a day (the application make thousands). It is using the SQLOLEDB provider,
MDAC 2.82.1830.0, SQL Server 8.00.2039 (SP4), Windows 5.2 (3790).
I put two Trace (print) statements : (1) Connection is opened. 2)
Connection is Closed.) I can see the two statements without any Exception.
But the problem is when I see on the Performance viewer (perfmon.exe/ perfmon.
msc->Sqlserver:General Statistics, User Connections) it shows Number of users
connected to the system is like thousands and more day by day ,Means the
number of open connections are in Hundreds…thousands and more . I am also
loosing the connections immediately with out any exception.
But still I am seeing open connection.
Please can anybody sort out my problem,
Is there a known bug like this? Is there a way to trace the SQLOLEDB provider?
Regards,
Rasheeds
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200612/1
"malkeshsheth via droptable.com" <u13567@.uwe> wrote in message
news:6b18cb6b1bfe5@.uwe...
> Hi,
> I have troubles with a threaded application on W2003 server. It
> seems to leave open connections behind time to time, it sums to hundreds
> over
> a day (the application make thousands). It is using the SQLOLEDB provider,
> MDAC 2.82.1830.0, SQL Server 8.00.2039 (SP4), Windows 5.2 (3790).
> I put two Trace (print) statements : (1) Connection is opened.
> 2)
> Connection is Closed.) I can see the two statements without any Exception.
> But the problem is when I see on the Performance viewer (perfmon.exe/
> perfmon.
> msc->Sqlserver:General Statistics, User Connections) it shows Number of
> users
> connected to the system is like thousands and more day by day ,Means the
> number of open connections are in Hundreds…thousands and more . I am also
> loosing the connections immediately with out any exception.
> But still I am seeing open connection.
> Please can anybody sort out my problem,
> Is there a known bug like this? Is there a way to trace the SQLOLEDB
> provider?
>
Sounds like OleDb Session Pooling.
|||"malkeshsheth via droptable.com" <u13567@.uwe> wrote in message
news:6b18cb6b1bfe5@.uwe...
> Hi,
> I have troubles with a threaded application on W2003 server. It
> seems to leave open connections behind time to time, it sums to hundreds
> over
> a day (the application make thousands). It is using the SQLOLEDB provider,
> MDAC 2.82.1830.0, SQL Server 8.00.2039 (SP4), Windows 5.2 (3790).
> I put two Trace (print) statements : (1) Connection is opened.
> 2)
> Connection is Closed.) I can see the two statements without any Exception.
> But the problem is when I see on the Performance viewer (perfmon.exe/
> perfmon.
> msc->Sqlserver:General Statistics, User Connections) it shows Number of
> users
> connected to the system is like thousands and more day by day ,Means the
> number of open connections are in Hundreds…thousands and more . I am also
> loosing the connections immediately with out any exception.
> But still I am seeing open connection.
> Please can anybody sort out my problem,
> Is there a known bug like this? Is there a way to trace the SQLOLEDB
> provider?
>
OOPS.
Sounds like you're using Connection Pooling (or whatever they call it in
OleDb)
See, eg
Support WebCast: ODBC Connection Pooling and OLEDB Session Pooling in
Microsoft Data Access Components
http://support.microsoft.com/kb/324686
David

Connection Leak

Hi,
I have troubles with a threaded application on W2003 server. It
seems to leave open connections behind time to time, it sums to hundreds ove
r
a day (the application make thousands). It is using the SQLOLEDB provider,
MDAC 2.82.1830.0, SQL Server 8.00.2039 (SP4), Windows 5.2 (3790).
I put two Trace (print) statements : (1) Connection is opened. 2)
Connection is Closed.) I can see the two statements without any Exception.
But the problem is when I see on the Performance viewer (perfmon.exe/ perfmo
n.
msc->Sqlserver:General Statistics, User Connections) it shows Number of user
s
connected to the system is like thousands and more day by day ,Means the
number of open connections are in Hundreds…thousands and more . I am also
loosing the connections immediately with out any exception.
But still I am seeing open connection.
Please can anybody sort out my problem,
Is there a known bug like this? Is there a way to trace the SQLOLEDB provide
r?
Regards,
Rasheeds
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200612/1"malkeshsheth via droptable.com" <u13567@.uwe> wrote in message
news:6b18cb6b1bfe5@.uwe...
> Hi,
> I have troubles with a threaded application on W2003 server. It
> seems to leave open connections behind time to time, it sums to hundreds
> over
> a day (the application make thousands). It is using the SQLOLEDB provider,
> MDAC 2.82.1830.0, SQL Server 8.00.2039 (SP4), Windows 5.2 (3790).
> I put two Trace (print) statements : (1) Connection is opened.
> 2)
> Connection is Closed.) I can see the two statements without any Exception.
> But the problem is when I see on the Performance viewer (perfmon.exe/
> perfmon.
> msc->Sqlserver:General Statistics, User Connections) it shows Number of
> users
> connected to the system is like thousands and more day by day ,Means the
> number of open connections are in Hundreds…thousands and more . I am als
o
> loosing the connections immediately with out any exception.
> But still I am seeing open connection.
> Please can anybody sort out my problem,
> Is there a known bug like this? Is there a way to trace the SQLOLEDB
> provider?
>
Sounds like OleDb Session Pooling.|||"malkeshsheth via droptable.com" <u13567@.uwe> wrote in message
news:6b18cb6b1bfe5@.uwe...
> Hi,
> I have troubles with a threaded application on W2003 server. It
> seems to leave open connections behind time to time, it sums to hundreds
> over
> a day (the application make thousands). It is using the SQLOLEDB provider,
> MDAC 2.82.1830.0, SQL Server 8.00.2039 (SP4), Windows 5.2 (3790).
> I put two Trace (print) statements : (1) Connection is opened.
> 2)
> Connection is Closed.) I can see the two statements without any Exception.
> But the problem is when I see on the Performance viewer (perfmon.exe/
> perfmon.
> msc->Sqlserver:General Statistics, User Connections) it shows Number of
> users
> connected to the system is like thousands and more day by day ,Means the
> number of open connections are in Hundreds…thousands and more . I am als
o
> loosing the connections immediately with out any exception.
> But still I am seeing open connection.
> Please can anybody sort out my problem,
> Is there a known bug like this? Is there a way to trace the SQLOLEDB
> provider?
>
OOPS.
Sounds like you're using Connection Pooling (or whatever they call it in
OleDb)
See, eg
Support WebCast: ODBC Connection Pooling and OLEDB Session Pooling in
Microsoft Data Access Components
http://support.microsoft.com/kb/324686
David

Connection Leak

Hi,
I have troubles with a threaded application on W2003 server. It
seems to leave open connections behind time to time, it sums to hundreds over
a day (the application make thousands). It is using the SQLOLEDB provider,
MDAC 2.82.1830.0, SQL Server 8.00.2039 (SP4), Windows 5.2 (3790).
I put two Trace (print) statements : (1) Connection is opened. 2)
Connection is Closed.) I can see the two statements without any Exception.
But the problem is when I see on the Performance viewer (perfmon.exe/ perfmon.
msc->Sqlserver:General Statistics, User Connections) it shows Number of users
connected to the system is like thousands and more day by day ,Means the
number of open connections are in Hundredsâ?¦thousands and more . I am also
loosing the connections immediately with out any exception.
But still I am seeing open connection.
Please can anybody sort out my problem,
Is there a known bug like this? Is there a way to trace the SQLOLEDB provider?
Regards,
Rasheeds
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200612/1"malkeshsheth via SQLMonster.com" <u13567@.uwe> wrote in message
news:6b18cb6b1bfe5@.uwe...
> Hi,
> I have troubles with a threaded application on W2003 server. It
> seems to leave open connections behind time to time, it sums to hundreds
> over
> a day (the application make thousands). It is using the SQLOLEDB provider,
> MDAC 2.82.1830.0, SQL Server 8.00.2039 (SP4), Windows 5.2 (3790).
> I put two Trace (print) statements : (1) Connection is opened.
> 2)
> Connection is Closed.) I can see the two statements without any Exception.
> But the problem is when I see on the Performance viewer (perfmon.exe/
> perfmon.
> msc->Sqlserver:General Statistics, User Connections) it shows Number of
> users
> connected to the system is like thousands and more day by day ,Means the
> number of open connections are in Hundredsâ?¦thousands and more . I am also
> loosing the connections immediately with out any exception.
> But still I am seeing open connection.
> Please can anybody sort out my problem,
> Is there a known bug like this? Is there a way to trace the SQLOLEDB
> provider?
>
Sounds like OleDb Session Pooling.|||"malkeshsheth via SQLMonster.com" <u13567@.uwe> wrote in message
news:6b18cb6b1bfe5@.uwe...
> Hi,
> I have troubles with a threaded application on W2003 server. It
> seems to leave open connections behind time to time, it sums to hundreds
> over
> a day (the application make thousands). It is using the SQLOLEDB provider,
> MDAC 2.82.1830.0, SQL Server 8.00.2039 (SP4), Windows 5.2 (3790).
> I put two Trace (print) statements : (1) Connection is opened.
> 2)
> Connection is Closed.) I can see the two statements without any Exception.
> But the problem is when I see on the Performance viewer (perfmon.exe/
> perfmon.
> msc->Sqlserver:General Statistics, User Connections) it shows Number of
> users
> connected to the system is like thousands and more day by day ,Means the
> number of open connections are in Hundredsâ?¦thousands and more . I am also
> loosing the connections immediately with out any exception.
> But still I am seeing open connection.
> Please can anybody sort out my problem,
> Is there a known bug like this? Is there a way to trace the SQLOLEDB
> provider?
>
OOPS.
Sounds like you're using Connection Pooling (or whatever they call it in
OleDb)
See, eg
Support WebCast: ODBC Connection Pooling and OLEDB Session Pooling in
Microsoft Data Access Components
http://support.microsoft.com/kb/324686
David|||Yes David,
i hope you are correct !!!! So do you tell me. Is there any such issue or my
program has any fault?
if my program is wrong then same connection leak problem has to shown on my
machine, but it shown on client machine. So can you suggest me to resolve
such issues in which aria I have to concentrate?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200612/1

Connection in vb 6.0 app

Ok first time poster here. I am very inexperienced with SQL and most all programs I am trying to use, lol. Taking on too much too soon I guess. Ok, I am having a problem in VB but I think it has to do something with a setting I have in SQL server. here it is. I am trying to make a connection to a databasae using this code in VB

ConnectString = "Provider=MSDASQL.1;Password=password;Persist Security Info=True;User ID=sa;Data Source=mas500_app;Initial Catalog="

It is giving me a data source not found and no default driver specified. I know for a fact that this is the correct name for the database. Another mock database i created works fine. So what could be the problem. Is there something in SQL Server that i need to tweak in order for VB to open this connection? Any help would be greatly appreciated and a round of beers would seem to be in order as well. thanks alot.ConnectString = "Provider=MSDASQL.1;Password=password;Persist Security Info=True;User ID=sa;Data Source=mas500_app;Initial Catalog="

You haven't mentioned the Initial Catalog.OK first of all check these things.
1.Make sure that User and password are correct.
2.Check the server name.
Try this one ...
Provider=SQLOLEDB.1;Persist Security Info=true;User ID=sa;Password=password;Initial Catalog=Test
I hope this will solve your problem.
Joydeep|||Hi

I am not 100% on this however I believe that MSDASQL.1 is now considered obsolete. I have certainly never used it. I have certainly seen things on the web re bugs and slow running using this provider. Have a look at http://www.connectionstrings.com/ and see if you can improve things.

HTH|||Hmm - not sure if this is the very same thing but:
http://www.carlprothman.net/Default.aspx?tabid=87#OLEDBProviderForODBCDatabase s|||From Bill himself:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mdacsdk/htm/mdac_deprecated_components.asp

Also - you would be strongly advised not to use the SA account for connecting to your server. Use either windows authentification (MS recommeded) or create a new SQL Server Login with only the permissions required of the user.

HTH|||Thanks alot for the help. Sad thing was, I had visited connectionstrings.com and even saved it to my favorites last night but failed to even give it a shot. It got me one stone closer to where I need to go. Now it's off to some VB forums to solve other issues. I am sure I will return for more simple stuff in the near future. Again, thanks.

TIbor

connection failed

Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and after
entering it - it works. But only for the current transaction. Next time it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC drivers, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.
It depends on the said program. How the program is configured or coded to
connect to the SQL Server database? It sounds the program is configured or
hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of error
is bacause "sa" account's password has been changed, which is good (maybe
the DB admin knew some apps use "sa" to access the SQL Server, which is bad
practice, and he changed it?).
You must find a way to reconfigure it to use new password. If the password
is hard coded, then you may out luck to change it easily.
"Marius Kaizerman" <marius@.kaizerman.org> wrote in message
news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and
after
entering it - it works. But only for the current transaction. Next time
it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC
drivers, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.
|||Norman,
You were absolutely right.
Thanks alot!
"Norman Yuan" <NoAddress@.NoEmail.fake> wrote in message
news:OonyLvDMIHA.1164@.TK2MSFTNGP02.phx.gbl...
> It depends on the said program. How the program is configured or coded to
> connect to the SQL Server database? It sounds the program is configured or
> hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of
> error is bacause "sa" account's password has been changed, which is good
> (maybe the DB admin knew some apps use "sa" to access the SQL Server,
> which is bad practice, and he changed it?).
> You must find a way to reconfigure it to use new password. If the password
> is hard coded, then you may out luck to change it easily.
>
> "Marius Kaizerman" <marius@.kaizerman.org> wrote in message
> news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I have a program using ms sql. It worked fine for some time, but
> now each time the program access the databases it outputs "Connection
> Failed
> SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
> After pressing OK it gives an option to input a new password manually, and
> after
> entering it - it works. But only for the current transaction. Next time
> it'll prompt again.
> I've tried to change the password, I've chaned it in the system ODBC
> drivers, tried
> different usernames, but the same error returns.
> What could be the problem ?
> Thanks.

connection failed

Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and after
entering it - it works. But only for the current transaction. Next time it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC drivers, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.
It depends on the said program. How the program is configured or coded to
connect to the SQL Server database? It sounds the program is configured or
hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of error
is bacause "sa" account's password has been changed, which is good (maybe
the DB admin knew some apps use "sa" to access the SQL Server, which is bad
practice, and he changed it?).
You must find a way to reconfigure it to use new password. If the password
is hard coded, then you may out luck to change it easily.
"Marius Kaizerman" <marius@.kaizerman.org> wrote in message
news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and
after
entering it - it works. But only for the current transaction. Next time
it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC
drivers, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.
|||Norman,
You were absolutely right.
Thanks alot!
"Norman Yuan" <NoAddress@.NoEmail.fake> wrote in message
news:OonyLvDMIHA.1164@.TK2MSFTNGP02.phx.gbl...
> It depends on the said program. How the program is configured or coded to
> connect to the SQL Server database? It sounds the program is configured or
> hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of
> error is bacause "sa" account's password has been changed, which is good
> (maybe the DB admin knew some apps use "sa" to access the SQL Server,
> which is bad practice, and he changed it?).
> You must find a way to reconfigure it to use new password. If the password
> is hard coded, then you may out luck to change it easily.
>
> "Marius Kaizerman" <marius@.kaizerman.org> wrote in message
> news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I have a program using ms sql. It worked fine for some time, but
> now each time the program access the databases it outputs "Connection
> Failed
> SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
> After pressing OK it gives an option to input a new password manually, and
> after
> entering it - it works. But only for the current transaction. Next time
> it'll prompt again.
> I've tried to change the password, I've chaned it in the system ODBC
> drivers, tried
> different usernames, but the same error returns.
> What could be the problem ?
> Thanks.

connection failed

Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and a
fter
entering it - it works. But only for the current transaction. Next time it'l
l prompt again.
I've tried to change the password, I've chaned it in the system ODBC drivers
, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.It depends on the said program. How the program is configured or coded to
connect to the SQL Server database? It sounds the program is configured or
hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of error
is bacause "sa" account's password has been changed, which is good (maybe
the DB admin knew some apps use "sa" to access the SQL Server, which is bad
practice, and he changed it?).
You must find a way to reconfigure it to use new password. If the password
is hard coded, then you may out luck to change it easily.
"Marius Kaizerman" <marius@.kaizerman.org> wrote in message
news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
Hi,
I have a program using ms sql. It worked fine for some time, but
now each time the program access the databases it outputs "Connection Failed
SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
After pressing OK it gives an option to input a new password manually, and
after
entering it - it works. But only for the current transaction. Next time
it'll prompt again.
I've tried to change the password, I've chaned it in the system ODBC
drivers, tried
different usernames, but the same error returns.
What could be the problem ?
Thanks.|||Norman,
You were absolutely right.
Thanks alot!
"Norman Yuan" <NoAddress@.NoEmail.fake> wrote in message
news:OonyLvDMIHA.1164@.TK2MSFTNGP02.phx.gbl...
> It depends on the said program. How the program is configured or coded to
> connect to the SQL Server database? It sounds the program is configured or
> hard-coded (too bad!!!) with "sa/sapassword" to connect. The reason of
> error is bacause "sa" account's password has been changed, which is good
> (maybe the DB admin knew some apps use "sa" to access the SQL Server,
> which is bad practice, and he changed it?).
> You must find a way to reconfigure it to use new password. If the password
> is hard coded, then you may out luck to change it easily.
>
> "Marius Kaizerman" <marius@.kaizerman.org> wrote in message
> news:e9e%23NcDMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I have a program using ms sql. It worked fine for some time, but
> now each time the program access the databases it outputs "Connection
> Failed
> SQLState 28000, SQL Server Error 18456, Login failed for user 'sa'".
> After pressing OK it gives an option to input a new password manually, and
> after
> entering it - it works. But only for the current transaction. Next time
> it'll prompt again.
> I've tried to change the password, I've chaned it in the system ODBC
> drivers, tried
> different usernames, but the same error returns.
> What could be the problem ?
> Thanks.

Connection error

Hi there,

I installed Visual Web Developer Express and SQL Server Express. I then installed the Time Tracker Starter Kit on my localhost. My instance of SQL Server Express is 'Express'. So I updated the root web.config file. I try out the app. by creating a new user and then get this error:

Exception Details:System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

I'm using a HTTP connection port 7080 (ie,http://localhost:7080/TimeTracker/), does that mean I have to update anything in the app?

I was told to update SQL Server 2005 Surface Area Configuration - Remote Connections to Using both TCP/IP and named pipes. So I already did that and rebooted.

Any suggestions?

Post your connection string, it may help|||

Hey it works.

I noticed that I had to modify the database connnection under the database explorer, even though I had updated the web.config

Take care

Connection

iam using an execute sql task

ineed the connection to be daynamic ,changed at run time ..

how can i do that

Depending on your scenario you may have more than one option. Serach in package configurations or "http://msdn2.microsoft.com/en-us/library/ms141682.aspx">http://msdn2.microsoft.com/en-us/library/ms141682.aspx

"http://msdn2.microsoft.com/en-us/library/ms141232.aspx">http://msdn2.microsoft.com/en-us/library/ms141232.aspx

|||

Batool wrote:

iam using an execute sql task

ineed the connection to be daynamic ,changed at run time ..

how can i do that

Use an "http://blogs.conchango.com/jamiethomson/archive/2006/10/05/SSIS-Nugget_3A00_-Dynamically-set-a-logfile-name.aspx">http://blogs.conchango.com/jamiethomson/archive/2006/10/05/SSIS-Nugget_3A00_-Dynamically-set-a-logfile-name.aspx

talks about setting an expressoin on the ConnectionString property of a file conenction manager rather than an OLE DB Conenction Manager, but the concept is the same.

-Jamie

|||

Hi,

The easiest way to set dynamic connection at run time is by declaring two SSIS variables

1. DBName
2. DBServer

In connection properties open the "InitialCatalog" = "@.[User::DBName]" and "ServerName" = "@.[User::DBServer]".While running the package if you just set the value of variables dynamically the connection to the DB will be created accordingly. Using this connection in SQL task will server your purpose. This works with both OLEDB and ADO.NET connections.

Thanks

Mohit

|||thx for ur replay and i think its my solution but,can we read theses variable from the registry|||

Hi,

Using follwoing in Script tasks will retrieve value from registry

Imports Microsoft.Win32

VarValue = Registry.LocalMachine.GetValue(<Registry Key>)

After getting the value you can set this in SSIS variables using Dts.Variables("DBServer").Value = VarValue will set the value from registry

Thanks

Mohit

|||Sorry that seems a bit mad. Why write code when there is a built in mechanism, see Configurations. You can use the registry as a source for a configuration. It also happens before the package starts executing, so things start working from the very begining. Often changing a connection part way can be an issue, as tasks have started to validate or do other preparation.|||

I PUT THE NEEDED VALUES IN THE REGISTRY

(DB NAME AND SERVER NAME )

BUT I DID NOT KNOW HOW TO RETRIVE THESE VALUES AND MADE THE CONNECTION STRING

|||

Independently where you want to store your configuration values; in the case of connection managers you can better store the whole connection string, instead of Server name and DB name; and then use that value against the connection string property.

|||

There is a section in Books Online that describes the registry format. Seems that you must use one value per key, and that value must be called Value. It also seems to be limited to values within HKEY_CURRENT_USER. In retrospect the Script task method may be better after all with these rather restrictive limitations.

Package Configurations
(http://msdn2.microsoft.com/en-us/library/d20e0311-1fc9-4ddc-a381-6d127cf11b69.aspx)

Added Connect Feedback on these restrictions - https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=250871

connection

Please help me resolve I'm stuck and a novice
I have a connection string in a VB app that I am working
on but when i execute app I get
Run time Error -2147467259 (80004005) Login failed for
user *** reseaon not a trusted SQL Server connection.
I am set up on SQL server I can run enterprise manage from
my PC and run queries against server but I can not through
my application, I am set up using my windows user info..Hi, Chuck.
Refer to the following site:
http://www.able-consulting.com/ado_conn.htm
You can see many connection examples. This may help you.
"Chuck" <anonymous@.discussions.microsoft.com> wrote in message
news:051d01c3bbd7$20610da0$a501280a@.phx.gbl...
> Please help me resolve I'm stuck and a novice
> I have a connection string in a VB app that I am working
> on but when i execute app I get
> Run time Error -2147467259 (80004005) Login failed for
> user *** reseaon not a trusted SQL Server connection.
> I am set up on SQL server I can run enterprise manage from
> my PC and run queries against server but I can not through
> my application, I am set up using my windows user info..

connecting two different databases

Hi,

Is there a way to connect to two separate databases at the same time through my web application?

In my web.config under the configuration/appSetting I have created two keys for database connection:
<add key="MyConn" value="server=PLMNBK\PLMNBKSQLSERVER;uid=sa;pwd=xxxx;database=SourcingDB" />
<add key="MyConn2" value="server=PLMNBK\PLMNBKSQLSERVER;uid=sa;pwd=xxxx;database=SeaTender" /
This enable me to pass the connection string to a session variable through a dropdownlist box and connect to the desired database.

However, I would like to create a dataset from two tables which are not in the same database, one in the "SourcingDB" and the other one in the "SeaTender".

Thanks for some guidance.

PLMOne option might be to use the 3-part naming convention in you query(s) - ( assuming you have cross db permissions and both catalogs are located on the same server).

Something like:

FROM <DatabaseName>.<OwnerName>.<ObjectName>

|||Thanks,

Actually both databases are on the same server, if I understand well the "From<Databasename>.<OwnerName>.<ObjectName>" syntax should be in my SQL Select clause? Am I right?

Slts.

PLM|||checkout books on line about OPENDATASOURCE.

hth|||>>if I understand well

You are right.

Connecting to sql server from local computer using client tools

Hi,

I just installed SQL Server for the first time on a windows 2003 OS which is on its on server. Then, I installed the client tools on my local computer. Now how do I connect to the sql server with my client tools? What I wanted to do is from my local computer use the enterprise manager and pull up the databases that are located on the server that contains the sql server.

Thanks a bunch,
Laura ;)Right click on SQL Server Group in Enterprise Manager and select New Server Registration. If it doesn't automatically list your server you will have to type its name in.|||Oh Perfect.

Thank You So Much,
Laura

Connecting to SQL Server from diffrent platform, Please HELP!

Hi,

This is second time that I ask this question in this forum but there was no answer last time I did this :(

What I have to do if I want to connect to MS SQL Server 2000 installed on Windows 2000 when I write a Visual Basic program on a Windows 98?
I mean, If I install a MS SQL Server 2000 on Windows 2000, and I want to connect to server with a Visual Basic programm that I write on a computer with Windows 98 operating system, I got "ACCESS DENIED" error :(
What I have to do to make it works?

Please help me about this problem, any Idea or article, web site and etc. you think it can help me!

Thanks again for you attention ;)Can you give some more details. How do you connect, are your logins correct etc. From your post it's impossible to know what the exact problem is.|||if you have access to where the db's are located the easiest way is to just create a .udl file in it and then you can gui wise select your driver and all that, it then creates the connection string for you when you open it in wordpad

you can see this everywhere, msdn,wrox books, teacher pass it off as their own too, this method has no origin because people always rip it off VERBATIM and never say where they got it from, *shrug*|||You've got response to your first question.

The "Access denied" error may be caused by the missing DCOM functionality (ADO works with ActiveX objects, which are communicating with (D)COM.

Connecting to Sql Server 2005 on Win2K3 Server

Hello,
I have a Win2K3 Server running .Net Framework 2.0 applications. When I
run an application for the first time on a particular day, the first
connection takes an extremely long time to connect (60 seconds or
more). Other connections afterwards are fine.
I am running the application on the same machine as the db server. So
network issues should not be a factor.
I can connect with Sql Server Management Studio fine. As a matter of
fact, I can connect with Sql Server Management Studio first. But the
first time I run an application on any day, it takes an extremely long
time to connect. I am using the Enterprise Library Data Application
Block for data access in my applications. It's the January 2006 version
of the data application block.
Anyone know why this happens?
Thanks.
IT takes a while for the DAAB to obtain all of the metadata that it requires
to continue to function properly.
I suggest that if you can't live with the 'setup' time issue, that perhaps
you should investigate direct connections using stored procedures instead of
the DAAB.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
<rmgalante@.yahoo.com> wrote in message
news:1166105657.334884.75560@.73g2000cwn.googlegrou ps.com...
> Hello,
> I have a Win2K3 Server running .Net Framework 2.0 applications. When I
> run an application for the first time on a particular day, the first
> connection takes an extremely long time to connect (60 seconds or
> more). Other connections afterwards are fine.
> I am running the application on the same machine as the db server. So
> network issues should not be a factor.
> I can connect with Sql Server Management Studio fine. As a matter of
> fact, I can connect with Sql Server Management Studio first. But the
> first time I run an application on any day, it takes an extremely long
> time to connect. I am using the Enterprise Library Data Application
> Block for data access in my applications. It's the January 2006 version
> of the data application block.
> Anyone know why this happens?
> Thanks.
>

Connecting to Sql Server 2005 on Win2K3 Server

Hello,
I have a Win2K3 Server running .Net Framework 2.0 applications. When I
run an application for the first time on a particular day, the first
connection takes an extremely long time to connect (60 seconds or
more). Other connections afterwards are fine.
I am running the application on the same machine as the db server. So
network issues should not be a factor.
I can connect with Sql Server Management Studio fine. As a matter of
fact, I can connect with Sql Server Management Studio first. But the
first time I run an application on any day, it takes an extremely long
time to connect. I am using the Enterprise Library Data Application
Block for data access in my applications. It's the January 2006 version
of the data application block.
Anyone know why this happens?
Thanks.IT takes a while for the DAAB to obtain all of the metadata that it requires
to continue to function properly.
I suggest that if you can't live with the 'setup' time issue, that perhaps
you should investigate direct connections using stored procedures instead of
the DAAB.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
<rmgalante@.yahoo.com> wrote in message
news:1166105657.334884.75560@.73g2000cwn.googlegroups.com...
> Hello,
> I have a Win2K3 Server running .Net Framework 2.0 applications. When I
> run an application for the first time on a particular day, the first
> connection takes an extremely long time to connect (60 seconds or
> more). Other connections afterwards are fine.
> I am running the application on the same machine as the db server. So
> network issues should not be a factor.
> I can connect with Sql Server Management Studio fine. As a matter of
> fact, I can connect with Sql Server Management Studio first. But the
> first time I run an application on any day, it takes an extremely long
> time to connect. I am using the Enterprise Library Data Application
> Block for data access in my applications. It's the January 2006 version
> of the data application block.
> Anyone know why this happens?
> Thanks.
>