In SQL 2000, the 'Copy SQL Server Objects' task allows 'copy indexes' under
'Advanced Copy Options' when transferring tables. But I cannot see where the
SQL 2005 Import and Export Wizard allows this option. Is there an easy way
to do this (I hope) ?
Hello Mark,
You could check "Transfer SQL server objects" task in SSIS project in
VS.net 2005. DTS is ugpraded to SSIS in SQL 2005.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Cannot copy indexes w 2005 Import/Export Wizard
>thread-index: AcYnif7U0qKGdOuRRFuiyisljvKhWg==
>X-WBNR-Posting-Host: 67.96.43.11
>From: "=?Utf-8?B?TWFya0dzY2g=?=" <markgsch@.noemail.noemail>
>Subject: Cannot copy indexes w 2005 Import/Export Wizard
>Date: Wed, 1 Feb 2006 15:48:26 -0800
>Lines: 4
>Message-ID: <D1072BA0-E4FF-4E06-8F4C-018F334730F9@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:419786
>X-Tomcat-NG: microsoft.public.sqlserver.server
>In SQL 2000, the 'Copy SQL Server Objects' task allows 'copy indexes'
under
>'Advanced Copy Options' when transferring tables. But I cannot see where
the
>SQL 2005 Import and Export Wizard allows this option. Is there an easy
way
>to do this (I hope) ?
>
Showing posts with label allows. Show all posts
Showing posts with label allows. Show all posts
Wednesday, March 7, 2012
Cannot copy indexes w 2005 Import/Export Wizard
In SQL 2000, the 'Copy SQL Server Objects' task allows 'copy indexes' under
'Advanced Copy Options' when transferring tables. But I cannot see where the
SQL 2005 Import and Export Wizard allows this option. Is there an easy way
to do this (I hope) ?Hello Mark,
You could check "Transfer SQL server objects" task in SSIS project in
VS.net 2005. DTS is ugpraded to SSIS in SQL 2005.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Cannot copy indexes w 2005 Import/Export Wizard
>thread-index: AcYnif7U0qKGdOuRRFuiyisljvKhWg==
>X-WBNR-Posting-Host: 67.96.43.11
>From: "examnotes" <markgsch@.noemail.noemail>
>Subject: Cannot copy indexes w 2005 Import/Export Wizard
>Date: Wed, 1 Feb 2006 15:48:26 -0800
>Lines: 4
>Message-ID: <D1072BA0-E4FF-4E06-8F4C-018F334730F9@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:419786
>X-Tomcat-NG: microsoft.public.sqlserver.server
>In SQL 2000, the 'Copy SQL Server Objects' task allows 'copy indexes'
under
>'Advanced Copy Options' when transferring tables. But I cannot see where
the
>SQL 2005 Import and Export Wizard allows this option. Is there an easy
way
>to do this (I hope) ?
>
'Advanced Copy Options' when transferring tables. But I cannot see where the
SQL 2005 Import and Export Wizard allows this option. Is there an easy way
to do this (I hope) ?Hello Mark,
You could check "Transfer SQL server objects" task in SSIS project in
VS.net 2005. DTS is ugpraded to SSIS in SQL 2005.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Cannot copy indexes w 2005 Import/Export Wizard
>thread-index: AcYnif7U0qKGdOuRRFuiyisljvKhWg==
>X-WBNR-Posting-Host: 67.96.43.11
>From: "examnotes" <markgsch@.noemail.noemail>
>Subject: Cannot copy indexes w 2005 Import/Export Wizard
>Date: Wed, 1 Feb 2006 15:48:26 -0800
>Lines: 4
>Message-ID: <D1072BA0-E4FF-4E06-8F4C-018F334730F9@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:419786
>X-Tomcat-NG: microsoft.public.sqlserver.server
>In SQL 2000, the 'Copy SQL Server Objects' task allows 'copy indexes'
under
>'Advanced Copy Options' when transferring tables. But I cannot see where
the
>SQL 2005 Import and Export Wizard allows this option. Is there an easy
way
>to do this (I hope) ?
>
Cannot copy indexes w 2005 Import/Export Wizard
In SQL 2000, the 'Copy SQL Server Objects' task allows 'copy indexes' under
'Advanced Copy Options' when transferring tables. But I cannot see where the
SQL 2005 Import and Export Wizard allows this option. Is there an easy way
to do this (I hope) ?Hello Mark,
You could check "Transfer SQL server objects" task in SSIS project in
VS.net 2005. DTS is ugpraded to SSIS in SQL 2005.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Cannot copy indexes w 2005 Import/Export Wizard
>thread-index: AcYnif7U0qKGdOuRRFuiyisljvKhWg==>X-WBNR-Posting-Host: 67.96.43.11
>From: "=?Utf-8?B?TWFya0dzY2g=?=" <markgsch@.noemail.noemail>
>Subject: Cannot copy indexes w 2005 Import/Export Wizard
>Date: Wed, 1 Feb 2006 15:48:26 -0800
>Lines: 4
>Message-ID: <D1072BA0-E4FF-4E06-8F4C-018F334730F9@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:419786
>X-Tomcat-NG: microsoft.public.sqlserver.server
>In SQL 2000, the 'Copy SQL Server Objects' task allows 'copy indexes'
under
>'Advanced Copy Options' when transferring tables. But I cannot see where
the
>SQL 2005 Import and Export Wizard allows this option. Is there an easy
way
>to do this (I hope) ?
>
'Advanced Copy Options' when transferring tables. But I cannot see where the
SQL 2005 Import and Export Wizard allows this option. Is there an easy way
to do this (I hope) ?Hello Mark,
You could check "Transfer SQL server objects" task in SSIS project in
VS.net 2005. DTS is ugpraded to SSIS in SQL 2005.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Cannot copy indexes w 2005 Import/Export Wizard
>thread-index: AcYnif7U0qKGdOuRRFuiyisljvKhWg==>X-WBNR-Posting-Host: 67.96.43.11
>From: "=?Utf-8?B?TWFya0dzY2g=?=" <markgsch@.noemail.noemail>
>Subject: Cannot copy indexes w 2005 Import/Export Wizard
>Date: Wed, 1 Feb 2006 15:48:26 -0800
>Lines: 4
>Message-ID: <D1072BA0-E4FF-4E06-8F4C-018F334730F9@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:419786
>X-Tomcat-NG: microsoft.public.sqlserver.server
>In SQL 2000, the 'Copy SQL Server Objects' task allows 'copy indexes'
under
>'Advanced Copy Options' when transferring tables. But I cannot see where
the
>SQL 2005 Import and Export Wizard allows this option. Is there an easy
way
>to do this (I hope) ?
>
Tuesday, February 14, 2012
Cannot connect to remote Sql Server 2005
Hi;
I installed the dev version of SqlServer 2005 and can access it fine on the
server it is on. And the properties say it allows remote connections.
But SqlServer Management Studio cannot connect from my workstation to the
server. And I cannot connect using ADO.NET or JDBC.
SSMS says "An error...Named Pipes Provider, error: 40 - Could not open a
connection to SQL Server)(Microsoft SQL Server, Error: 233)
The ADO.NET exception is:
System.Data.SqlClient.SqlException was unhandled
Message="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)"
Source=".Net SqlClient Data Provider"
ErrorCode=-2146232060
Class=20
LineNumber=0
Number=233
Server="lumiere"
State=0
StackTrace:
at
System.Data.ProviderBase.DbConnectionPool.GetConne ction(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at DBConnTest.SqlServer2005Test.TestSqlServerConnecti on(Boolean
useSSPI) in C:\src\DBConnTest\DBConnTest\SqlServer2005Test.cs: line 31
at DBConnTest.Program.Main() in
C:\src\DBConnTest\DBConnTest\Program.cs:line 29
at System.AppDomain.nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence
assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.Run UsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context( Object state)
at System.Threading.ExecutionContext.Run(ExecutionCon text
executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
Any ideas?
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htm
Hello Dave,
To resolve this issue, please do the following steps on the server:
1. Start SQL Server Configuration Manager in the Start Menu -> Microsoft
SQL Server 2005 -> Configuration Tools
2. Under SQL Server 2005 Network Configuration, Enabled TCP/IP
3. Right clicked Properties on TCP/IP, on the IP Address tab, enabled the
appropriate, active IP Address and then test to connect to the server again.
If this still could not help, please do the following on the client:
1. Start SQL Server Configuration Manager
2. Under SQL Native Client Configuration, Right click Aliases, click New
Alias.
3. Add the Server name and Port No and then test to connect to the server
again.
Hope this will be helpful.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti.../default.aspx.
==================================================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
|||The TCP/IP (and named pipes) was disabled. Turning that on fixed it.
I understand starting with everything locked down but boy is it a pain...
Any suggestions of a good Sql Server 2005 book for someone who knows Sql
Server 2000?
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htm
"Wei Lu [MSFT]" wrote:
> Hello Dave,
> To resolve this issue, please do the following steps on the server:
> 1. Start SQL Server Configuration Manager in the Start Menu -> Microsoft
> SQL Server 2005 -> Configuration Tools
> 2. Under SQL Server 2005 Network Configuration, Enabled TCP/IP
> 3. Right clicked Properties on TCP/IP, on the IP Address tab, enabled the
> appropriate, active IP Address and then test to connect to the server again.
> If this still could not help, please do the following on the client:
> 1. Start SQL Server Configuration Manager
> 2. Under SQL Native Client Configuration, Right click Aliases, click New
> Alias.
> 3. Add the Server name and Port No and then test to connect to the server
> again.
> Hope this will be helpful.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscripti...ult.aspx#notif
> ications.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscripti.../default.aspx.
> ==================================================
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
|||Here are a few books to get you started:
Microsoft SQL ServerT 2005: Database Essentials Step by Step
Solid Quality Learning
Microsoft Press
ISBN 0-7356-2207-8 (exp. 9/6/06)
Microsoft SQL ServerT 2005: Applied Techniques Step by Step
Solid Quality Learning
Microsoft Press
ISBN 0-7356-2316-3
Inside Microsoft SQL ServerT 2005: The Storage Engine
Kalen Delaney
Microsoft Press
ISBN 0-7356-2105-5 (exp. 9/27/06)
Administrator's Guide to SQL Server 2005 (Paperback)
Buck Woody
Addison-Wesley
ISBN: 0321397975
Pro SQL Server 2005
Thomas Rizzo, Julian Skinner, Adam Machanic
APress
ISBN: 1590594770
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"David Thielen" <thielen@.nospam.nospam> wrote in message
news:43747646-4865-4388-9221-0389550C410B@.microsoft.com...[vbcol=seagreen]
> The TCP/IP (and named pipes) was disabled. Turning that on fixed it.
> I understand starting with everything locked down but boy is it a pain...
> Any suggestions of a good Sql Server 2005 book for someone who knows Sql
> Server 2000?
> --
> thanks - dave
> david_at_windward_dot_net
> http://www.windwardreports.com
> Cubicle Wars - http://www.windwardreports.com/film.htm
>
>
> "Wei Lu [MSFT]" wrote:
I installed the dev version of SqlServer 2005 and can access it fine on the
server it is on. And the properties say it allows remote connections.
But SqlServer Management Studio cannot connect from my workstation to the
server. And I cannot connect using ADO.NET or JDBC.
SSMS says "An error...Named Pipes Provider, error: 40 - Could not open a
connection to SQL Server)(Microsoft SQL Server, Error: 233)
The ADO.NET exception is:
System.Data.SqlClient.SqlException was unhandled
Message="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)"
Source=".Net SqlClient Data Provider"
ErrorCode=-2146232060
Class=20
LineNumber=0
Number=233
Server="lumiere"
State=0
StackTrace:
at
System.Data.ProviderBase.DbConnectionPool.GetConne ction(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at DBConnTest.SqlServer2005Test.TestSqlServerConnecti on(Boolean
useSSPI) in C:\src\DBConnTest\DBConnTest\SqlServer2005Test.cs: line 31
at DBConnTest.Program.Main() in
C:\src\DBConnTest\DBConnTest\Program.cs:line 29
at System.AppDomain.nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence
assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.Run UsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context( Object state)
at System.Threading.ExecutionContext.Run(ExecutionCon text
executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
Any ideas?
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htm
Hello Dave,
To resolve this issue, please do the following steps on the server:
1. Start SQL Server Configuration Manager in the Start Menu -> Microsoft
SQL Server 2005 -> Configuration Tools
2. Under SQL Server 2005 Network Configuration, Enabled TCP/IP
3. Right clicked Properties on TCP/IP, on the IP Address tab, enabled the
appropriate, active IP Address and then test to connect to the server again.
If this still could not help, please do the following on the client:
1. Start SQL Server Configuration Manager
2. Under SQL Native Client Configuration, Right click Aliases, click New
Alias.
3. Add the Server name and Port No and then test to connect to the server
again.
Hope this will be helpful.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti.../default.aspx.
==================================================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
|||The TCP/IP (and named pipes) was disabled. Turning that on fixed it.
I understand starting with everything locked down but boy is it a pain...
Any suggestions of a good Sql Server 2005 book for someone who knows Sql
Server 2000?
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htm
"Wei Lu [MSFT]" wrote:
> Hello Dave,
> To resolve this issue, please do the following steps on the server:
> 1. Start SQL Server Configuration Manager in the Start Menu -> Microsoft
> SQL Server 2005 -> Configuration Tools
> 2. Under SQL Server 2005 Network Configuration, Enabled TCP/IP
> 3. Right clicked Properties on TCP/IP, on the IP Address tab, enabled the
> appropriate, active IP Address and then test to connect to the server again.
> If this still could not help, please do the following on the client:
> 1. Start SQL Server Configuration Manager
> 2. Under SQL Native Client Configuration, Right click Aliases, click New
> Alias.
> 3. Add the Server name and Port No and then test to connect to the server
> again.
> Hope this will be helpful.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscripti...ult.aspx#notif
> ications.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscripti.../default.aspx.
> ==================================================
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
|||Here are a few books to get you started:
Microsoft SQL ServerT 2005: Database Essentials Step by Step
Solid Quality Learning
Microsoft Press
ISBN 0-7356-2207-8 (exp. 9/6/06)
Microsoft SQL ServerT 2005: Applied Techniques Step by Step
Solid Quality Learning
Microsoft Press
ISBN 0-7356-2316-3
Inside Microsoft SQL ServerT 2005: The Storage Engine
Kalen Delaney
Microsoft Press
ISBN 0-7356-2105-5 (exp. 9/27/06)
Administrator's Guide to SQL Server 2005 (Paperback)
Buck Woody
Addison-Wesley
ISBN: 0321397975
Pro SQL Server 2005
Thomas Rizzo, Julian Skinner, Adam Machanic
APress
ISBN: 1590594770
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"David Thielen" <thielen@.nospam.nospam> wrote in message
news:43747646-4865-4388-9221-0389550C410B@.microsoft.com...[vbcol=seagreen]
> The TCP/IP (and named pipes) was disabled. Turning that on fixed it.
> I understand starting with everything locked down but boy is it a pain...
> Any suggestions of a good Sql Server 2005 book for someone who knows Sql
> Server 2000?
> --
> thanks - dave
> david_at_windward_dot_net
> http://www.windwardreports.com
> Cubicle Wars - http://www.windwardreports.com/film.htm
>
>
> "Wei Lu [MSFT]" wrote:
Friday, February 10, 2012
Cannot connect remotely to MSDE2000 database
Hi,
I have a win98 Pc connecting to a winxp pc - trying to connect to the
MSDE2000 database - the database is operating in mixed mode (allows SQL
logins) rather than windows integrated. The database is working ok on winxp
pc - i can use the SQL Web Data adminsitrator to verify that SQL Logins work
ok - also the ODBC Adminstrator can make connections to the database.
Now when i try using the ODBC Administrator to connect using the same
details it fails - SQL server does not exist or access denied.
Now i have disabled windows firewall to rule that out (although i had
enabled port 1433- sql server listening port).
Now how can i verify SQL server is listening on port 1433 for remote
connections?
How do i configre SQL server to listen for remote connections?
Any other ideas for resolving my connection problem?
Thanks a lot!
hi John,
John Blair wrote:
> Hi,
> I have a win98 Pc connecting to a winxp pc - trying to connect to the
> MSDE2000 database - the database is operating in mixed mode (allows
> SQL logins) rather than windows integrated. The database is working
> ok on winxp pc - i can use the SQL Web Data adminsitrator to verify
> that SQL Logins work ok - also the ODBC Adminstrator can make
> connections to the database.
> Now when i try using the ODBC Administrator to connect using the same
> details it fails - SQL server does not exist or access denied.
> Now i have disabled windows firewall to rule that out (although i had
> enabled port 1433- sql server listening port).
> Now how can i verify SQL server is listening on port 1433 for remote
> connections?
> How do i configre SQL server to listen for remote connections?
> Any other ideas for resolving my connection problem?
> Thanks a lot!
please verify, using Server Network Utility (svrnetcn.exe), that the MSDE
instance allows remote connections via the desired/required network
protocol...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks a lot - very immpressed - that did the trick - TCP/IP protocol was
disabled - i enabled it and it worked!
I've spent 2 days trying to get this working - eventually found out the
registry needed changing to allow mixed mode (SQL login)- found out my
firewall was blocking port 1433 - and finally your suggestion for enabling
the protocol - never even heard of that utility svrnetcn.exe - thanks very
much! John.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:37md0nF5eceloU1@.individual.net...
> hi John,
> John Blair wrote:
> please verify, using Server Network Utility (svrnetcn.exe), that the MSDE
> instance allows remote connections via the desired/required network
> protocol...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Exposing SQL through a firewall by opening port 1433 is generally considered
to be a bad thing.
-Andrew
"John Blair" <john_blair@.hotmail.com> wrote in message
news:H2oRd.910$gv6.611@.newsfe3-gui.ntli.net...
> Thanks a lot - very immpressed - that did the trick - TCP/IP protocol was
> disabled - i enabled it and it worked!
> I've spent 2 days trying to get this working - eventually found out the
> registry needed changing to allow mixed mode (SQL login)- found out my
> firewall was blocking port 1433 - and finally your suggestion for enabling
> the protocol - never even heard of that utility svrnetcn.exe - thanks very
> much! John.
>
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:37md0nF5eceloU1@.individual.net...
>
|||I am only exposing this port on a local intranet - so i wasn't aware that
there are any security risks. Do you have a better way of letting VB6 apps
access a remote SQL Server database? Thanks.
"Andrew" <nemoby@.nospam.nospam> wrote in message
news:uVC2%23ofFFHA.4016@.TK2MSFTNGP09.phx.gbl...
> Exposing SQL through a firewall by opening port 1433 is generally
> considered to be a bad thing.
> -Andrew
> "John Blair" <john_blair@.hotmail.com> wrote in message
> news:H2oRd.910$gv6.611@.newsfe3-gui.ntli.net...
>
I have a win98 Pc connecting to a winxp pc - trying to connect to the
MSDE2000 database - the database is operating in mixed mode (allows SQL
logins) rather than windows integrated. The database is working ok on winxp
pc - i can use the SQL Web Data adminsitrator to verify that SQL Logins work
ok - also the ODBC Adminstrator can make connections to the database.
Now when i try using the ODBC Administrator to connect using the same
details it fails - SQL server does not exist or access denied.
Now i have disabled windows firewall to rule that out (although i had
enabled port 1433- sql server listening port).
Now how can i verify SQL server is listening on port 1433 for remote
connections?
How do i configre SQL server to listen for remote connections?
Any other ideas for resolving my connection problem?
Thanks a lot!
hi John,
John Blair wrote:
> Hi,
> I have a win98 Pc connecting to a winxp pc - trying to connect to the
> MSDE2000 database - the database is operating in mixed mode (allows
> SQL logins) rather than windows integrated. The database is working
> ok on winxp pc - i can use the SQL Web Data adminsitrator to verify
> that SQL Logins work ok - also the ODBC Adminstrator can make
> connections to the database.
> Now when i try using the ODBC Administrator to connect using the same
> details it fails - SQL server does not exist or access denied.
> Now i have disabled windows firewall to rule that out (although i had
> enabled port 1433- sql server listening port).
> Now how can i verify SQL server is listening on port 1433 for remote
> connections?
> How do i configre SQL server to listen for remote connections?
> Any other ideas for resolving my connection problem?
> Thanks a lot!
please verify, using Server Network Utility (svrnetcn.exe), that the MSDE
instance allows remote connections via the desired/required network
protocol...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks a lot - very immpressed - that did the trick - TCP/IP protocol was
disabled - i enabled it and it worked!
I've spent 2 days trying to get this working - eventually found out the
registry needed changing to allow mixed mode (SQL login)- found out my
firewall was blocking port 1433 - and finally your suggestion for enabling
the protocol - never even heard of that utility svrnetcn.exe - thanks very
much! John.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:37md0nF5eceloU1@.individual.net...
> hi John,
> John Blair wrote:
> please verify, using Server Network Utility (svrnetcn.exe), that the MSDE
> instance allows remote connections via the desired/required network
> protocol...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Exposing SQL through a firewall by opening port 1433 is generally considered
to be a bad thing.
-Andrew
"John Blair" <john_blair@.hotmail.com> wrote in message
news:H2oRd.910$gv6.611@.newsfe3-gui.ntli.net...
> Thanks a lot - very immpressed - that did the trick - TCP/IP protocol was
> disabled - i enabled it and it worked!
> I've spent 2 days trying to get this working - eventually found out the
> registry needed changing to allow mixed mode (SQL login)- found out my
> firewall was blocking port 1433 - and finally your suggestion for enabling
> the protocol - never even heard of that utility svrnetcn.exe - thanks very
> much! John.
>
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:37md0nF5eceloU1@.individual.net...
>
|||I am only exposing this port on a local intranet - so i wasn't aware that
there are any security risks. Do you have a better way of letting VB6 apps
access a remote SQL Server database? Thanks.
"Andrew" <nemoby@.nospam.nospam> wrote in message
news:uVC2%23ofFFHA.4016@.TK2MSFTNGP09.phx.gbl...
> Exposing SQL through a firewall by opening port 1433 is generally
> considered to be a bad thing.
> -Andrew
> "John Blair" <john_blair@.hotmail.com> wrote in message
> news:H2oRd.910$gv6.611@.newsfe3-gui.ntli.net...
>
Subscribe to:
Posts (Atom)