Latest Event Updates

Creating a Linked Server

Posted on Updated on

Sometimes life is a lot easier if you don’t have to work with flat files. Here are some methods to link to other servers (i.e. DB2) or to SQL.

Linking to Microsoft Access 2007

— THE INITIAL SETUP

EXEC sp_addlinkedserver
@server = N’MSACCESS’,
@provider = N’Microsoft.ACE.OLEDB.12.0′,
@srvproduct = N’Access2007′,
@datasrc = N’C:\Users\Chris\Documents\MyDatabase.accdb’
GO

— SET UP LOGIN MAPPING
EXEC sp_addlinkedsrvlogin
@rmtsrvname = @@servername,
@useself = N’TRUE’,
@locallogin = NULL,
@rmtuser = N’MSACCESS’,
@rmtpassword =
GO

— TO SEE ALL OF THE TABLES
EXEC sp_tables_ex N’MSACCESS’
GO

— SELECTING THE TABLES

SELECT ID, FirstName, LastName
FROM [MSACCESS]…[Customer]

IF YOU GET THIS ERROR MESSAGE

Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 41
The OLE DB provider “SQL Server” for linked server “(null)” reported an error. The provider did not give any information about the error.
Msg 7330, Level 16, State 2, Procedure sp_tables_ex, Line 41
Cannot fetch a row from OLE DB provider “SQL Server” for linked server “(null)”.

1. Go to SQL Server Management Studio

2. Server Objects

3. Linked Servers

Providers

4. Left click on Microsoft.ACE.OLEDB.12.0

5. Click on Properties

6. Check Allow inprocess

7. Click Ok

Now re-run the query. It should work.

This is how the properties screen looks like.

SQL Linked Server
SQL Linked Server

If you get this message, The Maximum Connection Limit, click on the link to see correction.

Here’s a great article I found from StarQuest regarding DB2 with SQL.

StarQuest Technical Documents

How to Use a Microsoft SQL Server Linked Server to Access DB2 with StarSQL

Last Update: 12 May 2009
Product: StarSQL
Version: 5.x
Article ID: SQV00SQ004

Abstract

SQL Server linked servers can be used to access DB2 through a StarSQL ODBC data source. This document demonstrates how to add and use a linked server. These instructions apply to SQL Server 7, SQL Server 2000, SQL Server 2005, and SQL Server 2008.

Solution

Perform the following steps to configure, test, and use a linked server.

StarSQL (64-bit) users should review the StarQuest Technical Document Considerations for using StarSQL (64-bit) with SQL Server 2005/2008.

Configure a Linked Server

  1. Launch the SQL Server 7/2000 Enterprise Manager or SQL Server 2005/2008 Management Studio.
  2. Under the Security folder (SQL Server 7/2000) or the Server Objects folder (SQL Server 2005/2008), right-click on Linked Servers and select New Linked Server.
  3. Enter in a name for the Linked Server and choose “Other data source”. Do not use any spaces or special characters in the Linked Server name.
  4. Select “Microsoft OLE DB Provider for ODBC Drivers” as the Provider Name. On SQL Server 2005/2008, enter MSDASQL for the Product Name.
  5. In the “Data source” field, enter in the name of the ODBC system data source you wish to use. Note that you must enter in the Data Source name exactly as it is shown in the ODBC Data Source Administrator.
  6. For SQL Server 7/2000, click the “Security” tab and select “Be made with this security context”. For SQL Server 2005/2008, select the Security page and select “Be made using this security context”. Enter a valid remote user/login (user ID) and password for the remote host.
  7. Leave the remaining fields blank and click OK to save the linked server configuration.

Test the Linked Server

If an error occurs while testing the linked server connection, review the error and make changes to the linked server configuration as necessary.

SQL Server 7/2000:

In the Enterprise Manager, expand the new linked server and click on Tables to display a table list.

SQL Server 2005:

In the Management Studio, click on the New Query button and execute a query using the samples below as a guideline.

SQL Server 2008:

In the Management Studio, expand the linked server node and then expand the Catalogs node. Click on the node for the linked server and expand the Tables to view a table list.

Sample Linked Server SQL Syntax

The following examples demonstrate how to use a linked server to execute SELECT, INSERT, UPDATE, and DELETE statements.  Execute these statements in either the SQL Server 7/2000 Query Analyzer or the SQL Server 2005/2008 New Query field. These examples assume the following:

  • “STARSQLDSN” is a linked server that accesses DB2 through a StarSQL data source.
  • TITLES is a valid table located within a library (or with a schema name) called BOOKS, TITLE is a valid column in the TITLES table.

To perform a SELECT on the table:

SELECT * FROM STARSQLDSN..BOOKS.TITLES

OR

SELECT * FROM OPENQUERY (STARSQLDSN, ‘SELECT * FROM BOOKS.TITLES’)

To INSERT a row into the table:

INSERT INTO STARSQLDSN..BOOKS.TITLES (TITLE) VALUES (‘The Grapes of Wrath’)

OR

INSERT INTO OPENQUERY (STARSQLDSN, ‘SELECT * FROM BOOKS.TITLES’) (TITLE) VALUES (‘The Grapes of Wrath’)

To UPDATE a row in the table:

UPDATE STARSQLDSN..BOOKS.TITLES SET TITLE = ‘Of Mice and Men’ WHERE TITLE = ‘The Grapes of Wrath’

OR

UPDATE OPENQUERY (STARSQLDSN, ‘SELECT * FROM BOOKS.TITLES’) SET TITLE = ‘Of Mice and Men’ WHERE TITLE = ‘The Grapes of Wrath’

To DELETE a row in the table:

DELETE STARSQLDSN..BOOKS.TITLES WHERE TITLE = ‘The Grapes of Wrath’

OR

DELETE OPENQUERY (STARSQLDSN, ‘SELECT * FROM BOOKS.TITLES’) WHERE TITLE = ‘The Grapes of Wrath’

NOTES:

  • To perform DELETE or UPDATE operations, the target table must have a unique index. For more information, please refer to the section titled UPDATE and DELETE Requirements for OLE DB Providers in the SQL Server Books Online.
  • If the table being accessed has an index defined on more than 16 columns, you may receive this error message:OLE DB provider “MSDASQL” for linked server “” returned an invalid index definition for table “””.””.”””.

As a workaround, either use the OPENQUERY syntax to query this table or remove the offending index. Refer to the “Maximum Capacity Specifications for SQL Server” section of the SQL Server Books Online for more information.

OPENQUERY Vs LinkedServer

Posted on Updated on

What’s the differences between OPENQUERY vs. Linked Server?

  1. OPENQUERY uses the source server’s processing power to query the data
  2. OPENQUERY returns the result set specific to the WHERE clause making it faster
  3. LinkedServer uses the local server processing power to query all of the source’s data and then reprocesses the data to return the result set
  4. LinkedServer is not a direct call to the source server

How to use OPENQUERY and LinkedServer

ORACLE represents the Providers name under the Linked Servers, Server Objects in SQL MSSMS. (MSSMS -> Object Explorer -> Database -> Server Objects -> Linked Servers – > Providers)

OPENQUERY

SELECT * FROM OPENQUERY(ORACLE,’SELECT * FROM PAYMASTR WHERE CHECK_ID = 1′)

LinkedServer

SELECT * FROM ORACLE.DATABASENAME.dbo.PAYMASTR WHERE CHECK_ID = 1

Creating a Temp Table on the Fly

Posted on Updated on

Sometimes we need to create a temporary table on the fly to hold our data for whatever reasons. Here is one approach in creating a temporary table on the fly.

–LOCAL SCOPE
–ONLY YOU CAN SEE THIS TEMP TABLE

SELECT *
INTO #forMe
FROM Customer

SELECT * FROM #forMe

–GLOBAL SCOPE
–EVERYONE CAN SEE THIS TEMP TABLE

SELECT *
INTO ##forEveryone
FROM Customer

SELECT * FROM ##forEveryone

DROP TABLE #forMe
DROP TABLE ##forEveryone

Recover a Deleted Stored Procedure

Posted on Updated on

To recover a deleted object, the SQL Service MUST NOT be restarted. If the SQL Service has been restarted then you won’t be able to find your deleted Stored Procedure.

SELECT A.objtype, B.text, C.query_plan
FROM sys.dm_exec_cached_plans A
CROSS APPLY sys.dm_exec_sql_text ( A.plan_handle ) B
CROSS APPLY sys.dm_exec_query_plan ( A.plan_handle ) C
WHERE B.text LIKE ‘%Alter%’

Check if TABLE exist

Posted on Updated on

Check if the table exists before dropping the table.

IF OBJECT_ID(‘dbo.Customer‘) IS NOT NULL
     DROP TABLE dbo.Customer
ELSE
     PRINTTable already exist

Find SQL Version installed

Posted on Updated on

SQL Versions: 2005, 2008, 2008 R2, 2012, 2014

If you need to see the specific version of SQL you’re running.

SELECT @@VERSIONN

Find current Service Pack installed

Posted on

SQL Versions: 2005, 2008, 2008 R2, 2012, 2014

If you need to see the specific version of SQL Service Pack installed. This SP is not the same as the Windows OS SP.

SELECT SERVERPROPERTY(‘ProductLevel‘)