Showing posts with label advanced. Show all posts
Showing posts with label advanced. Show all posts

Sunday, March 25, 2012

conntectionString Question Please

I'm having problems connecting Efficon's Advanced DataGrid to the database in DNN3.
Can someone help me with the syntax for the connection string?
Thanks in advance,
ScottTry http://www.connectionstrings.com for help on connection strings.
|||Resolution:
Connection Sting
Provder=SQLOLEDB
Trusted_Connection= yes (trusted_connection=true did not work)
sqlsql

Tuesday, March 20, 2012

Connectionstring

Im using sql server express advanced edition and Windows Vista. My Windows
account doesnt have any permissions to the sql server at all, so I need to
use sql server logins in my connectionstring. How can I provide that when
using attachdb?
This is my connectionstring today:
Data Source=. \SQLEXPRESS;AttachDbFilename=|DataDirect
ory|\site_db.mdf;User
Instance=False;Initial Catalog=site_db;
StigSee http://www.microsoft.com/sql/howtob...stasupport.mspx for
considerations on using SQL 2005 under Vista. Note that SP2 is still in CTP
(beta).
I haven't played around with SQL Express but you ought to be able to add the
desired SQL login credentials in the connection string:
Data Source=. \SQLEXPRESS;AttachDbFilename=|DataDirect
ory|\site_db.mdf;User
Instance=False;Initial Catalog=site_db;User Id=MyLogin;Password=MyPassword
Hope this helps.
Dan Guzman
SQL Server MVP
"Stig Kulvedrsten" <stig@.spire.as> wrote in message
news:0ABA74C2-E6C4-4E84-B331-3633D0BEC597@.microsoft.com...
> Im using sql server express advanced edition and Windows Vista. My Windows
> account doesnt have any permissions to the sql server at all, so I need to
> use sql server logins in my connectionstring. How can I provide that when
> using attachdb?
> This is my connectionstring today:
> Stig|||I reinstalled and got my sql server express up and running. I then loaded up
VS.NET and tried to run my website.
Right away I got this error:
Timeout expired. The timeout period elapsed prior to obtaining a connection
from the pool. This may have occurred because all pooled connections were
in use and max pool size was reached.
What causes this error at first runtime?
Stig
"Stig Kulvedrsten" <stig@.spire.as> wrote in message
news:0ABA74C2-E6C4-4E84-B331-3633D0BEC597@.microsoft.com...
> Im using sql server express advanced edition and Windows Vista. My Windows
> account doesnt have any permissions to the sql server at all, so I need to
> use sql server logins in my connectionstring. How can I provide that when
> using attachdb?
> This is my connectionstring today:
> Data Source=. \SQLEXPRESS;AttachDbFilename=|DataDirect
ory|\site_db.mdf;User
> Instance=False;Initial Catalog=site_db;
> Stig

Thursday, March 8, 2012

Connection to SQL Server

I have installed MS SQL Server 2005 Express Edition with Advanced Services and MS SQL Server 2005 Express Edition Toolkit SP1. Everything istalled without any errors noted. When starting SQL Server Management Studio Express, accepting the server name MAYNARD-MAIN with authentication as windows authentication. I get the following message:

Cannot connect to MAYNARD-MAIN

Additional information:

An error has occurred while establishing a connection to the server. Wehn connecting to SQL Server 2005, this failure may be caused by the fact that under the default setting SQL Server does not allow remote connections.(provider:Shared Memory Provider, error:36 - The Shared Memory dll used to connect to SQL Server was not found)(Microsoft SQL Server, Error: 126)

I haven found any info on either of these error in the forum.

The Configuration Manager shows the following:

SQL Server FullTextSearch(SQLEXPRESS) - Running

SQL Server(SQLEXPRESS) - Running

SQL Server Reporting Services(SQLEXPRESS) - Running

SQL Server Browser - Running

Protocols for SQLEXPRESS

Shared Memory - Enabled

All others disabled

Client Protocols

Shared Memory - Order 1 - Enabled

TCP/IP - Order 2 - Enabled

Named Pipes - Order 3 - Enabled

VIA - Disabled.

What do I need to be trying to find to corect this.

Either connect to the default server instance..."SQLEXPRESS" or Make sure that the "MAYNARD_MAN" instance is running before trying to connect to it|||Well that was easy enough - I really feel dumb now. Add instance to machine name and it works a lot better. Sorry I took up your time being not to bright.