Sql server not in VS 2005s "server explorer"

hi all.
i have SQL SERVER developer edition and VS 2005 pro edition. for some strange reason- my SQL server is not visible in VSs "server explorer". i have to "add a connection" every time i want to view or edit a DB (far from optimal...).
i know this is the SQL forum (as opposed to VS forum) but i got no answare there, so i'm trying you guys.
thanks.

Lior,
Is this still an issue?
Thank you!
Ed Price, Power BI & SQL Server Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Similar Messages

DB mail not working in sql server 2005

Hi,
from today i get following error on sql server 2005
Exception Type: Microsoft.SqlServer.Management.SqlIMail.Server.Common.BaseException
Message: There was an error on the connection. Reason: 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.
Data: System.Collections.ListDictionaryInternal
TargetSite: Void OpenConnection(Microsoft.SqlServer.Management.Common.SqlConnectionInfo)
I can not send the mail.I am sending the mails same profile that configured.Before it is working perfectly.Today I send the bulk mails(near about 4000-5000 mails) through the java code. And from that time i can not get any mails.
Please tell me how to solve the problem?

Hello,
Please refer to the following thread:
https://social.technet.microsoft.com/Forums/en-US/c8fa3c2d-9e8a-4886-97bf-264c1b8bc31c/throttling-settings-for-sending-more-that-1500-emails-simultaneously-using-sql-job?forum=exchangesvrsecuremessaging
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Transact-SQL debugger not working in SQL Server 2008: "...debugger does not support SQL Server 2005 or earlier..."

I have recently installed SQL Server 2008. When I try to execute a query against an Access database, I receive this debugging error:
"Unable to start Transact-SQL debugger. The Transact-SQL debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors)"
Nor will the query execute; I get a transport-level error 0. Any thoughts?

Hi Davidmhjr,
>>Unable to start the Transact-SQL Debugger. The Transact-SQL Debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors).
Have you tried to restart the server once you have installed SQL Server 2008? As Naomi N mentioned please check the version of SQL Server you are using.
If you tried to connect to SQL Server 2005 from SQL Server 2008 SSMS, you would not be able to debug and get this error, it happens because T-SQL debugger includes both server-side and client-side components. The server-side debugger components are installed
with each instance of the SQL Server 2008 Database Engine. The client-side components are installed when you install the SQL Server 2008 client-side tools.
So it works with SQL Server 2008 only so far. Another way is you can triy to use SQL Server 2005 SSMS to connect to SQL Server 2005.
More information about configuration requirement to run T-SQL debugger as below, please refer:
There are no configuration requirements to run the Transact-SQL debugger when SQL Server Management Studio is running on the same computer as the instance of the SQL Server Database Engine. However, to run the Transact-SQL debugger when SQL Server Management
Studio is running on a different computer from the instance of the Database Engine, you must enable program and port exceptions by using the Windows Firewall Control Panel application on both computers.
On the computer that is running the instance of the Database Engine, in Windows Firewall, specify the following information:
•Add TCP port 135 to the exceptions list.
•Add the program sqlservr.exe to the exceptions list. By default, sqlservr.exe is installed in C:\Program Files\Microsoft SQL Server\MSSQL10.InstanceName\MSSQL\Binn, where InstanceName is MSSQLSERVER for the default instance, and the instance name for
any named instance.
•If the domain policy requires network communications to be done through IPsec, you must also add UDP port 4500 and UDP port 500 to the exception list.
On the computer that is running SQL Server Management Studio, in Windows Firewall, specify the following information:
•Add TCP port 135 to the exceptions list.
•Add program ssms.exe (SQL Server Management Studio) to the exceptions list. By default, ssms.exe is installed in C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE.
Hope it is helpful.
Regards, Amber zhang

XP_DELETE_FILE NOT WORKING IN SQL SERVER 2005 SP2

Hi All,
I have one job in sql 2005 sp2 that deletes backup older than one week.It is not working.I have checked service account permissions on backup folder and all required permissions and authentications are in place.Please let me know how to troubleshoot the
same.
Regards
Rahul

Check the following:
http://stackoverflow.com/questions/212603/sql-server-xp-delete-file-not-deleting-files
QUOTE: "Note that xp_delete_file is broken in SP2 and won't work on report files;"
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

SQL Server reporting server 2005 having error. 'The report server is not responding. Verify that report server is running and can be accessed from this computer'

Hi team,
I got below error message in SQL Server 2005 reporting service.
''The report server is not responding. Verify that report server is running and can be accessed from this computer'
also in reports, i am getting below error:
"The encrypted value for the "LogonCred" configuration setting cannot be decrypted. (rsFailedToDecryptConfigInformation)
Get Online Help
The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError)
Get Online Help "
Please find below log:
<Header>
<Product>Microsoft SQL Server Reporting Services Version 9.00.4060.00</Product>
<Locale>en-US</Locale>
<TimeZone>Eastern Daylight Time</TimeZone>
<Path>F:\Program Files\Microsoft SQL Server\MSSQL.6\Reporting Services\LogFiles\ReportServer__07_28_2014_09_08_41.log</Path>
<SystemName>MFLDDDBS04</SystemName>
<OSName>Microsoft Windows NT 5.2.3790 Service Pack 2</OSName>
<OSVersion>5.2.3790.131072</OSVersion>
</Header>
w3wp!webserver!1!7/28/2014-09:08:41:: i INFO: Reporting Web Server started
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing ConnectionType to '1' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing ProcessRecycleOptions to '0' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' as specified in Configuration
file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file.
w3wp!resourceutilities!1!7/28/2014-09:08:42:: i INFO: Reporting Services starting SKU: Enterprise
w3wp!resourceutilities!1!7/28/2014-09:08:42:: i INFO: Evaluation copy: 0 days left
w3wp!library!1!7/28/2014-09:08:42:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information., CryptUnprotectData:
Win32 error:13;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information.
w3wp!library!1!7/28/2014-09:08:42:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.FailedToDecryptConfigInformationException: The encrypted value for the "LogonCred" configuration setting cannot be decrypted., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.FailedToDecryptConfigInformationException: The encrypted value for the "LogonCred" configuration setting cannot be decrypted. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The report server has encountered a configuration error. See the report server log files for more information.
   at Microsoft.ReportingServices.Diagnostics.DataProtectionLocal.UnprotectData(Byte[] data, Int32 dwFlags, Boolean transitoryData)
   at Microsoft.ReportingServices.Diagnostics.DataProtectionLocal.LocalUnprotectData(String data, Boolean transitoryData)
   at Microsoft.ReportingServices.Diagnostics.RSConfiguration.DecryptCatalogData(String encryptedData, String element)
   --- End of inner exception stack trace ---

Hi Vivek,
In Reporting Services, values for LogonUser, LogonDomain, and LogonCred are created when the report server connection is configured to use a domain account. As to the error that “The encrypted value for the "LogonCred" configuration setting cannot be decrypted”,
we can know that it relates to the domain account for report server connection.
To fix this issue, we can refer to the following steps:
Log in to SQL Server Database Engine in SQL Server Management Studio.
Under Security folder, give sufficient permissions for your domain account.
Open your Reporting Services Configuration (go to Start -> All Programs -> Microsoft SQL Server 2005 -> Configuration Tools -> Reporting Services Configuration)
Navigate to the Database Setup tab, select ‘Service Credentials’ as the Credentials Type, then type your domain account and password in there. Press Apply.
Restart the Report Server services.
Reference:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2d05b404-83aa-4fb2-bba6-52b587e890ec/sql-2005-rs-configuration-tool-encryption-key-error
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

SQL Server Agent - Job History not being recorded (SQL Server 2005)

