Error when trying to save or write to table

Hi,
I am doing a tuning exercise on a SQL 2K5 instance, I am encountering
a problem when Profiler goes to create a table. I have profiled
Profiler and have extracted the following code
CREATE TABLE [dbo].[con1] ([RowNumber] int IDENTITY(0,1) PRIMARY KEY,
[EventClass] int NULL,[Duration] bigint NULL,,
[TextData] ntext NULL,[SPID] int NULL,[BinaryData] image NULL,[CPU]
int NULL,[Reads] bigint NULL,[Writes] bigint NULL,[ApplicationName]
nvarchar(128) NULL,[ClientProcessID] int NULL,[DatabaseID] int NULL,
[DatabaseName] nvarchar(128) NULL,[EventSequence] int NULL,
[EventSubClass] int NULL,[HostName] nvarchar(128) NULL,[IntegerData]
int NULL,[IsSystem] int NULL,[LoginName] nvarchar(128) NULL,[LoginSid]
image NULL,[NTDomainName] nvarchar(128) NULL,[NTUserName]
nvarchar(128) NULL,[RequestID] int NULL,[ServerName] nvarchar(128)
NULL,[SessionLoginName] nvarchar(128) NULL,[StartTime] datetime NULL,
[TransactionID] bigint NULL)
As you can see, after Duration (the 3rd column), there is a double
comma inserted which of course is erroring.
This occurs when defining a table to save to prior to running the
trace, and defining a table after running the trace.
I have tried the standard profiler which appears to work fine.
I also updated to SP2 CTP (this is a test server) because it appeared
to be an issue simular to this http://support.microsoft.com/?
kbid=925335.
A quick response would be appreciated as I am a contractor and I am on
tight timescales.
Cheers
Steve
Steve,
I don't know how to fix the error with profiler but I recommend you not do
that in the fist place. Tracing to a table can be a huge performance hit and
can skew your results. It is recommended that you trace directly to a file
using sp_trace_create and then use fn_trace_gettable to retrieve the data.
You can do something like this to put the trace results in a table:
SELECT * INTO YourTable FROM fn_trace_gettable(xxx)
If you already have a trace in profiler you can save it to a file and do the
same.
Andrew J. Kelly SQL MVP
"Steve L" <steve_lawrenson@.tiscali.co.uk> wrote in message
news:1170411376.241148.280690@.v33g2000cwv.googlegr oups.com...
> Hi,
> I am doing a tuning exercise on a SQL 2K5 instance, I am encountering
> a problem when Profiler goes to create a table. I have profiled
> Profiler and have extracted the following code
> CREATE TABLE [dbo].[con1] ([RowNumber] int IDENTITY(0,1) PRIMARY KEY,
> [EventClass] int NULL,[Duration] bigint NULL,,
> [TextData] ntext NULL,[SPID] int NULL,[BinaryData] image NULL,[CPU]
> int NULL,[Reads] bigint NULL,[Writes] bigint NULL,[ApplicationName]
> nvarchar(128) NULL,[ClientProcessID] int NULL,[DatabaseID] int NULL,
> [DatabaseName] nvarchar(128) NULL,[EventSequence] int NULL,
> [EventSubClass] int NULL,[HostName] nvarchar(128) NULL,[IntegerData]
> int NULL,[IsSystem] int NULL,[LoginName] nvarchar(128) NULL,[LoginSid]
> image NULL,[NTDomainName] nvarchar(128) NULL,[NTUserName]
> nvarchar(128) NULL,[RequestID] int NULL,[ServerName] nvarchar(128)
> NULL,[SessionLoginName] nvarchar(128) NULL,[StartTime] datetime NULL,
> [TransactionID] bigint NULL)
> As you can see, after Duration (the 3rd column), there is a double
> comma inserted which of course is erroring.
> This occurs when defining a table to save to prior to running the
> trace, and defining a table after running the trace.
> I have tried the standard profiler which appears to work fine.
> I also updated to SP2 CTP (this is a test server) because it appeared
> to be an issue simular to this http://support.microsoft.com/?
> kbid=925335.
> A quick response would be appreciated as I am a contractor and I am on
> tight timescales.
> Cheers
> Steve
>
|||On 2 Feb, 14:11, "Andrew J. Kelly" <sqlmvpnooos...@.shadhawk.com>
wrote:
> Steve,
> I don't know how to fix the error with profiler but I recommend you not do
> that in the fist place. Tracing to a table can be a huge performance hit and
> can skew your results. It is recommended that you trace directly to a file
> using sp_trace_create and then use fn_trace_gettable to retrieve the data.
> You can do something like this to put the trace results in a table:
> SELECT * INTO YourTable FROM fn_trace_gettable(xxx)
> If you already have a trace in profiler you can save it to a file and do the
> same.
> --
> Andrew J. Kelly SQL MVP
> "Steve L" <steve_lawren...@.tiscali.co.uk> wrote in message
> news:1170411376.241148.280690@.v33g2000cwv.googlegr oups.com...
>
>
>
>
>
>
> - Show quoted text -
Hi Andrew
thanks for the response, I will use the method above as a workaround
and thanks for that information. It would be nice to know if this is a
recognised issue by MS and what their recommended workarounds are for
it.
Cheers
Steve L

Error when running Profiler

I install SQL Server 2005 Dev to my computer, when I try to run the Profiler,
I got the error message:
"The application failed to initialize properly (0xc0000005). Click on OK to
terminate the application."
How can I fix it so that I could run the Profiler on my machine?
Thanks in advance.
QHi
Error 0xc0000005 is usually an access violation. Does this occur for other
users? Can you run profiler on other machines?
John
"Q" wrote:
> I install SQL Server 2005 Dev to my computer, when I try to run the Profiler,
> I got the error message:
> "The application failed to initialize properly (0xc0000005). Click on OK to
> terminate the application."
> How can I fix it so that I could run the Profiler on my machine?
> Thanks in advance.
> Q

Error when running Profiler

I install SQL Server 2005 Dev to my computer, when I try to run the Profiler,
I got the error message:
"The application failed to initialize properly (0xc0000005). Click on OK to
terminate the application."
How can I fix it so that I could run the Profiler on my machine?
Thanks in advance.
Q
Hi
Error 0xc0000005 is usually an access violation. Does this occur for other
users? Can you run profiler on other machines?
John
"Q" wrote:

> I install SQL Server 2005 Dev to my computer, when I try to run the Profiler,
> I got the error message:
> "The application failed to initialize properly (0xc0000005). Click on OK to
> terminate the application."
> How can I fix it so that I could run the Profiler on my machine?
> Thanks in advance.
> Q

Error when running Profiler

I install SQL Server 2005 Dev to my computer, when I try to run the Profiler
,
I got the error message:
"The application failed to initialize properly (0xc0000005). Click on OK to
terminate the application."
How can I fix it so that I could run the Profiler on my machine?
Thanks in advance.
QHi
Error 0xc0000005 is usually an access violation. Does this occur for other
users? Can you run profiler on other machines?
John
"Q" wrote:

> I install SQL Server 2005 Dev to my computer, when I try to run the Profil
er,
> I got the error message:
> "The application failed to initialize properly (0xc0000005). Click on OK t
o
> terminate the application."
> How can I fix it so that I could run the Profiler on my machine?
> Thanks in advance.
> Qsql

Error to open SQL Profiler

I only Microsoft Clients Tools are installed in this Computer. Try to open
Profiler and Query Analyzer in Windows XP PRO SP2.
I get the following message:
"Program Files\Microsoft Sql Server\80\Tools\Binn\Profiler.exe is not a
valid Win32 application."
"Program Files\Microsoft Sql Server\80\Tools\Binn\isqlw.exe is not a valid
Win32 application."
How do I troubleshoot resolve this issue?
Thanks
Carlos Andrés Lozano G.
Solution Development
Try to reinstall Sql Server Client Tools.
Cristian Lefter, SQL Server MVP
"c@.rlos" <crlos@.discussions.microsoft.com> wrote in message
news:6266E3EB-6128-4E92-B640-E758ED1FB770@.microsoft.com...
>I only Microsoft Clients Tools are installed in this Computer. Try to open
> Profiler and Query Analyzer in Windows XP PRO SP2.
> I get the following message:
> "Program Files\Microsoft Sql Server\80\Tools\Binn\Profiler.exe is not a
> valid Win32 application."
> "Program Files\Microsoft Sql Server\80\Tools\Binn\isqlw.exe is not a valid
> Win32 application."
> How do I troubleshoot resolve this issue?
> --
> Thanks
> Carlos Andrs Lozano G.
> Solution Development
|||I have installed in 3 occasions and the same error leaves.
Will be able to be the computer?
"Cristian Lefter" wrote:

> Try to reinstall Sql Server Client Tools.
> Cristian Lefter, SQL Server MVP
|||c@.rlos wrote:[vbcol=seagreen]
> I have installed in 3 occasions and the same error leaves.
> Will be able to be the computer?
> "Cristian Lefter" wrote:
Try uninstalling the client tools, reinstalling from the SQL Server CD,
and then applying either the SP3a or SP4 (if you're already using SP4)
to the client. Make sure you install using an admin account.
Barring that option, you may have some unrelated corruption on the PC.
You could try reinstalling MDAC from http://www.microsoft.com/data.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||The installers are found in a unit shared of the Servant. We have done the
installation in a Windows 2000 and functions without problems
"David Gugick" escribió:

> Try uninstalling the client tools, reinstalling from the SQL Server CD,
> and then applying either the SP3a or SP4 (if you're already using SP4)
> to the client. Make sure you install using an admin account.
> Barring that option, you may have some unrelated corruption on the PC.
> You could try reinstalling MDAC from http://www.microsoft.com/data.
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
|||isqlw is not a valid Win32 application
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
|||Are you sure?
"Durga Prasad Datta" wrote:

> isqlw is not a valid Win32 application
> ************************************************** ********************
> Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
> Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
|||Durga Prasad Datta wrote:
> isqlw is not a valid Win32 application
>
It's a valid Windows EXE as far as I know. If you open up the EXE you
can see the ubiquitous "The program cannot be run in DOS mode" message
in the EXE header.
David Gugick
Quest Software
www.imceda.com
www.quest.com