Subqueries with NOT EXISTS
Subqueries with NOT EXISTS NOT EXISTS works like EXISTS, except the WHERE clause in which it is used is satisfied if no rows are returned by the subquery. For example, to find the names of publishers who do not publish business books: USE pubs SELECT pub_name FROM publishers WHERE NOT EXISTS (SELECT * FROM titles WHERE pub_id = publishers.pub_id AND type = 'business') Here is the result set: pub_name ---------------------------------------- Binnet & Hardley Five Lakes Publishing Ramona Publishers GGG&G Scootney Books Lucerne Publishing (6 row(s) affected) This query finds the titles for which there have been no sales. USE pubs SELECT title FROM titles WHERE NOT EXISTS (SELECT title_id FROM sales WHERE title_id = titles.title_id) title ---------------------------------- The Psychology of Computer Cooking Net Etiquette (2 row(s) affected) See Also
CONQUEST SOFTWARE SOLUTIONS - Tools for Oracle development, database administration, SQL and PL/SQL formatting, analysis and flowcharting, oracle development tools, pl/sql gui, plsql ide, pl/sql tools, pl/sql ide, pl/sql environment, pl/sql development, p
ClearSQL 6.5 is a code review and quality control tool for Oracle PL/SQL. Its code review feature gives recommendations for better coding style and checks for error-prone places in your project. ClearSQL 6.5 analyzes thousands of PL/SQL scripts and Oracle Forms PL/SQL with only a few clicks. It provides a quick look at the most important analysis summaries and tracks changes to PL/SQL code and analysis results. Key Features Coding standards enforcement Flowcharts, Call Tree diagrams and CRUD matrices Automated project and database analysis (Command line support) Support for PL/SQL of Oracle Forms Powerful and Intuitive Graphical User Interface
Accessing Data with ADO
For performance and reliability reasons, it is strongly recommended that you use a client-server database engine for the deployment of data driven Web applications that require high-demand access from more than approximately 10 concurrent users. Although ADO works with any OLE DB compliant data source, it has been extensively tested and is designed to work with client server databases such as SQL Server. ASP supports shared file databases (Access or FoxPro) as valid data sources. Although some ASP example code use a shared file database, it is recommended that these types of database engines be used only for development purposes or limited deployment scenarios. Shared file databases may not be as well suited as client-server databases for very high-demand, production-quality Web applications. If you are developing an ASP database application intended to connect to a remote SQL Server database you should also be aware of the following issues: Choosing Connection Scheme for SQL Server
How To Set the SQL Server Network Library in an ADO Connection String
SQL Server allows you to choose from a number of different network libraries that you can use when connecting. You can configure these network libraries when you create a data source name (DSN) for your data source. However, an alternative way to specify the DSN is to pass in the network library, which you want to use, with the connection string. This article describes how to specify the network library that you want to use for connecting to SQL Server when connecting from a Visual Basic application that uses ActiveX Data Objects (ADO). SQL Server allows you to use the following network libraries when establishing a connection. Note Make sure that User ID has the appropriate permissions to perform this operation on the database. For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base: ( ) INF: ODBC SQL Server Connection Parameters ( )
asp classic - Server-side Javascript in production fails to open connection to a named instance of SQL2008
SQL Server Named Pipe Connection...
For the purpose of assisting others with this problem/solution I wish to add to the scenario. BTW my solution above is a result of reading MS articles and allot of trial and error. We have 2 x 2003 servers here. 1 x internal only (has SQL Server) and 1 x external (No data store) To eliminate any potential firewall etc problems (correct, I am not very network savvy), I was testing this remote connection from my dev machine (third machine XP) to the internal only 2003 machine. Both of these machines have SQL Server installed and a duplicate set of web pages. After implementing the solution in my previous post I had remote connectivity between these two machines (my dev machine and the 2003 internal only box) using: "Provider=sqloledb;Data Source=xx;Initial Catalog=xx;User Id=xx;Password=xx;" When I tried to connect from the external 2003 machine to the internal only 2003 machine I was getting the old 'sql server does not exist or access denied' error (original problem and error)
sql server - How to get a list of users for all instance's databases
Named Pipes Provider, error: 40 - Could not open a connection to SQL Server - SQL Protocols
This error was most frequently hitted by our customers, and in this post, give a brief summary of troubleshooting tips for this specific error message. First, take a look at below MSDN forum link lists about this topic: The various causes fall into five categories: 1 Incorrect connection string, such as using SqlExpress. 2 NP was not enabled on the SQL instance. 3 Remote connection was not enabled. 4 Server not started, or point to not a real server in your connection string. 5 Other reasons such as incorrect security context. Let's go throught the detail one by one: I. a.
Andy Leonard : Quick Database Connectivity Testing
Introduction Ever find yourself needing to test connectivity, but you’re on a machine with no client tools? It happens to me occasionally. Here’s one trick to help: UDL files Right-click on the Windows Desktop, hover over New, and click Text Document: Rename the file to test.udl: Because you are changing the extension, you will be prompted: Click Yes. Click the Test Connection button to test connectivity: Conclusion There you have it – a way to test connectivity without database client tools installed!
Overview of the SQL Server Browser service
Problem A new service, SQL Server Browser, was introduced with SQL Server 2005 and is also used with SQL Server 2008. In this tip I will cover what this is and how to use this service to improve your SQL Server environment. Solution The SQL Server Browser service introduced in SQL Server 2005, runs as a Windows service and it is an extension of SQL Server Resolution Protocol (SSRP) of SQL Server 2000. To configure a better and safe access mechanism for SQL Server, a DBA should have proper understanding of the SQL Server Browser service. Below I will discuss the access mechanism with reference to the TCP/IP protocol. How to access SQL Server Browser service SQL Server Browser service can be configured during installation or after installation it can be accessed in number of ways. Through Windows Services MMC. It should be noted that SAC just provides access to start/stop or to change the startup type for the SQL Server Browser service. What if SQL Server Browser service is stopped? Next Steps
