earching for specific content or a specific column is a common task for a SQL Server administrator or developer. If you’re familiar with the database or it’s documented, searches aren’t a problem. However, you’re not always that lucky. Sometimes the database you need to search is unfamiliar or undocumented, which
ike Delphi’s other development platforms, Delphi for .NET offers a wide range of data access options for ASP.NET developers. These include support for the generic foundation class library (FCL) data access classes (ODBC and OleDb), dbExpress drivers, BDP for .NET providers, as well as support for all third-party solutions that
ending email from SQL Server can be a useful way to keep yourself or the system’s administrator informed of any errors and alerts, but depending on your version of SQL Server, the setup can be quite involved or relatively simple. With SQL Server 2000, the setup requires a heavy email
uppose you have a constantly growing database that currently contains 75 tables. Like any other database, a significant percentage of the tables carry metadata (i.e., the kind of data that appears as checkboxes or dropdown lists in your web form). Whenever you add a new table, you have to implement
hen creating a connection to foreign data, the .NET configuration wizard is a great place to start. Not only will it create a point-and-click connection for you, but it also can quickly and easily produce a control for users to retrieve, display, and manipulate the data. However, the wizard seldom
imiting the number of records in a group is a common request. For example, suppose your sales director requests a custom report showing the top salesperson for each region. At first, limiting the number of records in that group seems simple: Use GROUP BY and TOP, but that doesn’t work.
he ORA-8177 error “Cannot serialize access” often frustrates developers and testers of Oracle database-driven applications that employ SERIALIZABLE isolation levels. These errors can be particularly vexing because they stem from rows that are not being modified by any other transaction (INSERT/UPDATE/DELETE) than the one currently underway. Not only are the
any MS Access and SQL Server developers are moving to .NET. It’s a natural migration because these developers can use .NET to create the same types of solutions they would in either database, but there’s much more to .NET than your ordinary database. After all, .NET is not a database?it
ou might expect all SQL Server’s clauses to support a column alias. As reasonable as that assumption seems, SQL Server can’t honor a column alias in that way. If you refer to an aliased column in another clause, SQL Server returns an error?surprise! Figure 1 shows the result of running