Difference between RPC:Completed and SP:Completed

Hi,
I know that SP refers to stored procedures, and RPC to remote procedure
calls, but I don't know what that means in real life.
I can see in my trace files that each stored procedure has related
RPC:Completed event. So why would anybody include SP:Completed event too?
Any ideas or advices?
Thanks
SP:Completed events would occur if you called a sp from within another sp or
if the sp was initially called in a batch. If you only traced RPC events
you would miss these executions. Sometimes you don't care to see anything
other than the initial call to the server which would either be a RPC or a
batch depending on how the call was made. An RPC only occurs when you call
the sp as a sp. By that I mean you would use the command type of stored
procedure to properly execute a sp as a RPC. If you said the type was text
it would come across as a Batch:Completed and then it would have a
SP:Completed. This is due to the fact each batch gets a plan and each sp
execution gets it's own plan as well. Note that not all columns show up for
SP:Completed as they do for RPC and Batch such as reads, cpu etc.
Andrew J. Kelly SQL MVP
"peja" <peja@.sympatico.ca> wrote in message
news:erFcUZaKGHA.668@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I know that SP refers to stored procedures, and RPC to remote procedure
> calls, but I don't know what that means in real life.
> I can see in my trace files that each stored procedure has related
> RPC:Completed event. So why would anybody include SP:Completed event too?
> Any ideas or advices?
> Thanks
>

device_type = 7 in backupmediafamily?

Does anyone know what device_type = 7 means in the
msdb..backupmediafamily table? The physical_device_name values are
strange (i.e., "model_00__9834ee39_40a6_4d36_9ba6_a65daaac40b9_") .
Records for backups that I've initiated have device_type = 2 or 102
and the physical_device_name is the disk path of the backup file.
The SQL documentation shows six valid values for device_type: 2 or 102
= disk, 5 or 105 = tape, 6 or 106 = pipe.
Any insight is greatly appreciated.
TIA,
Doug
Looks like a virtual_device used to create backups using the VBDI API. The
Veritas SQL Server client uses this among others.
Sincerely,
Anthony Thomas
"Doug" wrote:

> Does anyone know what device_type = 7 means in the
> msdb..backupmediafamily table? The physical_device_name values are
> strange (i.e., "model_00__9834ee39_40a6_4d36_9ba6_a65daaac40b9_") .
> Records for backups that I've initiated have device_type = 2 or 102
> and the physical_device_name is the disk path of the backup file.
> The SQL documentation shows six valid values for device_type: 2 or 102
> = disk, 5 or 105 = tape, 6 or 106 = pipe.
> Any insight is greatly appreciated.
> TIA,
> Doug
>

device_type = 7 in backupmediafamily?

Does anyone know what device_type = 7 means in the
msdb..backupmediafamily table? The physical_device_name values are
strange (i.e., " model_00__9834ee39_40a6_4d36_9ba6_a65daa
ac40b9_").
Records for backups that I've initiated have device_type = 2 or 102
and the physical_device_name is the disk path of the backup file.
The SQL documentation shows six valid values for device_type: 2 or 102
= disk, 5 or 105 = tape, 6 or 106 = pipe.
Any insight is greatly appreciated.
TIA,
DougLooks like a virtual_device used to create backups using the VBDI API. The
Veritas SQL Server client uses this among others.
Sincerely,
Anthony Thomas
"Doug" wrote:

> Does anyone know what device_type = 7 means in the
> msdb..backupmediafamily table? The physical_device_name values are
> strange (i.e., " model_00__9834ee39_40a6_4d36_9ba6_a65daa
ac40b9_").
> Records for backups that I've initiated have device_type = 2 or 102
> and the physical_device_name is the disk path of the backup file.
> The SQL documentation shows six valid values for device_type: 2 or 102
> = disk, 5 or 105 = tape, 6 or 106 = pipe.
> Any insight is greatly appreciated.
> TIA,
> Doug
>

device_type = 7 in backupmediafamily?

Does anyone know what device_type = 7 means in the
msdb..backupmediafamily table? The physical_device_name values are
strange (i.e., "model_00__9834ee39_40a6_4d36_9ba6_a65daaac40b9_").
Records for backups that I've initiated have device_type = 2 or 102
and the physical_device_name is the disk path of the backup file.
The SQL documentation shows six valid values for device_type: 2 or 102
= disk, 5 or 105 = tape, 6 or 106 = pipe.
Any insight is greatly appreciated.
TIA,
DougLooks like a virtual_device used to create backups using the VBDI API. The
Veritas SQL Server client uses this among others.
Sincerely,
Anthony Thomas
"Doug" wrote:
> Does anyone know what device_type = 7 means in the
> msdb..backupmediafamily table? The physical_device_name values are
> strange (i.e., "model_00__9834ee39_40a6_4d36_9ba6_a65daaac40b9_").
> Records for backups that I've initiated have device_type = 2 or 102
> and the physical_device_name is the disk path of the backup file.
> The SQL documentation shows six valid values for device_type: 2 or 102
> = disk, 5 or 105 = tape, 6 or 106 = pipe.
> Any insight is greatly appreciated.
> TIA,
> Doug
>

device is ambiguous in the namespace microsoft.directx.direc3d

Can anybody tell me what this error message means. I get it when trying to use directx3d. The code is included below.

I have checked and double checked that I have all the necessary references and includes. Obviously I am missing something.
Thanks Dick

Imports System

Imports System.Drawing

Imports System.Windows.Forms

Imports Microsoft.DirectX

Imports Microsoft.DirectX.Direct3D

Public Class Form1

Inherits System.Windows.Forms.Form

Dim device As Device ' Our rendering device

#Region "Windows Form Designer generated code "

Public Sub New()

MyBase.New()

'This call is required by the Windows Form Designer.

InitializeComponent()

End Sub

'Form overrides dispose to clean up the component list.

Protected Overloads Overrides Sub Dispose(ByVal Disposing As Boolean)

If Disposing Then

If Not components Is Nothing Then

components.Dispose()

End If

End If

MyBase.Dispose(Disposing)

End Sub

'Required by the Windows Form Designer

#End Region

Public Function InitializeGraphics() As Boolean

Try

' Now let's setup our D3D stuff

Dim presentParams As PresentParameters = New PresentParameters()

presentParams.Windowed = True

presentParams.SwapEffect = SwapEffect.Discard

device = New Device(0, DeviceType.Hardware, this, CreateFlags.SoftwareVertexProcessing, presentParams)

Return True

Catch

Return False

End Try

End Function

Private Sub Render()

If device Is Nothing Then

Exit Sub

End If

'Clear the backbuffer to a blue color

device.Clear(ClearFlags.Target, System.Drawing.Color.Blue, 1.0F, 0)

'Begin the scene

device.BeginScene()

' Rendering of scene objects can happen here

'End the scene

device.EndScene()

device.Present()

End Sub

Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

If Not InitializeGraphics() Then

MessageBox.Show("Could not initialize Direct3D. This tutorial will exit.")

Exit Sub

End If

Me.Show()

' While the form is still valid, render and process messages

Do While Me.Created

Render()

Application.DoEvents()

Loop

End Sub

End Class

This is a SQL Server forum. I think you've accidentally posted to the wrong place...

device is ambiguous in the namespace microsoft.directx.direc3d

Can anybody tell me what this error message means. I get it when trying to use directx3d. The code is included below.

I have checked and double checked that I have all the necessary references and includes. Obviously I am missing something.
Thanks Dick

Imports System

Imports System.Drawing

Imports System.Windows.Forms

Imports Microsoft.DirectX

Imports Microsoft.DirectX.Direct3D

Public Class Form1

Inherits System.Windows.Forms.Form

Dim device As Device ' Our rendering device

#Region "Windows Form Designer generated code "

Public Sub New()

MyBase.New()

'This call is required by the Windows Form Designer.

InitializeComponent()

End Sub

'Form overrides dispose to clean up the component list.

Protected Overloads Overrides Sub Dispose(ByVal Disposing As Boolean)

If Disposing Then

If Not components Is Nothing Then

components.Dispose()

End If

End If

MyBase.Dispose(Disposing)

End Sub

'Required by the Windows Form Designer

#End Region

Public Function InitializeGraphics() As Boolean

Try

' Now let's setup our D3D stuff

Dim presentParams As PresentParameters = New PresentParameters()

presentParams.Windowed = True

presentParams.SwapEffect = SwapEffect.Discard

device = New Device(0, DeviceType.Hardware, this, CreateFlags.SoftwareVertexProcessing, presentParams)

Return True

Catch

Return False

End Try

End Function

Private Sub Render()

If device Is Nothing Then

Exit Sub

End If

'Clear the backbuffer to a blue color

device.Clear(ClearFlags.Target, System.Drawing.Color.Blue, 1.0F, 0)

'Begin the scene

device.BeginScene()

' Rendering of scene objects can happen here

'End the scene

device.EndScene()

device.Present()

End Sub

Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

If Not InitializeGraphics() Then

MessageBox.Show("Could not initialize Direct3D. This tutorial will exit.")

Exit Sub

End If

Me.Show()

' While the form is still valid, render and process messages

Do While Me.Created

Render()

Application.DoEvents()

Loop

End Sub

End Class

This is a SQL Server forum. I think you've accidentally posted to the wrong place...