To insert the results of a stored procedure into a temporary table in SQL Server, you can follow these steps. The specific method you use might depend on the structure of the data returned by the stored procedure and whether you are using SQL Server to create the temporary table or it already exists.

If the Temporary Table Does Not Exist

You can use the INSERT INTO ... EXEC command to insert the results directly into a temporary table. However, this requires that the temporary table be created beforehand. Here’s how you can do it:

1. Create a Temporary Table: First, you need to define the structure of the temporary table to match the output of the stored procedure.

CREATE TABLE #TempTable ( Column1 DataType, Column2 DataType, ... );

2. Insert Data from Stored Procedure: After creating the temporary table, you can insert the data from the stored procedure into the table.

INSERT INTO #TempTable
EXEC YourStoredProcedureName @Parameter1, @Parameter2, ...;

If the Temporary Table Already Exists

If the temporary table already exists and you want to insert additional data into it from a stored procedure, you can follow the same INSERT INTO ... EXEC pattern as shown above.

Using OPENROWSET

Another method involves using the OPENROWSET command, but this requires the Ad Hoc Distributed Queries server configuration option to be enabled. This method can directly insert the results into a temporary table without explicitly creating it first but is generally less preferred due to security and configuration implications.

INSERT INTO #TempTable
SELECT * 
FROM OPENROWSET('SQLNCLI', 'Server=localhost;Trusted_Connection=yes;',
    'EXEC YourDatabase.dbo.YourStoredProcedureName @Parameter1, @Parameter2, ...');

Note: Replace YourDatabase, YourStoredProcedureName, Column1, Column2, …, DataType, and @Parameter1, @Parameter2, … with the actual database name, stored procedure name, column names, data types, and parameters of your stored procedure.

Keep in mind that not all methods work in every situation, especially when dealing with complex stored procedures that might return multiple result sets or have dynamic output structures. For stored procedures with multiple result sets, you might need to handle each result set individually.