I have been trying to get to the bottom of an issue with SQL Server Agent not recording any job history. I am using SQL Server 2005 on a single Windows Server 2008 machine (i.e. no other domain controllers/active directory servers).
The SQL Server Agent service is configured to 'Log On As' NT user account 'sqlagent'. The jobs themselves are executed successfully (all 'Transact-SQL' type steps actually use the 'sa' account) however the there is no actual job history to be found for any
of the jobs -- in the SQL Activity monitor, the 'Last Run Outcome' is always 'Unknown' and the 'Last Run' date is always 'Never' for all jobs; in the SQL Job History Viewer there are no entries for any instances of a job being executed.
The 'sqlagent' NT user account ia a member of the 'Administrators' NT group; the 'Administrators' group appears under Security > Logins on the database server. I have another server that also uses the same setup with a 'sqlagent' NT user account, on that
database server the 'sqlagent' user account appears under Security > Logins and the SQL job history works correctly. I have attempted to add the 'sqlagent' to the Logins on the affected server using the SQL Server Surface Area configuration but this operation
returns an error, detailed below.
Additionally, I have attempted to use the built-in NT system account 'NETWORKSEVICES' to run the SQL Agent Service but this also results in exceptions in the error log and no job history being recorded. The entries in the error logs are very similar to those
from the 'sqlagent' NT user account but instead the user is referred to as 'NT AUTHORITY\ANONYMOUS LOGON' in the error logs, again these are detailed below.
Many thanks in advance for anyone's time and help with this issue!
Arthur
The following errors are raised in SQL Server Agent > Error Logs each time a job is executed:
Date 11/11/2012 18:30:01
Log SQL Agent (Current - 11/11/2012 18:30:00)
Message
[298] SQLServer Error: 18452, Login failed for user ''. The user is not associated with a trusted SQL Server connection. [SQLSTATE 28000]
Date 11/11/2012 18:30:01
Log SQL Agent (Current - 11/11/2012 18:30:00)
Message
[382] Logon to server 'XXXXXXXX' failed (ConnAttemptCachableOp)
If the SQLAgent service is configured to use the NT system account 'NETWORKSERVICE' then the following errors are returned instead:
Date 29/10/2012 18:30:15
Log SQL Agent (Archive #1 - 29/10/2012 18:38:00)
Message
[298] SQLServer Error: 18456, Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [SQLSTATE 28000]
Date 29/10/2012 18:30:15
Log SQL Agent (Archive #1 - 29/10/2012 18:38:00)
Message
[382] Logon to server 'XXXXXXXX' failed (ConnAttemptCachableOp)
I have tried granting the 'sqlagent' NT user account with SysAdmin Server Role privaledges using the SQL Server User Provisioning tool in SQL Server Surface Area Configuration, but this always throws the following, similar error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Error: 18452)
===================================
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18452&LinkId=20476
Server Name: 127.0.0.1,1344
Error Number: 18452
Severity: 14
State: 1
Line Number: 65536
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at sqlprov.SysAdminServerRole.ProvisionInstance(Instance instance, String userName)
at sqlprov.ProvisionTask.Provision(Instance instance, String userName)
at sqlprov.MainForm.ProvisionTasks()

Hi Rama,
Thanks for your reply. I have run the query you specified and can see only one entry with "NTLM" in the auth_scheme column, all of the rest have "SQL". It figures that the entry with "NTLM" is relating to the one NT user account that can successfully log
in to the service (as mentioned in my reply to Nag above, this is the NT user account that installed the service on the machine). I have also executed the same query on the other machine that I mentioned in my original post and this contains two "NTLM" entries,
I'd assume that these relate to the NT user that installed the software and the correctly working "sqlagent" NT user account that is correctly logging the job history on that machine.
I think the problem is very much to do with granting access to new NT user accounts, as per the KB article that you have quoted above. In this case, it is not relating to scenarios 1 or 2 as these relate to SQL Server logins and this issue is about a Windows
Authentication login. As I mentioned to Nag above, I am unable to grant any NT user accounts with access to the service however the NT accounts are all defined locally on the same machine as the SQL server is installed (i.e. there is no domain controller,
active directory controller, etc) so I don't understand how the Windows login cannot be verified.
Any further advice on the issue would be greatly appreciated, please let me know if there is any more information I can provide to help diagnose the problem.
Many thanks!
Arthur

App not versioned error in JDeveloper - ADF with SQL Server 2005

Hello All,
I am developing a sample ADF application. Database is MS SQL Server 2005 SP2. I get below error message. I am trying in parallel to google it... However trying here if any encountered such an issue and had resolved it.
Thanks in advance for your time.
Cheers,
Vagic.
[02:06:19 PM] Deploying Application...
<Feb 23, 2010 2:06:20 PM PST> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application ExmReports is not versioned.>
<Feb 23, 2010 2:06:20 PM PST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1266962779600' for task '0'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
     at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:290)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)

You might need to add the JDBC jar file for SQL Server to the classpath of the integrated WebLogic. See minute 8 here: http://download.oracle.com/otn_hosted_doc/jdeveloper/11gdemos/NBtoJDevProject/NBtoJDevProject.html

Addon in Client is not connecting to SQL Server 2005

Hi, we have an add-on, which is working in SBO 2005 with SQL Server 2000.
When the addon tries to connect to the same DB, restored on a SQL Server 2005, the addon is hanging up on the oCompany.Connect method. But this only happens when we try a remote connection from a SBO client.
If we run the addon from the SBO server, where the SQL Server is running too, the addon completes the connection in the expected way.
The SBO Client is connecting to the server, and works fine, but the addon is not connecting to the server.
We try to connect to the server from the client, using SQL Query Analizer from SQL Server 2000, and it works fine too.
Does anyone knows how to fix this issue?
Thanks

Hi Alejandro, thanks for your response.
After installing SBO Patch 20 the add-on is now connecting fine, so I think it must be an upgrade on the new DI API. I noticed the version changes from 6.80.318 to 6.80.319
I had checked the SQL to confirm is was allowing remote connections.
Thank you guys.

Package developed on SQL Server 2005 SP1 not opening in SQL Server 2005 SP2

Recently I have upgraded my system to SQL Server 2005 SP2 version 9.00.3054; I have developed my packages on SQL Server 2005 SP1 version 9.00.2047. I am unable to open all these packages on SQL Serever SP2 version 9.00.3054 it is giving me error.
Error: Error loading Package.dtsx cannot create an instance of the XML Document Object Model. MSXML may not be registered.
Can any body help me in this?
Thanks in advance

Try the search function.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1446338&SiteID=1

Arc is not implemented for SQL Server 2005 physical model

I added the Arc in my relational model, which is supposed to provide that references are mutually exclusive (so only one refering column can be not null). However there is not any implementation for this in the SQL Server 2005 physical model. The SQL code generated simply ignores the Arc and allows any values for the columns covered by Arc. If we check Oracle physical model. then it generates some trigger, which controls how many columns have values assigned - this is actually an implementation of Arc. But there is nothing of this kind for SQL Server model...
By the way, implementing this Arc by trigger looks like to heavy approach. The very simple table level check constraint will do the same job. But this is a different subject though.
Edited by: Otbl on Nov 3, 2011 7:34 PM

Hi Dmitry,
it's fixed in Data Modeler 3.1 EA2.
Philip

SQL Server 2005: Multi-part identifier could not be bound

