Connect to remote server

From Enterprise Manager on my PC, how do I connect to a remote server over
the internet - I have the IP address, User Name and Password.

ThanksWhen creating an SQL connection using SQL Server EM you will need to:

Configure the server alias
Create the SQL connection.

Configure the Server alias

Open SQL Server Client Network Utility.
When Client Network Utility opens, click on the Alias tab.
Click on the Add button.
In the Server Alias text box enter a name for your SQL connection.
Select TCP/IP under Network libraries
Enter the IP address of the Server your SQL database is located on, in
the Server name text box.
Click on the OK button.
Your Server alias will now be configured, click on the Apply button.
Click on the OK button.

Create Connection

Open SQL Server Enterprise Manager
When Enterprise Manager opens, right click SQL Server Group and select
New SQL Server Registration.
The Register SQL Server wizard will now open.
Click on the Next button.
>From the Available Servers drop down menu, select the server alias you
created earlier.
Click on the Add button.
The server should now be listed under Added servers, click on the Next
button.
When the next dialog box appears select 'The SQL Server login
information that was assigned to me by the system administrator' (see
above).
Click on the Next button.
Enter your Login name and Password - this will be used every time you
connect to your SQL server. Click on the Next button.
Ensure that 'Add the SQL Server(s) to an existing SQL Server group' is
selected and 'SQL Server Group' is selected for Group name.

Click on the Next button.
When the next dialog box opens you can click on the Finish button.
Your SQL Connection will now be created.

HTH
Paul|||Paul

That works fine, thanks.

<stpaul_71@.yahoo.com> wrote in message
news:1102537081.548714.60980@.z14g2000cwz.googlegro ups.com...
> When creating an SQL connection using SQL Server EM you will need to:
> Configure the server alias
> Create the SQL connection.
> Configure the Server alias
> Open SQL Server Client Network Utility.
> When Client Network Utility opens, click on the Alias tab.
> Click on the Add button.
> In the Server Alias text box enter a name for your SQL connection.
> Select TCP/IP under Network libraries
> Enter the IP address of the Server your SQL database is located on, in
> the Server name text box.
> Click on the OK button.
> Your Server alias will now be configured, click on the Apply button.
> Click on the OK button.
>
> Create Connection
> Open SQL Server Enterprise Manager
> When Enterprise Manager opens, right click SQL Server Group and select
> New SQL Server Registration.
> The Register SQL Server wizard will now open.
> Click on the Next button.
>>From the Available Servers drop down menu, select the server alias you
> created earlier.
> Click on the Add button.
> The server should now be listed under Added servers, click on the Next
> button.
> When the next dialog box appears select 'The SQL Server login
> information that was assigned to me by the system administrator' (see
> above).
> Click on the Next button.
> Enter your Login name and Password - this will be used every time you
> connect to your SQL server. Click on the Next button.
> Ensure that 'Add the SQL Server(s) to an existing SQL Server group' is
> selected and 'SQL Server Group' is selected for Group name.
> Click on the Next button.
> When the next dialog box opens you can click on the Finish button.
> Your SQL Connection will now be created.
>
> HTH
> Paul

Connect to external DataBase Via SQLExpress?

Hi again... I guess this is yet another newbie question (Sorry if its been asked before!)

If I have an IP address for an external SQL DB with valid User & Pass... Can I connect to it using SQLExpress on my machine?

If so can anyone point me towards how to do it, or run through it below (In easy steps as I'm dumb )

Hi,

Yes, In the Server Name write your IP Address and Select Authenticaion Mode as SQL , supply your given credential and thats it!!! Once it let you in , right click on that IP Address in left corner and right click on it and select Register to Register the server.

Hemantgiri S. Goswami

|||

You can use Sql Server Management Studio (SSMS) to connect to other servers also. In Object Explorer window of SSMS, you have a Connect Combo in Top Left corner of Object Explorer window.

Steps are as follows

(a) Press on Connect

(b) Select Database Engine - You will get a "Connect To Server " window

(c) In this window Give IP Address in Server Name Text Box

(d) giver login name and passoward

(e) Press Connect Button

Madhu

|||Hi ... Many thanks for taking the time to reply, but I am getting this error message? Do I have to change any other settings?

TITLE: Connect to Server

Cannot connect to XX.XX.XX.XX

ADDITIONAL INFORMATION:

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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476|||

Can you get the DBA to run SQL Server Surfice Area Configuration tool to chech that Name Pipes is allowed.

Also, one thing worth check, have you confirmed the port on the IP address.
Finally please remember to check the firewall settings on the server as this could also be causing you problems.

hth

Barry Andrew

|||Thank you very much! All sorted and connected :o)... Thankssqlsql

Connect at only One port

When connecting to sql 2000 Enterprise manager opens multiple ports.
For example
Proto Local Address Foreign Address State
TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
How can I force sql to connect only at 1433 or other single port. I facts
is there such posibility?
Hi -
If you analyze the entries in the SQL Server error log file, you can verify
that the instance of SQL Server is listening on the correct IP address and on
the correct port. By default, a default instance of SQL Server listens on the
port 1433. You can also use Server Network Utility to verify the protocol
settings for SQL Server and to change the properties in SQL Server, including
the protocols that can connect to SQL Server and the ports that can be used.
For more information about using Server Network Utility, see the "SQL Server
Network Utility" topic in SQL Server Books Online.
Sometimes, SQL Server 2000 may not bind to port 1433 or any other specified
port. This problem may occur if the port is being used by another application
or if you are trying to connect by using an IP address that is not correct.
Therefore, the TCP/IP connections to SQL Server may not be successful and you
may receive the following error message in the SQL Server error log file:
2001-11-14 15:49:14.12 server SuperSocket Info: Bind failed on TCP port 1433.
Please check the below link :
http://support.microsoft.com/default.aspx?kbid=307197
Let me know if it helps you.
"Radin" wrote:

> When connecting to sql 2000 Enterprise manager opens multiple ports.
> For example
> Proto Local Address Foreign Address State
> TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
> TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
> TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
> How can I force sql to connect only at 1433 or other single port. I facts
> is there such posibility?
>

Connect at only One port

When connecting to sql 2000 Enterprise manager opens multiple ports.
For example
Proto Local Address Foreign Address State
TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
How can I force sql to connect only at 1433 or other single port. I facts
is there such posibility?Hi -
If you analyze the entries in the SQL Server error log file, you can verify
that the instance of SQL Server is listening on the correct IP address and o
n
the correct port. By default, a default instance of SQL Server listens on th
e
port 1433. You can also use Server Network Utility to verify the protocol
settings for SQL Server and to change the properties in SQL Server, includin
g
the protocols that can connect to SQL Server and the ports that can be used.
For more information about using Server Network Utility, see the "SQL Server
Network Utility" topic in SQL Server Books Online.
Sometimes, SQL Server 2000 may not bind to port 1433 or any other specified
port. This problem may occur if the port is being used by another applicatio
n
or if you are trying to connect by using an IP address that is not correct.
Therefore, the TCP/IP connections to SQL Server may not be successful and yo
u
may receive the following error message in the SQL Server error log file:
2001-11-14 15:49:14.12 server SuperSocket Info: Bind failed on TCP port 1433
.
Please check the below link :
http://support.microsoft.com/default.aspx?kbid=307197
Let me know if it helps you.
"Radin" wrote:

> When connecting to sql 2000 Enterprise manager opens multiple ports.
> For example
> Proto Local Address Foreign Address State
> TCP 192.168.7.12:1433 192.168.7.12:3275 ESTABLISHED
> TCP 192.168.7.12:1433 192.168.7.12:3634 ESTABLISHED
> TCP 192.168.7.12:3634 192.168.7.12:1433 ESTABLISHED
> How can I force sql to connect only at 1433 or other single port. I facts
> is there such posibility?
>

Confusing question or should I address it some where else?

I posted a question here on 12/6/05 about importing data from .csv file and
no one addressed it.
Here is the link
http://www.microsoft.com/technet/co...ogramming&fltr=
And the title is
Subject: import data properly from csv file.
Should I post it some where else or the question was not clear?
Please let me know if there is a better design for this.
I would really appreciate it.
ThanksActually, this is the direct link to your original quiestion:
http://msdn.microsoft.com/newsgroup...86f3&sloc=en-us
I don't really see any need for a global temporary table here. Why can't you
simply query the file directly? You're building stairs in the football field
.
If for some reason you do need a temporary table, create a local one (#name
instead of ##name). Of course local temporary tables are scope-specific, so
you'd have to create it in a top level procedure that starts the whole
process (creates the table, calls a sub procedure to import data, then does
the rest of transformations).
ML
http://milambda.blogspot.com/|||Assuming you know the structure of the resulting table, which would
be likely if you have other code to process it, how about
create table #temptbl (
thisCol thisType,
thatCol thatType
)
insert into #temptbl exec (
'SELECT * into ##temptbl FROM '+
@.linked_server + '...['+@.file + '#' +
@.extension + ']')
-- process as before
drop table #temptbl
If this is all in a procedure, you don't have to explicitly drop
#temptbl, but it's not a bad idea to do so.
Steve Kass
Drew University
sqlster wrote:

>I posted a question here on 12/6/05 about importing data from .csv file and
>no one addressed it.
>Here is the link
>http://www.microsoft.com/technet/co...ogramming&fltr=
>And the title is
>Subject: import data properly from csv file.
>Should I post it some where else or the question was not clear?
>Please let me know if there is a better design for this.
>I would really appreciate it.
>Thanks
>
>|||ML and Steve,
Thank you very much...
"Steve Kass" wrote:

> Assuming you know the structure of the resulting table, which would
> be likely if you have other code to process it, how about
> create table #temptbl (
> thisCol thisType,
> thatCol thatType
> )
> insert into #temptbl exec (
> 'SELECT * into ##temptbl FROM '+
> @.linked_server + '...['+@.file + '#' +
> @.extension + ']')
> -- process as before
> drop table #temptbl
> If this is all in a procedure, you don't have to explicitly drop
> #temptbl, but it's not a bad idea to do so.
> Steve Kass
> Drew University
> sqlster wrote:
>
>

Confusing data error

I have a gridview that is very basic and list name, address, ......, and a URL.

If I have this url in the database I have no problemhttp://www.lubbockisd.org/earlychildhood/

yet when I place this URLhttp://www.lubbockisd.org/erlychildhood/stubbs.htm

It triggers this error on my localhost server and my production server.

Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints.

Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details:System.Data.ConstraintException: Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints.

I've made changes to datatypes with no success, made sure my length of data type was set long enough with no success.

Which datatype is best for a URL in sql express?

Any ideas why this happens with such a minor change?

Thanks

Tony

Hi. Tha dataTable you are using as Datasource for the gridview has a unique constraint in the column you are changing tha data, or the column is defined as primary key... and you are attempting to insert a data that is not unique|||

You may have already done all this but I just want to make sure that that URL is not already present in the database. Other than that, what are the constraints on your fields. Does the URL field accepts only unique values.

bullpit

|||

Thanks for replying so quickly,

That is what is confusing me so much, I don't have any constraints on this field, nor is it a unique or identifier field.

Tony

|||

Hi Tony,

Is there any other table that reference this field in the DataSet?

|||

Nope, this is the only page that uses this particular table...http://www.tonyhager.com/schools/prek.aspx

TH

|||

Hi,

Please check each column that you have constraints on this table. If it has a unique constraint, make sure it is not violated with a duplicated value.

A VarChar data type will be suitable to store URLs.

HTH. If this does not answer your question, please feel free to mark the post as Not Answered and reply. Thank you!

|||

As stated previously, I have no constraints in this table. You can see that I have the URL duplicated on the page in question in the table with all three of the PreK schools listed. I have 5 pages that use this data table and none of the other pages trigger the error even when I have the URL that does trigger the error on the PreK page the other pages work fine. It only happens when I add the page name to the one URL. The default page ishttp://www.tonyhager.com/schools/

Thanks again,

TH

|||

Hi,

To troubleshoot on this issue, if you're using a DataSet to store the values, I suggest you use WriteXml("filename.xml", XmlWriteMode.WriteSchema) to write all the data and schema out to an xml file.

Analysis on this file will reveal where the constraint error is. If you're having problem, you can paste it here together with the new data you're inserting to this DataSet, and I will try to check this for you.

|||try checking your XML schema designer page and see if any of your fields have theNullValue property set to "(Throw exception)". If so, then try changing it to null.|||

Would I even have a XML schema page if I am using a sql express database? Where do I look for this page?

|||the XSD schema is generated if you "drag and drop" your tables. It creates strongly typed objects through which you can manage your scheme via the designer's interface.

if a schema has been generated it is normally generated under your "App_Code" folder and the name ends in "XSD". If you don't have a schema then you may want to consider this approach for creating strongly typed datasets in the future. It is much quicker and less error prone.|||Every field had it set to "throw exception" is that a default setting? So I should change each string field to read null?|||

only change the "offending" fields to null (unless you don't mind your other fields accepting null values as well).

the dataset schema acts as a second 'safety mechanism' to catch data-type mismatches, differences in column names, null values etc. It is a good thing but it can cause confusion sometimes because it adds an extra layer of complexity