Using: Windows 2003 server, SQL Server 2005 Express, SQl server management
studio.
I have an SQL server 2005 express database installed in the server but I
can't acces it with management studio. The error is:
"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-- errror locating Server\Instance"
note that:
- database is installed in the local machine.
- remote connections are enabled
-I CAN access database from my asp.net application and using ODBC attaching
tables in an Access DB
-The instance is: ServerName\SQLEXPRESS
- Shared memory, TCP/IP ad named pipes are enabled. For TCP/IP all adapters
are enabled.
- Windows firewall is disabled
Thanks for suggestionsFrank wrote:
> Using: Windows 2003 server, SQL Server 2005 Express, SQl server management
> studio.
> I have an SQL server 2005 express database installed in the server but I
> can't acces it with management studio. The error is:
> "when connecting to sql server 2005, this failure may be caused by the fac
t
> that under the default settings SQL server does not allow remote
> connections-- errror locating Server\Instance"
> note that:
> - database is installed in the local machine.
> - remote connections are enabled
> -I CAN access database from my asp.net application and using ODBC attachin
g
> tables in an Access DB
> -The instance is: ServerName\SQLEXPRESS
> - Shared memory, TCP/IP ad named pipes are enabled. For TCP/IP all adapter
s
> are enabled.
> - Windows firewall is disabled
> Thanks for suggestions
Are you running studio manager locally on the same server?|||Yes, I'm running studio manager locally on the same server
"Ken" <kshapley@.sbcglobal.net> ha scritto nel messaggio
news:1158625215.196916.240230@.m73g2000cwd.googlegroups.com...
> Frank wrote:
> Are you running studio manager locally on the same server?
>
Showing posts with label managementstudio. Show all posts
Showing posts with label managementstudio. Show all posts
Saturday, February 25, 2012
can't open SQLserver 2005 express with management studio
Using: Windows 2003 server, SQL Server 2005 Express, SQl server management
studio.
I have an SQL server 2005 express database installed in the server but I
can't acces it with management studio. The error is:
"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-- errror locating Server\Instance"
note that:
- database is installed in the local machine.
- remote connections are enabled
-I CAN access database from my asp.net application and using ODBC attaching
tables in an Access DB
-The instance is: ServerName\SQLEXPRESS
- Shared memory, TCP/IP ad named pipes are enabled. For TCP/IP all adapters
are enabled.
- Windows firewall is disabled
Thanks for suggestions
Frank wrote:
> Using: Windows 2003 server, SQL Server 2005 Express, SQl server management
> studio.
> I have an SQL server 2005 express database installed in the server but I
> can't acces it with management studio. The error is:
> "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-- errror locating Server\Instance"
> note that:
> - database is installed in the local machine.
> - remote connections are enabled
> -I CAN access database from my asp.net application and using ODBC attaching
> tables in an Access DB
> -The instance is: ServerName\SQLEXPRESS
> - Shared memory, TCP/IP ad named pipes are enabled. For TCP/IP all adapters
> are enabled.
> - Windows firewall is disabled
> Thanks for suggestions
Are you running studio manager locally on the same server?
|||Yes, I'm running studio manager locally on the same server
"Ken" <kshapley@.sbcglobal.net> ha scritto nel messaggio
news:1158625215.196916.240230@.m73g2000cwd.googlegr oups.com...
> Frank wrote:
> Are you running studio manager locally on the same server?
>
studio.
I have an SQL server 2005 express database installed in the server but I
can't acces it with management studio. The error is:
"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-- errror locating Server\Instance"
note that:
- database is installed in the local machine.
- remote connections are enabled
-I CAN access database from my asp.net application and using ODBC attaching
tables in an Access DB
-The instance is: ServerName\SQLEXPRESS
- Shared memory, TCP/IP ad named pipes are enabled. For TCP/IP all adapters
are enabled.
- Windows firewall is disabled
Thanks for suggestions
Frank wrote:
> Using: Windows 2003 server, SQL Server 2005 Express, SQl server management
> studio.
> I have an SQL server 2005 express database installed in the server but I
> can't acces it with management studio. The error is:
> "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-- errror locating Server\Instance"
> note that:
> - database is installed in the local machine.
> - remote connections are enabled
> -I CAN access database from my asp.net application and using ODBC attaching
> tables in an Access DB
> -The instance is: ServerName\SQLEXPRESS
> - Shared memory, TCP/IP ad named pipes are enabled. For TCP/IP all adapters
> are enabled.
> - Windows firewall is disabled
> Thanks for suggestions
Are you running studio manager locally on the same server?
|||Yes, I'm running studio manager locally on the same server
"Ken" <kshapley@.sbcglobal.net> ha scritto nel messaggio
news:1158625215.196916.240230@.m73g2000cwd.googlegr oups.com...
> Frank wrote:
> Are you running studio manager locally on the same server?
>
Friday, February 24, 2012
can't modify table in SMS...timeout expired?
Hi: I'm trying to add a field to a table by modifying it in Management
Studio. I'm running SQLSMS locally on the server.
When I try to save the table I get an error
"Post-Save Notifications...
[table name]
- Unable to modify table.
Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding."
The table currently has 5454 rows in it.
geek-y-guy (noone@.nowhere.org) writes:
> Hi: I'm trying to add a field to a table by modifying it in Management
> Studio. I'm running SQLSMS locally on the server.
That is a very dangerous function, which has serious bugs and shortcomings.
I strongly recommend to use ALTER TABLE statements to change your tables.
Or, at the very least, never, I say NEVER, save directly to implement
a change, but always generate a script and perform these modifications:
o Remove all BEGIN and COMMIT TRANSACTION except for the first and last.
o Wrap all batches in IF @.@.trancount > 0 BEGIN ... END
o Change all WITH NOCHECK to WITH CHECK.
And be very careful to check that the script only include the
changes you want to make. There are bugs that can cause discarded
changes to be includd.
> When I try to save the table I get an error
> "Post-Save Notifications...
> [table name]
> - Unable to modify table.
> Timeout expired. The timeout period elapsed prior to completion of the
> operation or the server is not responding."
> The table currently has 5454 rows in it.
Under Tools->Options there is a timeout for the Designers you can
change, if you insist on using that function. But if you run the script
from a query window,the timeout is not an issue.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Studio. I'm running SQLSMS locally on the server.
When I try to save the table I get an error
"Post-Save Notifications...
[table name]
- Unable to modify table.
Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding."
The table currently has 5454 rows in it.
geek-y-guy (noone@.nowhere.org) writes:
> Hi: I'm trying to add a field to a table by modifying it in Management
> Studio. I'm running SQLSMS locally on the server.
That is a very dangerous function, which has serious bugs and shortcomings.
I strongly recommend to use ALTER TABLE statements to change your tables.
Or, at the very least, never, I say NEVER, save directly to implement
a change, but always generate a script and perform these modifications:
o Remove all BEGIN and COMMIT TRANSACTION except for the first and last.
o Wrap all batches in IF @.@.trancount > 0 BEGIN ... END
o Change all WITH NOCHECK to WITH CHECK.
And be very careful to check that the script only include the
changes you want to make. There are bugs that can cause discarded
changes to be includd.
> When I try to save the table I get an error
> "Post-Save Notifications...
> [table name]
> - Unable to modify table.
> Timeout expired. The timeout period elapsed prior to completion of the
> operation or the server is not responding."
> The table currently has 5454 rows in it.
Under Tools->Options there is a timeout for the Designers you can
change, if you insist on using that function. But if you run the script
from a query window,the timeout is not an issue.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Subscribe to:
Posts (Atom)