Hello,
I use IBM WebSphere Portal and am desperately trying to move data from the default Cloudspace Database to MS SQL Server 2005, of course following the official guidelines.
What happens is that WebSphere's Configuration Wizard fails because of an error caused by the SQL Script. Trouble is, I can't bring it to work not even in the SQL Server Management Studio.
What follows is the code generated by the script. The error is caused by the last "check"-constraint (colored in red).
CREATE TABLE community.APP_DESC (
OID BINARY(18) NOT NULL,
TYPE INTEGER NOT NULL,
APP_NAME NVARCHAR(255) NOT NULL,
IS_ACTIVE INTEGER NOT NULL,
JSR_VERSION NVARCHAR(255),
GUID NVARCHAR(255),
WEB_MOD_OID BINARY(18),
WEB_MOD_SL BINARY(18),
WSRP_PROD_OID BINARY(18),
WSRP_PROD_SL BINARY(18),
DEFAULT_LOCALE NVARCHAR(64),
CREATED BIGINT NOT NULL,
MODIFIED BIGINT NOT NULL,
WSC_GROUP_ID NVARCHAR(255),
CONSTRAINT PK20 PRIMARY KEY NONCLUSTERED (OID),
CONSTRAINT FK20A FOREIGN KEY (WEB_MOD_OID) REFERENCES community.WEB_MOD (OID) ON DELETE CASCADE,
constraint FK20B FOREIGN KEY (WSRP_PROD_OID) REFERENCES community.WSRP_PROD (OID) ON DELETE CASCADE,
CONSTRAINT CC20A CHECK (((community.APP_DESC.WEB_MOD_OID IS NULL) AND (community.APP_DESC.WEB_MOD_SL IS NOT NULL)) OR ((community.APP_DESC.WEB_MOD_OID IS NOT NULL) AND (community.APP_DESC.WEB_MOD_SL IS NULL)))
And that's what SQL Server 2005 told me:
Msg 4104, Level 16, State 1, Line 1
The multi-part identifier "community.APP_DESC.WEB_MOD_OID" could not be bound.
Msg 4104, Level 16, State 1, Line 1
The multi-part identifier "community.APP_DESC.WEB_MOD_SL" could not be bound.
Msg 4104, Level 16, State 1, Line 1
The multi-part identifier "community.APP_DESC.WEB_MOD_OID" could not be bound.
Msg 4104, Level 16, State 1, Line 1
The multi-part identifier "community.APP_DESC.WEB_MOD_SL" could not be bound.
BTW, as this is a generated script I do not have the possibility to change it. Because it has been released by IBM I am rather convinced that it is correct - therefore I was wondering whether SQL Server 2005 has a known bug that makes it refuse "check"-constraints.
Any hint is very appreciated.
Thanks in advance,
adapter

THe problem is that is was probably not made for SQL Server 2005. It should read:
CONSTRAINT PK20 PRIMARY KEY NONCLUSTERED (OID),
CONSTRAINT FK20A FOREIGN KEY (WEB_MOD_OID) REFERENCES community.WEB_MOD (OID) ON DELETE CASCADE,
constraint FK20B FOREIGN KEY (WSRP_PROD_OID) REFERENCES community.WSRP_PROD (OID) ON DELETE CASCADE,
CONSTRAINT CC20A CHECK (((APP_DESC.WEB_MOD_OID IS NULL) AND (APP_DESC.WEB_MOD_SL IS NOT NULL)) OR ((APP_DESC.WEB_MOD_OID IS NOT NULL) AND (APP_DESC.WEB_MOD_SL IS NULL)))
The meaning of the first identifier changed in SQL Server 2005, as this is now the Schema and not the owner. DO you have a chance of using a SQL Server 2000 computer ? In terms of licences you will have a downgrade licence for the SQL Server, otherwise you should ping the IBM guys to provide a compatible script.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de

Configuration note of SQL SERVER 2005

Hello,
Is there a SAP configuration note for SQL 2005 like note 327494 for SQL 2000 ?
Or does someone know if there should be special configuration for SQL SERVER 2005 ?
Pelase advice,
Dimitry

Hello
Please review 879941 Configuration Parameters for SQL Server 2005
thanks
N.P.C

Nvarchar(max) of sql server 2005 is not accessible through Oracle DB Link

hi,
i have created the DB LINK from Oralce 11gR2 to MS Sql Server 2005,
am able to access the view of Sql Server from Oralce,
but the Columns which have Datatype nvarchar(max) in Sql Server am not able to access through DB Link.
can anybody know about this issues?

Pl do not post duplicate threads - Datatype nvarchar(max) not accessable (DB Link from Sql 2005 to Ora 11gR2 )

SQL server 2005 does not allow remote connnections error: 40 w/Synch Manage

I have a local server for B1 that I need to synch to a hosted Webserver. When I go to Synch Manager, I can't connect to the webtools on the hosted webserver even when I enter the IP address (which the firewall has been updated to allow).
When I try to connect is says "an error has occured while establishing 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 connection to SQL server.
I'm not a firewall or Infrastucture expert so I need assistance.
any help would be greatly appreciated!
Heidi

turned out we just needed to turn on remote connections and named pipes for SQL.

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,

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)

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)
Hello,
Make sure your SQL Server service is started.
Make sure TCP\IP and names pipes protocol is enabled
Make sure you have made an exception in firewall for SQL Server connection
Make sure SQL Server browser service is enabled
Make sure you connect with correct name hostname\instance name for named instance,MSSQLSERVER for default instance and Hotname\SQLEXPRESS for express edition.
Please make sure you use port no when connecting to SQL server listeing on different port (hostname\instance ,portno)
http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx
Hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Sql server not in VS 2005s "server explorer"

Similar Messages

Maybe you are looking for