Command to display SQL Statements

Does anyone know the command to display the whole SQL statement for a
connection after apply sp3?
Thanks,
LijunTake a look at the fn_get_sql topic in books online, assuming you updated...
"Lijun Zhang" <nospam@.nospam.nospam> wrote in message
news:#UPomeMnDHA.2592@.TK2MSFTNGP10.phx.gbl...
> Does anyone know the command to display the whole SQL statement for a
> connection after apply sp3?
> Thanks,
> Lijun
>|||Hi Lijun,
I agree with Aaron, you can use the fn_get_sql function to retrieve the SQL handle (sql_handle
column of the sysprocesses) and help you diagnose problematic processes.
You can also use "DBCC INPUTBUFFER" to easily display the LAST statement sent from a
client. The system process ID (SPID) for the user connection can be displayed in the output of
the sp_who system stored procedure.
Does that answer your question? Please feel free to post in the group if this solves your
problem or if you would like further assistance.
Best regards,
Billy Yao
Microsoft Online Partner Support

Come on! Just apply the +@*?&%&? settings! :p

Hi,
No matter how many times I push the god damn "Apply" button in the report
manager (parameters section) it never Applies my changes. The page doesn't
even refresh.
Im getting quite frustrated with this problem and I can't seem to find an
hint on what could possibly be causing it.
Thx for any input on this.This is usually caused by an issues with ASP.Net not being configured
correctly. You could try running aspnet_regiis.exe -i to reinstall asp.net
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:52F48552-990B-4DC2-8A0D-487547221EBC@.microsoft.com...
> Hi,
> No matter how many times I push the god damn "Apply" button in the report
> manager (parameters section) it never Applies my changes. The page doesn't
> even refresh.
> Im getting quite frustrated with this problem and I can't seem to find an
> hint on what could possibly be causing it.
> Thx for any input on this.|||Well that is just not a risk im willing to take in a production environment
... we're due to change our servers in a few weeks so I'll just wait until
then and see if the problem disapears ... (fingers crossed :S )
"Daniel Reib (MSFT)" wrote:
> This is usually caused by an issues with ASP.Net not being configured
> correctly. You could try running aspnet_regiis.exe -i to reinstall asp.net
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Eric" <Eric@.discussions.microsoft.com> wrote in message
> news:52F48552-990B-4DC2-8A0D-487547221EBC@.microsoft.com...
> > Hi,
> >
> > No matter how many times I push the god damn "Apply" button in the report
> > manager (parameters section) it never Applies my changes. The page doesn't
> > even refresh.
> >
> > Im getting quite frustrated with this problem and I can't seem to find an
> > hint on what could possibly be causing it.
> >
> > Thx for any input on this.
>
>

Comclust.exe Windows 2003 Server

From what I have read you do have to apply COMCLUST.exe to
a Windows 2003 Server on a cluster server with SQL Server
2000 Enterprise?
If this is not correct, I have already loaded Windows 2003
Server on a cluster with SQL Server 2000 Enterprise.
How would I correct this problem?
Thanks,
Mark P.
Hi
Look at
http://www.microsoft.com/technet/pro.../newclust.mspx
"
MSDTC Configuration
The Microsoft Distributed Transaction Coordinator (MSDTC) can now be
configured once, and then be replicated to all nodes.
Benefits
? Easier Administration In previous versions, the COMCLUST.EXE utility had
to be run on each node in order to cluster the MSDTC. It is now possible to
configure MSDTC as a resource type, assign it to a resource group, and have
it automatically configured on all cluster nodes.
"
Regards
Mike
"Mark P." wrote:

> From what I have read you do have to apply COMCLUST.exe to
> a Windows 2003 Server on a cluster server with SQL Server
> 2000 Enterprise?
> If this is not correct, I have already loaded Windows 2003
> Server on a cluster with SQL Server 2000 Enterprise.
> How would I correct this problem?
> Thanks,
> Mark P.
>
|||Hi Mark,
You wrote " From what I have read you do have to apply COMCLUST.exe to a Windows 2003 Server on a cluster server with SQL Server 2000 Enterprise?"
I would be curious to know where it was written that we need to run comclust.exe on Win2003 cluster. It is true for Windows 2000 cluster and not for 2003.
Here are some Microsoft KB articles that has information for MSDTC on Windows 2003
How to Configure Microsoft Distributed Transaction Coordinator on a Windows Server 2003 Cluster
http://support.microsoft.com/?id=301600
How to enable Network DTC access in Windows Server 2003
http://support.microsoft.com/?kbid=817064
You wrote "If this is not correct, I have already loaded Windows 2003 Server on a cluster with SQL Server 2000 Enterprise. How would I correct this problem?"
You DO NOT need to configure MSDTC as a clustered resource for SQL Server 2000 cluster to work. You need MSDTC only if you are doing distributed transactions.
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx