I try to connect to a LDAP server from SQL query analyzer with the following string
(SELECT * FROM OPENQUERY
(ADSI,'SELECT * FROM ''LDAP://DC=test-02,DC=test,CD=no'' '))
This resulted in a error meesage:
Server: Msg 7321, Level 16, State 2, Line 1
An error occurred while preparing a query for execution against OLE DB provider 'ADSDSOObject'.
OLE DB error trace [Non-interface error: OLE DB provider ADSDSOObject returned DBPROP_STRUCTUREDSTORAGE without DBPROPVAL_OO_BLOB being supported].
OLE DB error trace [OLE/DB Provider 'ADSDSOObject' ICommandPrepare::Prepare returned 0x80040e14].
What is the problem ? It is something wrong with my db-setup, the query or what ? I try to do the same thing in a VB-program and that worked fine.Did you setup the linked server?
exec sp_addlinkedserver 'ADSI', 'Active Directory Service Interfaces', 'ADSDSOObject', 'adsdatasource'
instead of select * try and name them to see if you can at least return something
SELECT [Name],SN[Last Name]
FROM OPENQUERY( ADSI,
'SELECT Name,SN FROM ''LDAP://DC=test-02,DC=test,CD=no'' ')
also, if objects are in containers you can specify the container name by CN= or if in OU's - OU=
if you are only wanting users you can specify
WHERE objectCategory = ''Person'' AND objectClass = ''user''
HTHsql
Showing posts with label analyzer. Show all posts
Showing posts with label analyzer. Show all posts
Friday, March 30, 2012
Monday, March 26, 2012
Query
Hi
I am trying to execute the below query in Query analyzer, the same query is executed in Sybase with the corresponding columns.
select (a.OnlineAccessId) + CASE
WHEN (a.onlineaccessid2) <> '00000000000000' THEN (a.onlineaccessid2)
else ''
End + CASE
WHEN (a.onlineaccessid3) <> '00000000000000' THEN (a.onlineaccessid3)
else ''
End as onlineaccessids, a.id as AcctInfoId, BankNo, RegionNo, OfficeNo, AcctNo,AcctShortNm ,SecLending, q.id as UsersId
from AcctInfo AS a INNER JOIN "104030" AS p ON a.AdminOfficer = p.CrmCode
inner join Users as q ON p.CrmDesc = q.OnlineaccessId union select
OnlineAccessIds = (a.OnlineAccessId) + CASE
WHEN (a.onlineaccessid2) <> '00000000000000' THEN (a.onlineaccessid2)
else ''
End + CASE
WHEN (a.onlineaccessid3) <> '00000000000000' THEN (a.onlineaccessid3)
else ''
End,q.id, a.Id, BankNo, RegionNo,
OfficeNo, AcctNo,AcctShortNm, SecLending
from AcctInfo as a
inner join users as q on
(q.onlineaccessid = substring(onlineaccessids, 1, 3))
The error message is
Server: Msg 207, Level 16, State 3, Line 1
Invalid column name 'onlineaccessids'..
It is able to recognize the field "onlineaccessids" and giving me the results in Sybase database and giving the error in SQL Server.
Try to help me out.
Thanx in advanceFirst, double check that both the AcctInfo and users tables have an attribute "onlineaccessids".
Secondly, add an alias to:
(q.onlineaccessid = substring(a/q.onlineaccessids, 1, 3))
I am trying to execute the below query in Query analyzer, the same query is executed in Sybase with the corresponding columns.
select (a.OnlineAccessId) + CASE
WHEN (a.onlineaccessid2) <> '00000000000000' THEN (a.onlineaccessid2)
else ''
End + CASE
WHEN (a.onlineaccessid3) <> '00000000000000' THEN (a.onlineaccessid3)
else ''
End as onlineaccessids, a.id as AcctInfoId, BankNo, RegionNo, OfficeNo, AcctNo,AcctShortNm ,SecLending, q.id as UsersId
from AcctInfo AS a INNER JOIN "104030" AS p ON a.AdminOfficer = p.CrmCode
inner join Users as q ON p.CrmDesc = q.OnlineaccessId union select
OnlineAccessIds = (a.OnlineAccessId) + CASE
WHEN (a.onlineaccessid2) <> '00000000000000' THEN (a.onlineaccessid2)
else ''
End + CASE
WHEN (a.onlineaccessid3) <> '00000000000000' THEN (a.onlineaccessid3)
else ''
End,q.id, a.Id, BankNo, RegionNo,
OfficeNo, AcctNo,AcctShortNm, SecLending
from AcctInfo as a
inner join users as q on
(q.onlineaccessid = substring(onlineaccessids, 1, 3))
The error message is
Server: Msg 207, Level 16, State 3, Line 1
Invalid column name 'onlineaccessids'..
It is able to recognize the field "onlineaccessids" and giving me the results in Sybase database and giving the error in SQL Server.
Try to help me out.
Thanx in advanceFirst, double check that both the AcctInfo and users tables have an attribute "onlineaccessids".
Secondly, add an alias to:
(q.onlineaccessid = substring(a/q.onlineaccessids, 1, 3))
Monday, March 12, 2012
Qry Analyzer: Processor utilization
I have noticed that when using SQL Query Analyzer some of my queries will use 100% CPU on my PC and next to nothing on the SQL server, while other Queries require 100% CPU on SQL server and do next to nothing on my PC. Does anyone know what determines this??
Right now I can produce this by executing two very similar T-SQL selects. The one that runs on the server only has one additional join - a very simply join at that. If I can change my SQL to make it run client side in some situations, that would be VERY HELPFUL!
Thanks in advance!
RyanWhat are you referring to when saying that the query takes 100% on your machine? Are you comparing the performance of MSDE running on your machine with SQL Server engine running on the server?|||No, MSDE is not involved. If I run a query with one join through SQL Query Analyzer on my PC, and against my production 7.0 sql server, it will use 100% of my PC's processor. If I execute a query with two inner joins in it, still from query analyzer and against the same SQL box, the query uses 100% of the server's processor and does not use the client PC processor.
I guess this would probably be occurring based on some decision made by the SQL optimizer, but I am trying to find out if anyone is familiar enough with such a situation that they know tricks to writing queries so that processing occurs on the client side.
I have some users that require atypical adhoc query support. When possible, I would like to write queries for them in such a way that I can place most of the processor requirements on the client PC.
Thanks
Ryan|||I don't think it's possible. ALL processing is done on the server. Unless you're talking about firing queries through MS Access that "claims" to be able to do data processing itself. But even then, whatever statement ends up going to the server from the Jet, - gets processed entirely by the SQL engine, the client just reads the results either from the named pipe file, or from TCP/IP packets (virtual file.)
Right now I can produce this by executing two very similar T-SQL selects. The one that runs on the server only has one additional join - a very simply join at that. If I can change my SQL to make it run client side in some situations, that would be VERY HELPFUL!
Thanks in advance!
RyanWhat are you referring to when saying that the query takes 100% on your machine? Are you comparing the performance of MSDE running on your machine with SQL Server engine running on the server?|||No, MSDE is not involved. If I run a query with one join through SQL Query Analyzer on my PC, and against my production 7.0 sql server, it will use 100% of my PC's processor. If I execute a query with two inner joins in it, still from query analyzer and against the same SQL box, the query uses 100% of the server's processor and does not use the client PC processor.
I guess this would probably be occurring based on some decision made by the SQL optimizer, but I am trying to find out if anyone is familiar enough with such a situation that they know tricks to writing queries so that processing occurs on the client side.
I have some users that require atypical adhoc query support. When possible, I would like to write queries for them in such a way that I can place most of the processor requirements on the client PC.
Thanks
Ryan|||I don't think it's possible. ALL processing is done on the server. Unless you're talking about firing queries through MS Access that "claims" to be able to do data processing itself. But even then, whatever statement ends up going to the server from the Jet, - gets processed entirely by the SQL engine, the client just reads the results either from the named pipe file, or from TCP/IP packets (virtual file.)
Qry Analyzer Debug broken: XP SP2
I read a post in this group that a hotfix (per KB839280) would take care of
this (posted by an MS support person). The post indicated this fix would take
care of the Visual Studio issue, and well as Query Analyzer.
I got the hotfix and installed it on my development server, however my XP
sp2 system still cannot remotely debug the server. I have always been able to
do this, until I installed XP sp2.
Any suggestions? Has anyone gotten remote debugging to work post XP sp2
installation?
Thanks for your assistance,
TomHi Tom,
Thanks for your posting!
From your descriptions, I understood that you could not use Query Analyzer
to debug after XP SP2 was upgraded. Have I understood you? If there is
anything I misunderstood, please feel free to let me know.
Based on my scope, as you said it is a remotely debugging ,does it used a
linked server? If so, here is another document address the probelm you may
meet.
You may receive a 7391 error message in SQL Server 2000 when you run a
distributed transaction against a linked server after you install Microsoft
Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=839279
What's the error message when it fails to debugging? Could you tell me how
to reporduce it on my machine? I need more detailed information for your
scenario, which, I believe, will make us closer to the resolution.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I am trying to debug a sql server, from a WinXP sp2 system. I was able to do
this prior to installing XP sp2 on the WinXP system. The sql server is at
sp3, and runs on a Windows 2003 system.
The message I get when running the debugger is:
Server: Msg 508, Level 16, State 1, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
on HESPERUS (Error = 0x800706ba). Ensure that client-side components, such as
SQLLE.DLL, are installed and registered on TOMHOME2. Debugging disabled for
connection 58.
""Mingqing Cheng [MSFT]"" wrote:
> Hi Tom,
> Thanks for your posting!
> From your descriptions, I understood that you could not use Query Analyzer
> to debug after XP SP2 was upgraded. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Based on my scope, as you said it is a remotely debugging ,does it used a
> linked server? If so, here is another document address the probelm you may
> meet.
> You may receive a 7391 error message in SQL Server 2000 when you run a
> distributed transaction against a linked server after you install Microsoft
> Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=839279
> What's the error message when it fails to debugging? Could you tell me how
> to reporduce it on my machine? I need more detailed information for your
> scenario, which, I believe, will make us closer to the resolution.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||This is the error in the event log of the SQL Server system:
Event Type: Error
Event Source: SQLDebugging98
Event Category: None
Event ID: 1
Date: 9/14/2004
Time: 9:45:19 PM
User: N/A
Computer: HESPERUS
Description:
SQL Server is running as 'Force3\SQLAdmin' and cannot connect to the
debugger on machine 'TOMHOME2' (error = 0x80070005 Access is denied. ). Use
one of the following options to fix this error. 1) Run SQL Server as "Local
System", as a domain account, or as a local account with identical usernames
and passwords on both machine 'HESPERUS' and 'TOMHOME2'. 2) Verify that
machine 'HESPERUS' can open files on machine 'TOMHOME2'. Debugging disabled
for connection 56.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
This setup did work prior to XP sp2, the logon account for the sql server
service is a domain (admin) account.
The odd thing now is, when I run the debugger, it actually runs, but does
not "step" thru the procedure, it goes straight thru to the end, and does not
show any of the values for the variables, connections, etc. In the results
pane, I get a result, and at the very bottom it says completed.
Putting in break points makes no difference, it just runs on to the end
regardless...
""Mingqing Cheng [MSFT]"" wrote:
> Hi Tom,
> Thanks for your posting!
> From your descriptions, I understood that you could not use Query Analyzer
> to debug after XP SP2 was upgraded. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Based on my scope, as you said it is a remotely debugging ,does it used a
> linked server? If so, here is another document address the probelm you may
> meet.
> You may receive a 7391 error message in SQL Server 2000 when you run a
> distributed transaction against a linked server after you install Microsoft
> Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=839279
> What's the error message when it fails to debugging? Could you tell me how
> to reporduce it on my machine? I need more detailed information for your
> scenario, which, I believe, will make us closer to the resolution.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi Tom,
Thanks for your detailed information and descriptions!
First of all, The reason for Error 508 and Error code 0x80070005 is
permission issue. As you said it works fine before upgrading to XP SP2,
have you tried disable the Firewall os XP SP2. Close the firewall and then
tell me whether it works. Checking the following documents to make sure
your SQL Server in XP XP2 is correctly configured
How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
http://support.microsoft.com/?id=841249
Secondly, The error 0x800706ba generated is a Distributed COM communication
error when using RPC. The error code 0x800706ba translates to "RPC server
unavailable". DCOM uses Remote Procedure Call (RPC) dynamic port
allocation. By default, RPC dynamic port allocation randomly selects port
numbers above 1024, so the problem seems to be the firewall blocking the
rpc communication. Do the folloing things to make sure DCOM is running
fine.
* On the client machine
--run dcomcnfg.
--Go to the dcom config properties under default properties, there is a
check box stating "enable Distributed COM on this computer", if this was
unchecked on the client machine, this is a default setting that is checked.
make sure it is checked.
*Then copied the new sqldbg.dll and sqldbreg.exe from the SQL Server CD,
replcaed the old ones with these on the client machine and then ran the
regsvr32 sqldbg.dll for re-resgistering the dll and sqldbreg.exe
/RegServer on the client machine and rebooted the box and everything
started to work like a charm.Customer was able to debug the stored proc on
the server using SQL QA and t-sql debugger from his client machine.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I found the problem: after applying the hotfix to the server, the client side
tools were no longer the same version as the server. Applying the hotfix to
the client fixed the problem.
""Mingqing Cheng [MSFT]"" wrote:
> Hi Tom,
> Thanks for your detailed information and descriptions!
> First of all, The reason for Error 508 and Error code 0x80070005 is
> permission issue. As you said it works fine before upgrading to XP SP2,
> have you tried disable the Firewall os XP SP2. Close the firewall and then
> tell me whether it works. Checking the following documents to make sure
> your SQL Server in XP XP2 is correctly configured
> How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
> http://support.microsoft.com/?id=841249
> Secondly, The error 0x800706ba generated is a Distributed COM communication
> error when using RPC. The error code 0x800706ba translates to "RPC server
> unavailable". DCOM uses Remote Procedure Call (RPC) dynamic port
> allocation. By default, RPC dynamic port allocation randomly selects port
> numbers above 1024, so the problem seems to be the firewall blocking the
> rpc communication. Do the folloing things to make sure DCOM is running
> fine.
> * On the client machine
> --run dcomcnfg.
> --Go to the dcom config properties under default properties, there is a
> check box stating "enable Distributed COM on this computer", if this was
> unchecked on the client machine, this is a default setting that is checked.
> make sure it is checked.
> *Then copied the new sqldbg.dll and sqldbreg.exe from the SQL Server CD,
> replcaed the old ones with these on the client machine and then ran the
> regsvr32 sqldbg.dll for re-resgistering the dll and sqldbreg.exe
> /RegServer on the client machine and rebooted the box and everything
> started to work like a charm.Customer was able to debug the stored proc on
> the server using SQL QA and t-sql debugger from his client machine.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||I also have the same problem after installed Windows XP SP2,
the similar error message when running debugger from query analyzer.
Is there any solution for this?
"TomT" <tomt@.tomt.com> wrote in message news:<93363379-8AFA-45EA-BE8D-F53FCB3835FE@.microsoft.com>...
> I am trying to debug a sql server, from a WinXP sp2 system. I was able to do
> this prior to installing XP sp2 on the WinXP system. The sql server is at
> sp3, and runs on a Windows 2003 system.
> The message I get when running the debugger is:
> Server: Msg 508, Level 16, State 1, Procedure sp_sdidebug, Line 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
> on HESPERUS (Error = 0x800706ba). Ensure that client-side components, such as
> SQLLE.DLL, are installed and registered on TOMHOME2. Debugging disabled for
> connection 58.
> ""Mingqing Cheng [MSFT]"" wrote:
> > Hi Tom,
> >
> > Thanks for your posting!
> >
> > From your descriptions, I understood that you could not use Query Analyzer
> > to debug after XP SP2 was upgraded. Have I understood you? If there is
> > anything I misunderstood, please feel free to let me know.
> >
> > Based on my scope, as you said it is a remotely debugging ,does it used a
> > linked server? If so, here is another document address the probelm you may
> > meet.
> >
> > You may receive a 7391 error message in SQL Server 2000 when you run a
> > distributed transaction against a linked server after you install Microsoft
> > Windows XP Service Pack 2
> > http://support.microsoft.com/default.aspx?kbid=839279
> >
> > What's the error message when it fails to debugging? Could you tell me how
> > to reporduce it on my machine? I need more detailed information for your
> > scenario, which, I believe, will make us closer to the resolution.
> >
> > Thank you for your patience and cooperation. If you have any questions or
> > concerns, don't hesitate to let me know. We are here to be of assistance!
> >
> >
> > Sincerely yours,
> >
> > Mingqing Cheng
> >
> > Online Partner Support Specialist
> > Partner Support Group
> > Microsoft Global Technical Support Center
> > ---
> > Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> > This posting is provided "as is" with no warranties and confers no rights.
> > Please reply to newsgroups only, many thanks!
> >
> >|||Check my last entry on this topic, dated 9/16/2004
"duandd" wrote:
> I also have the same problem after installed Windows XP SP2,
> the similar error message when running debugger from query analyzer.
> Is there any solution for this?
> "TomT" <tomt@.tomt.com> wrote in message news:<93363379-8AFA-45EA-BE8D-F53FCB3835FE@.microsoft.com>...
> > I am trying to debug a sql server, from a WinXP sp2 system. I was able to do
> > this prior to installing XP sp2 on the WinXP system. The sql server is at
> > sp3, and runs on a Windows 2003 system.
> >
> > The message I get when running the debugger is:
> >
> > Server: Msg 508, Level 16, State 1, Procedure sp_sdidebug, Line 1
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
> > on HESPERUS (Error = 0x800706ba). Ensure that client-side components, such as
> > SQLLE.DLL, are installed and registered on TOMHOME2. Debugging disabled for
> > connection 58.
> >
> > ""Mingqing Cheng [MSFT]"" wrote:
> >
> > > Hi Tom,
> > >
> > > Thanks for your posting!
> > >
> > > From your descriptions, I understood that you could not use Query Analyzer
> > > to debug after XP SP2 was upgraded. Have I understood you? If there is
> > > anything I misunderstood, please feel free to let me know.
> > >
> > > Based on my scope, as you said it is a remotely debugging ,does it used a
> > > linked server? If so, here is another document address the probelm you may
> > > meet.
> > >
> > > You may receive a 7391 error message in SQL Server 2000 when you run a
> > > distributed transaction against a linked server after you install Microsoft
> > > Windows XP Service Pack 2
> > > http://support.microsoft.com/default.aspx?kbid=839279
> > >
> > > What's the error message when it fails to debugging? Could you tell me how
> > > to reporduce it on my machine? I need more detailed information for your
> > > scenario, which, I believe, will make us closer to the resolution.
> > >
> > > Thank you for your patience and cooperation. If you have any questions or
> > > concerns, don't hesitate to let me know. We are here to be of assistance!
> > >
> > >
> > > Sincerely yours,
> > >
> > > Mingqing Cheng
> > >
> > > Online Partner Support Specialist
> > > Partner Support Group
> > > Microsoft Global Technical Support Center
> > > ---
> > > Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> > > This posting is provided "as is" with no warranties and confers no rights.
> > > Please reply to newsgroups only, many thanks!
> > >
> > >
>
this (posted by an MS support person). The post indicated this fix would take
care of the Visual Studio issue, and well as Query Analyzer.
I got the hotfix and installed it on my development server, however my XP
sp2 system still cannot remotely debug the server. I have always been able to
do this, until I installed XP sp2.
Any suggestions? Has anyone gotten remote debugging to work post XP sp2
installation?
Thanks for your assistance,
TomHi Tom,
Thanks for your posting!
From your descriptions, I understood that you could not use Query Analyzer
to debug after XP SP2 was upgraded. Have I understood you? If there is
anything I misunderstood, please feel free to let me know.
Based on my scope, as you said it is a remotely debugging ,does it used a
linked server? If so, here is another document address the probelm you may
meet.
You may receive a 7391 error message in SQL Server 2000 when you run a
distributed transaction against a linked server after you install Microsoft
Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=839279
What's the error message when it fails to debugging? Could you tell me how
to reporduce it on my machine? I need more detailed information for your
scenario, which, I believe, will make us closer to the resolution.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I am trying to debug a sql server, from a WinXP sp2 system. I was able to do
this prior to installing XP sp2 on the WinXP system. The sql server is at
sp3, and runs on a Windows 2003 system.
The message I get when running the debugger is:
Server: Msg 508, Level 16, State 1, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
on HESPERUS (Error = 0x800706ba). Ensure that client-side components, such as
SQLLE.DLL, are installed and registered on TOMHOME2. Debugging disabled for
connection 58.
""Mingqing Cheng [MSFT]"" wrote:
> Hi Tom,
> Thanks for your posting!
> From your descriptions, I understood that you could not use Query Analyzer
> to debug after XP SP2 was upgraded. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Based on my scope, as you said it is a remotely debugging ,does it used a
> linked server? If so, here is another document address the probelm you may
> meet.
> You may receive a 7391 error message in SQL Server 2000 when you run a
> distributed transaction against a linked server after you install Microsoft
> Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=839279
> What's the error message when it fails to debugging? Could you tell me how
> to reporduce it on my machine? I need more detailed information for your
> scenario, which, I believe, will make us closer to the resolution.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||This is the error in the event log of the SQL Server system:
Event Type: Error
Event Source: SQLDebugging98
Event Category: None
Event ID: 1
Date: 9/14/2004
Time: 9:45:19 PM
User: N/A
Computer: HESPERUS
Description:
SQL Server is running as 'Force3\SQLAdmin' and cannot connect to the
debugger on machine 'TOMHOME2' (error = 0x80070005 Access is denied. ). Use
one of the following options to fix this error. 1) Run SQL Server as "Local
System", as a domain account, or as a local account with identical usernames
and passwords on both machine 'HESPERUS' and 'TOMHOME2'. 2) Verify that
machine 'HESPERUS' can open files on machine 'TOMHOME2'. Debugging disabled
for connection 56.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
This setup did work prior to XP sp2, the logon account for the sql server
service is a domain (admin) account.
The odd thing now is, when I run the debugger, it actually runs, but does
not "step" thru the procedure, it goes straight thru to the end, and does not
show any of the values for the variables, connections, etc. In the results
pane, I get a result, and at the very bottom it says completed.
Putting in break points makes no difference, it just runs on to the end
regardless...
""Mingqing Cheng [MSFT]"" wrote:
> Hi Tom,
> Thanks for your posting!
> From your descriptions, I understood that you could not use Query Analyzer
> to debug after XP SP2 was upgraded. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Based on my scope, as you said it is a remotely debugging ,does it used a
> linked server? If so, here is another document address the probelm you may
> meet.
> You may receive a 7391 error message in SQL Server 2000 when you run a
> distributed transaction against a linked server after you install Microsoft
> Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=839279
> What's the error message when it fails to debugging? Could you tell me how
> to reporduce it on my machine? I need more detailed information for your
> scenario, which, I believe, will make us closer to the resolution.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi Tom,
Thanks for your detailed information and descriptions!
First of all, The reason for Error 508 and Error code 0x80070005 is
permission issue. As you said it works fine before upgrading to XP SP2,
have you tried disable the Firewall os XP SP2. Close the firewall and then
tell me whether it works. Checking the following documents to make sure
your SQL Server in XP XP2 is correctly configured
How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
http://support.microsoft.com/?id=841249
Secondly, The error 0x800706ba generated is a Distributed COM communication
error when using RPC. The error code 0x800706ba translates to "RPC server
unavailable". DCOM uses Remote Procedure Call (RPC) dynamic port
allocation. By default, RPC dynamic port allocation randomly selects port
numbers above 1024, so the problem seems to be the firewall blocking the
rpc communication. Do the folloing things to make sure DCOM is running
fine.
* On the client machine
--run dcomcnfg.
--Go to the dcom config properties under default properties, there is a
check box stating "enable Distributed COM on this computer", if this was
unchecked on the client machine, this is a default setting that is checked.
make sure it is checked.
*Then copied the new sqldbg.dll and sqldbreg.exe from the SQL Server CD,
replcaed the old ones with these on the client machine and then ran the
regsvr32 sqldbg.dll for re-resgistering the dll and sqldbreg.exe
/RegServer on the client machine and rebooted the box and everything
started to work like a charm.Customer was able to debug the stored proc on
the server using SQL QA and t-sql debugger from his client machine.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I found the problem: after applying the hotfix to the server, the client side
tools were no longer the same version as the server. Applying the hotfix to
the client fixed the problem.
""Mingqing Cheng [MSFT]"" wrote:
> Hi Tom,
> Thanks for your detailed information and descriptions!
> First of all, The reason for Error 508 and Error code 0x80070005 is
> permission issue. As you said it works fine before upgrading to XP SP2,
> have you tried disable the Firewall os XP SP2. Close the firewall and then
> tell me whether it works. Checking the following documents to make sure
> your SQL Server in XP XP2 is correctly configured
> How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
> http://support.microsoft.com/?id=841249
> Secondly, The error 0x800706ba generated is a Distributed COM communication
> error when using RPC. The error code 0x800706ba translates to "RPC server
> unavailable". DCOM uses Remote Procedure Call (RPC) dynamic port
> allocation. By default, RPC dynamic port allocation randomly selects port
> numbers above 1024, so the problem seems to be the firewall blocking the
> rpc communication. Do the folloing things to make sure DCOM is running
> fine.
> * On the client machine
> --run dcomcnfg.
> --Go to the dcom config properties under default properties, there is a
> check box stating "enable Distributed COM on this computer", if this was
> unchecked on the client machine, this is a default setting that is checked.
> make sure it is checked.
> *Then copied the new sqldbg.dll and sqldbreg.exe from the SQL Server CD,
> replcaed the old ones with these on the client machine and then ran the
> regsvr32 sqldbg.dll for re-resgistering the dll and sqldbreg.exe
> /RegServer on the client machine and rebooted the box and everything
> started to work like a charm.Customer was able to debug the stored proc on
> the server using SQL QA and t-sql debugger from his client machine.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||I also have the same problem after installed Windows XP SP2,
the similar error message when running debugger from query analyzer.
Is there any solution for this?
"TomT" <tomt@.tomt.com> wrote in message news:<93363379-8AFA-45EA-BE8D-F53FCB3835FE@.microsoft.com>...
> I am trying to debug a sql server, from a WinXP sp2 system. I was able to do
> this prior to installing XP sp2 on the WinXP system. The sql server is at
> sp3, and runs on a Windows 2003 system.
> The message I get when running the debugger is:
> Server: Msg 508, Level 16, State 1, Procedure sp_sdidebug, Line 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
> on HESPERUS (Error = 0x800706ba). Ensure that client-side components, such as
> SQLLE.DLL, are installed and registered on TOMHOME2. Debugging disabled for
> connection 58.
> ""Mingqing Cheng [MSFT]"" wrote:
> > Hi Tom,
> >
> > Thanks for your posting!
> >
> > From your descriptions, I understood that you could not use Query Analyzer
> > to debug after XP SP2 was upgraded. Have I understood you? If there is
> > anything I misunderstood, please feel free to let me know.
> >
> > Based on my scope, as you said it is a remotely debugging ,does it used a
> > linked server? If so, here is another document address the probelm you may
> > meet.
> >
> > You may receive a 7391 error message in SQL Server 2000 when you run a
> > distributed transaction against a linked server after you install Microsoft
> > Windows XP Service Pack 2
> > http://support.microsoft.com/default.aspx?kbid=839279
> >
> > What's the error message when it fails to debugging? Could you tell me how
> > to reporduce it on my machine? I need more detailed information for your
> > scenario, which, I believe, will make us closer to the resolution.
> >
> > Thank you for your patience and cooperation. If you have any questions or
> > concerns, don't hesitate to let me know. We are here to be of assistance!
> >
> >
> > Sincerely yours,
> >
> > Mingqing Cheng
> >
> > Online Partner Support Specialist
> > Partner Support Group
> > Microsoft Global Technical Support Center
> > ---
> > Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> > This posting is provided "as is" with no warranties and confers no rights.
> > Please reply to newsgroups only, many thanks!
> >
> >|||Check my last entry on this topic, dated 9/16/2004
"duandd" wrote:
> I also have the same problem after installed Windows XP SP2,
> the similar error message when running debugger from query analyzer.
> Is there any solution for this?
> "TomT" <tomt@.tomt.com> wrote in message news:<93363379-8AFA-45EA-BE8D-F53FCB3835FE@.microsoft.com>...
> > I am trying to debug a sql server, from a WinXP sp2 system. I was able to do
> > this prior to installing XP sp2 on the WinXP system. The sql server is at
> > sp3, and runs on a Windows 2003 system.
> >
> > The message I get when running the debugger is:
> >
> > Server: Msg 508, Level 16, State 1, Procedure sp_sdidebug, Line 1
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
> > on HESPERUS (Error = 0x800706ba). Ensure that client-side components, such as
> > SQLLE.DLL, are installed and registered on TOMHOME2. Debugging disabled for
> > connection 58.
> >
> > ""Mingqing Cheng [MSFT]"" wrote:
> >
> > > Hi Tom,
> > >
> > > Thanks for your posting!
> > >
> > > From your descriptions, I understood that you could not use Query Analyzer
> > > to debug after XP SP2 was upgraded. Have I understood you? If there is
> > > anything I misunderstood, please feel free to let me know.
> > >
> > > Based on my scope, as you said it is a remotely debugging ,does it used a
> > > linked server? If so, here is another document address the probelm you may
> > > meet.
> > >
> > > You may receive a 7391 error message in SQL Server 2000 when you run a
> > > distributed transaction against a linked server after you install Microsoft
> > > Windows XP Service Pack 2
> > > http://support.microsoft.com/default.aspx?kbid=839279
> > >
> > > What's the error message when it fails to debugging? Could you tell me how
> > > to reporduce it on my machine? I need more detailed information for your
> > > scenario, which, I believe, will make us closer to the resolution.
> > >
> > > Thank you for your patience and cooperation. If you have any questions or
> > > concerns, don't hesitate to let me know. We are here to be of assistance!
> > >
> > >
> > > Sincerely yours,
> > >
> > > Mingqing Cheng
> > >
> > > Online Partner Support Specialist
> > > Partner Support Group
> > > Microsoft Global Technical Support Center
> > > ---
> > > Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> > > This posting is provided "as is" with no warranties and confers no rights.
> > > Please reply to newsgroups only, many thanks!
> > >
> > >
>
Qry Analyzer Debug broken: XP SP2
I read a post in this group that a hotfix (per KB839280) would take care of
this (posted by an MS support person). The post indicated this fix would take
care of the Visual Studio issue, and well as Query Analyzer.
I got the hotfix and installed it on my development server, however my XP
sp2 system still cannot remotely debug the server. I have always been able to
do this, until I installed XP sp2.
Any suggestions? Has anyone gotten remote debugging to work post XP sp2
installation?
Thanks for your assistance,
Tom
Hi Tom,
Thanks for your posting!
From your descriptions, I understood that you could not use Query Analyzer
to debug after XP SP2 was upgraded. Have I understood you? If there is
anything I misunderstood, please feel free to let me know.
Based on my scope, as you said it is a remotely debugging ,does it used a
linked server? If so, here is another document address the probelm you may
meet.
You may receive a 7391 error message in SQL Server 2000 when you run a
distributed transaction against a linked server after you install Microsoft
Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=839279
What's the error message when it fails to debugging? Could you tell me how
to reporduce it on my machine? I need more detailed information for your
scenario, which, I believe, will make us closer to the resolution.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||I am trying to debug a sql server, from a WinXP sp2 system. I was able to do
this prior to installing XP sp2 on the WinXP system. The sql server is at
sp3, and runs on a Windows 2003 system.
The message I get when running the debugger is:
Server: Msg 508, Level 16, State 1, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
on HESPERUS (Error = 0x800706ba). Ensure that client-side components, such as
SQLLE.DLL, are installed and registered on TOMHOME2. Debugging disabled for
connection 58.
""Mingqing Cheng [MSFT]"" wrote:
> Hi Tom,
> Thanks for your posting!
> From your descriptions, I understood that you could not use Query Analyzer
> to debug after XP SP2 was upgraded. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Based on my scope, as you said it is a remotely debugging ,does it used a
> linked server? If so, here is another document address the probelm you may
> meet.
> You may receive a 7391 error message in SQL Server 2000 when you run a
> distributed transaction against a linked server after you install Microsoft
> Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=839279
> What's the error message when it fails to debugging? Could you tell me how
> to reporduce it on my machine? I need more detailed information for your
> scenario, which, I believe, will make us closer to the resolution.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||This is the error in the event log of the SQL Server system:
Event Type:Error
Event Source:SQLDebugging98
Event Category:None
Event ID:1
Date:9/14/2004
Time:9:45:19 PM
User:N/A
Computer:HESPERUS
Description:
SQL Server is running as 'Force3\SQLAdmin' and cannot connect to the
debugger on machine 'TOMHOME2' (error = 0x80070005 Access is denied. ). Use
one of the following options to fix this error. 1) Run SQL Server as "Local
System", as a domain account, or as a local account with identical usernames
and passwords on both machine 'HESPERUS' and 'TOMHOME2'. 2) Verify that
machine 'HESPERUS' can open files on machine 'TOMHOME2'. Debugging disabled
for connection 56.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
This setup did work prior to XP sp2, the logon account for the sql server
service is a domain (admin) account.
The odd thing now is, when I run the debugger, it actually runs, but does
not "step" thru the procedure, it goes straight thru to the end, and does not
show any of the values for the variables, connections, etc. In the results
pane, I get a result, and at the very bottom it says completed.
Putting in break points makes no difference, it just runs on to the end
regardless...
""Mingqing Cheng [MSFT]"" wrote:
> Hi Tom,
> Thanks for your posting!
> From your descriptions, I understood that you could not use Query Analyzer
> to debug after XP SP2 was upgraded. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Based on my scope, as you said it is a remotely debugging ,does it used a
> linked server? If so, here is another document address the probelm you may
> meet.
> You may receive a 7391 error message in SQL Server 2000 when you run a
> distributed transaction against a linked server after you install Microsoft
> Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=839279
> What's the error message when it fails to debugging? Could you tell me how
> to reporduce it on my machine? I need more detailed information for your
> scenario, which, I believe, will make us closer to the resolution.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||Hi Tom,
Thanks for your detailed information and descriptions!
First of all, The reason for Error 508 and Error code 0x80070005 is
permission issue. As you said it works fine before upgrading to XP SP2,
have you tried disable the Firewall os XP SP2. Close the firewall and then
tell me whether it works. Checking the following documents to make sure
your SQL Server in XP XP2 is correctly configured
How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
http://support.microsoft.com/?id=841249
Secondly, The error 0x800706ba generated is a Distributed COM communication
error when using RPC. The error code 0x800706ba translates to "RPC server
unavailable". DCOM uses Remote Procedure Call (RPC) dynamic port
allocation. By default, RPC dynamic port allocation randomly selects port
numbers above 1024, so the problem seems to be the firewall blocking the
rpc communication. Do the folloing things to make sure DCOM is running
fine.
* On the client machine
--run dcomcnfg.
--Go to the dcom config properties under default properties, there is a
check box stating "enable Distributed COM on this computer", if this was
unchecked on the client machine, this is a default setting that is checked.
make sure it is checked.
*Then copied the new sqldbg.dll and sqldbreg.exe from the SQL Server CD,
replcaed the old ones with these on the client machine and then ran the
regsvr32 sqldbg.dll for re-resgistering the dll and sqldbreg.exe
/RegServer on the client machine and rebooted the box and everything
started to work like a charm.Customer was able to debug the stored proc on
the server using SQL QA and t-sql debugger from his client machine.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||I have tried all the suggestions but the behavior remains the same: the
debugger connects and then runs thru the procedure beginning to end without
stopping, providing variable info, etc.
""Mingqing Cheng [MSFT]"" wrote:
> Hi Tom,
> Thanks for your detailed information and descriptions!
> First of all, The reason for Error 508 and Error code 0x80070005 is
> permission issue. As you said it works fine before upgrading to XP SP2,
> have you tried disable the Firewall os XP SP2. Close the firewall and then
> tell me whether it works. Checking the following documents to make sure
> your SQL Server in XP XP2 is correctly configured
> How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
> http://support.microsoft.com/?id=841249
> Secondly, The error 0x800706ba generated is a Distributed COM communication
> error when using RPC. The error code 0x800706ba translates to "RPC server
> unavailable". DCOM uses Remote Procedure Call (RPC) dynamic port
> allocation. By default, RPC dynamic port allocation randomly selects port
> numbers above 1024, so the problem seems to be the firewall blocking the
> rpc communication. Do the folloing things to make sure DCOM is running
> fine.
> * On the client machine
> --run dcomcnfg.
> --Go to the dcom config properties under default properties, there is a
> check box stating "enable Distributed COM on this computer", if this was
> unchecked on the client machine, this is a default setting that is checked.
> make sure it is checked.
> *Then copied the new sqldbg.dll and sqldbreg.exe from the SQL Server CD,
> replcaed the old ones with these on the client machine and then ran the
> regsvr32 sqldbg.dll for re-resgistering the dll and sqldbreg.exe
> /RegServer on the client machine and rebooted the box and everything
> started to work like a charm.Customer was able to debug the stored proc on
> the server using SQL QA and t-sql debugger from his client machine.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||I found the problem: after applying the hotfix to the server, the client side
tools were no longer the same version as the server. Applying the hotfix to
the client fixed the problem.
""Mingqing Cheng [MSFT]"" wrote:
> Hi Tom,
> Thanks for your detailed information and descriptions!
> First of all, The reason for Error 508 and Error code 0x80070005 is
> permission issue. As you said it works fine before upgrading to XP SP2,
> have you tried disable the Firewall os XP SP2. Close the firewall and then
> tell me whether it works. Checking the following documents to make sure
> your SQL Server in XP XP2 is correctly configured
> How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
> http://support.microsoft.com/?id=841249
> Secondly, The error 0x800706ba generated is a Distributed COM communication
> error when using RPC. The error code 0x800706ba translates to "RPC server
> unavailable". DCOM uses Remote Procedure Call (RPC) dynamic port
> allocation. By default, RPC dynamic port allocation randomly selects port
> numbers above 1024, so the problem seems to be the firewall blocking the
> rpc communication. Do the folloing things to make sure DCOM is running
> fine.
> * On the client machine
> --run dcomcnfg.
> --Go to the dcom config properties under default properties, there is a
> check box stating "enable Distributed COM on this computer", if this was
> unchecked on the client machine, this is a default setting that is checked.
> make sure it is checked.
> *Then copied the new sqldbg.dll and sqldbreg.exe from the SQL Server CD,
> replcaed the old ones with these on the client machine and then ran the
> regsvr32 sqldbg.dll for re-resgistering the dll and sqldbreg.exe
> /RegServer on the client machine and rebooted the box and everything
> started to work like a charm.Customer was able to debug the stored proc on
> the server using SQL QA and t-sql debugger from his client machine.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||I also have the same problem after installed Windows XP SP2,
the similar error message when running debugger from query analyzer.
Is there any solution for this?
"TomT" <tomt@.tomt.com> wrote in message news:<93363379-8AFA-45EA-BE8D-F53FCB3835FE@.microsoft.com>...[vbcol=seagreen]
> I am trying to debug a sql server, from a WinXP sp2 system. I was able to do
> this prior to installing XP sp2 on the WinXP system. The sql server is at
> sp3, and runs on a Windows 2003 system.
> The message I get when running the debugger is:
> Server: Msg 508, Level 16, State 1, Procedure sp_sdidebug, Line 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
> on HESPERUS (Error = 0x800706ba). Ensure that client-side components, such as
> SQLLE.DLL, are installed and registered on TOMHOME2. Debugging disabled for
> connection 58.
> ""Mingqing Cheng [MSFT]"" wrote:
|||Check my last entry on this topic, dated 9/16/2004
"duandd" wrote:
> I also have the same problem after installed Windows XP SP2,
> the similar error message when running debugger from query analyzer.
> Is there any solution for this?
> "TomT" <tomt@.tomt.com> wrote in message news:<93363379-8AFA-45EA-BE8D-F53FCB3835FE@.microsoft.com>...
>
this (posted by an MS support person). The post indicated this fix would take
care of the Visual Studio issue, and well as Query Analyzer.
I got the hotfix and installed it on my development server, however my XP
sp2 system still cannot remotely debug the server. I have always been able to
do this, until I installed XP sp2.
Any suggestions? Has anyone gotten remote debugging to work post XP sp2
installation?
Thanks for your assistance,
Tom
Hi Tom,
Thanks for your posting!
From your descriptions, I understood that you could not use Query Analyzer
to debug after XP SP2 was upgraded. Have I understood you? If there is
anything I misunderstood, please feel free to let me know.
Based on my scope, as you said it is a remotely debugging ,does it used a
linked server? If so, here is another document address the probelm you may
meet.
You may receive a 7391 error message in SQL Server 2000 when you run a
distributed transaction against a linked server after you install Microsoft
Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=839279
What's the error message when it fails to debugging? Could you tell me how
to reporduce it on my machine? I need more detailed information for your
scenario, which, I believe, will make us closer to the resolution.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||I am trying to debug a sql server, from a WinXP sp2 system. I was able to do
this prior to installing XP sp2 on the WinXP system. The sql server is at
sp3, and runs on a Windows 2003 system.
The message I get when running the debugger is:
Server: Msg 508, Level 16, State 1, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
on HESPERUS (Error = 0x800706ba). Ensure that client-side components, such as
SQLLE.DLL, are installed and registered on TOMHOME2. Debugging disabled for
connection 58.
""Mingqing Cheng [MSFT]"" wrote:
> Hi Tom,
> Thanks for your posting!
> From your descriptions, I understood that you could not use Query Analyzer
> to debug after XP SP2 was upgraded. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Based on my scope, as you said it is a remotely debugging ,does it used a
> linked server? If so, here is another document address the probelm you may
> meet.
> You may receive a 7391 error message in SQL Server 2000 when you run a
> distributed transaction against a linked server after you install Microsoft
> Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=839279
> What's the error message when it fails to debugging? Could you tell me how
> to reporduce it on my machine? I need more detailed information for your
> scenario, which, I believe, will make us closer to the resolution.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||This is the error in the event log of the SQL Server system:
Event Type:Error
Event Source:SQLDebugging98
Event Category:None
Event ID:1
Date:9/14/2004
Time:9:45:19 PM
User:N/A
Computer:HESPERUS
Description:
SQL Server is running as 'Force3\SQLAdmin' and cannot connect to the
debugger on machine 'TOMHOME2' (error = 0x80070005 Access is denied. ). Use
one of the following options to fix this error. 1) Run SQL Server as "Local
System", as a domain account, or as a local account with identical usernames
and passwords on both machine 'HESPERUS' and 'TOMHOME2'. 2) Verify that
machine 'HESPERUS' can open files on machine 'TOMHOME2'. Debugging disabled
for connection 56.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
This setup did work prior to XP sp2, the logon account for the sql server
service is a domain (admin) account.
The odd thing now is, when I run the debugger, it actually runs, but does
not "step" thru the procedure, it goes straight thru to the end, and does not
show any of the values for the variables, connections, etc. In the results
pane, I get a result, and at the very bottom it says completed.
Putting in break points makes no difference, it just runs on to the end
regardless...
""Mingqing Cheng [MSFT]"" wrote:
> Hi Tom,
> Thanks for your posting!
> From your descriptions, I understood that you could not use Query Analyzer
> to debug after XP SP2 was upgraded. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Based on my scope, as you said it is a remotely debugging ,does it used a
> linked server? If so, here is another document address the probelm you may
> meet.
> You may receive a 7391 error message in SQL Server 2000 when you run a
> distributed transaction against a linked server after you install Microsoft
> Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=839279
> What's the error message when it fails to debugging? Could you tell me how
> to reporduce it on my machine? I need more detailed information for your
> scenario, which, I believe, will make us closer to the resolution.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||Hi Tom,
Thanks for your detailed information and descriptions!
First of all, The reason for Error 508 and Error code 0x80070005 is
permission issue. As you said it works fine before upgrading to XP SP2,
have you tried disable the Firewall os XP SP2. Close the firewall and then
tell me whether it works. Checking the following documents to make sure
your SQL Server in XP XP2 is correctly configured
How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
http://support.microsoft.com/?id=841249
Secondly, The error 0x800706ba generated is a Distributed COM communication
error when using RPC. The error code 0x800706ba translates to "RPC server
unavailable". DCOM uses Remote Procedure Call (RPC) dynamic port
allocation. By default, RPC dynamic port allocation randomly selects port
numbers above 1024, so the problem seems to be the firewall blocking the
rpc communication. Do the folloing things to make sure DCOM is running
fine.
* On the client machine
--run dcomcnfg.
--Go to the dcom config properties under default properties, there is a
check box stating "enable Distributed COM on this computer", if this was
unchecked on the client machine, this is a default setting that is checked.
make sure it is checked.
*Then copied the new sqldbg.dll and sqldbreg.exe from the SQL Server CD,
replcaed the old ones with these on the client machine and then ran the
regsvr32 sqldbg.dll for re-resgistering the dll and sqldbreg.exe
/RegServer on the client machine and rebooted the box and everything
started to work like a charm.Customer was able to debug the stored proc on
the server using SQL QA and t-sql debugger from his client machine.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||I have tried all the suggestions but the behavior remains the same: the
debugger connects and then runs thru the procedure beginning to end without
stopping, providing variable info, etc.
""Mingqing Cheng [MSFT]"" wrote:
> Hi Tom,
> Thanks for your detailed information and descriptions!
> First of all, The reason for Error 508 and Error code 0x80070005 is
> permission issue. As you said it works fine before upgrading to XP SP2,
> have you tried disable the Firewall os XP SP2. Close the firewall and then
> tell me whether it works. Checking the following documents to make sure
> your SQL Server in XP XP2 is correctly configured
> How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
> http://support.microsoft.com/?id=841249
> Secondly, The error 0x800706ba generated is a Distributed COM communication
> error when using RPC. The error code 0x800706ba translates to "RPC server
> unavailable". DCOM uses Remote Procedure Call (RPC) dynamic port
> allocation. By default, RPC dynamic port allocation randomly selects port
> numbers above 1024, so the problem seems to be the firewall blocking the
> rpc communication. Do the folloing things to make sure DCOM is running
> fine.
> * On the client machine
> --run dcomcnfg.
> --Go to the dcom config properties under default properties, there is a
> check box stating "enable Distributed COM on this computer", if this was
> unchecked on the client machine, this is a default setting that is checked.
> make sure it is checked.
> *Then copied the new sqldbg.dll and sqldbreg.exe from the SQL Server CD,
> replcaed the old ones with these on the client machine and then ran the
> regsvr32 sqldbg.dll for re-resgistering the dll and sqldbreg.exe
> /RegServer on the client machine and rebooted the box and everything
> started to work like a charm.Customer was able to debug the stored proc on
> the server using SQL QA and t-sql debugger from his client machine.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||I found the problem: after applying the hotfix to the server, the client side
tools were no longer the same version as the server. Applying the hotfix to
the client fixed the problem.
""Mingqing Cheng [MSFT]"" wrote:
> Hi Tom,
> Thanks for your detailed information and descriptions!
> First of all, The reason for Error 508 and Error code 0x80070005 is
> permission issue. As you said it works fine before upgrading to XP SP2,
> have you tried disable the Firewall os XP SP2. Close the firewall and then
> tell me whether it works. Checking the following documents to make sure
> your SQL Server in XP XP2 is correctly configured
> How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
> http://support.microsoft.com/?id=841249
> Secondly, The error 0x800706ba generated is a Distributed COM communication
> error when using RPC. The error code 0x800706ba translates to "RPC server
> unavailable". DCOM uses Remote Procedure Call (RPC) dynamic port
> allocation. By default, RPC dynamic port allocation randomly selects port
> numbers above 1024, so the problem seems to be the firewall blocking the
> rpc communication. Do the folloing things to make sure DCOM is running
> fine.
> * On the client machine
> --run dcomcnfg.
> --Go to the dcom config properties under default properties, there is a
> check box stating "enable Distributed COM on this computer", if this was
> unchecked on the client machine, this is a default setting that is checked.
> make sure it is checked.
> *Then copied the new sqldbg.dll and sqldbreg.exe from the SQL Server CD,
> replcaed the old ones with these on the client machine and then ran the
> regsvr32 sqldbg.dll for re-resgistering the dll and sqldbreg.exe
> /RegServer on the client machine and rebooted the box and everything
> started to work like a charm.Customer was able to debug the stored proc on
> the server using SQL QA and t-sql debugger from his client machine.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||I also have the same problem after installed Windows XP SP2,
the similar error message when running debugger from query analyzer.
Is there any solution for this?
"TomT" <tomt@.tomt.com> wrote in message news:<93363379-8AFA-45EA-BE8D-F53FCB3835FE@.microsoft.com>...[vbcol=seagreen]
> I am trying to debug a sql server, from a WinXP sp2 system. I was able to do
> this prior to installing XP sp2 on the WinXP system. The sql server is at
> sp3, and runs on a Windows 2003 system.
> The message I get when running the debugger is:
> Server: Msg 508, Level 16, State 1, Procedure sp_sdidebug, Line 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
> on HESPERUS (Error = 0x800706ba). Ensure that client-side components, such as
> SQLLE.DLL, are installed and registered on TOMHOME2. Debugging disabled for
> connection 58.
> ""Mingqing Cheng [MSFT]"" wrote:
|||Check my last entry on this topic, dated 9/16/2004
"duandd" wrote:
> I also have the same problem after installed Windows XP SP2,
> the similar error message when running debugger from query analyzer.
> Is there any solution for this?
> "TomT" <tomt@.tomt.com> wrote in message news:<93363379-8AFA-45EA-BE8D-F53FCB3835FE@.microsoft.com>...
>
Friday, March 9, 2012
QA Template Mystery
In query analyzer I can not see the templates, clicking on the various
folders does nothing. The tql files DO exist in the templates folder and I
have double checked that QA is looking at the correct folder. I can use the
templates from the menu, but I just can not see them in the folder tree. Any
ideas on how to fix this annoying problem?
Files are hidden or something like that?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Dean" <Dean@.discussions.microsoft.com> wrote in message
news:B0EA84C1-D862-42CA-8C92-9E727982F187@.microsoft.com...
> In query analyzer I can not see the templates, clicking on the various
> folders does nothing. The tql files DO exist in the templates folder and I
> have double checked that QA is looking at the correct folder. I can use the
> templates from the menu, but I just can not see them in the folder tree. Any
> ideas on how to fix this annoying problem?
|||Not hidden, but compressed. Thanks for the idea to look at the other
attributes. This has been driving me crazy.
"Tibor Karaszi" wrote:
> Files are hidden or something like that?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Dean" <Dean@.discussions.microsoft.com> wrote in message
> news:B0EA84C1-D862-42CA-8C92-9E727982F187@.microsoft.com...
>
>
folders does nothing. The tql files DO exist in the templates folder and I
have double checked that QA is looking at the correct folder. I can use the
templates from the menu, but I just can not see them in the folder tree. Any
ideas on how to fix this annoying problem?
Files are hidden or something like that?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Dean" <Dean@.discussions.microsoft.com> wrote in message
news:B0EA84C1-D862-42CA-8C92-9E727982F187@.microsoft.com...
> In query analyzer I can not see the templates, clicking on the various
> folders does nothing. The tql files DO exist in the templates folder and I
> have double checked that QA is looking at the correct folder. I can use the
> templates from the menu, but I just can not see them in the folder tree. Any
> ideas on how to fix this annoying problem?
|||Not hidden, but compressed. Thanks for the idea to look at the other
attributes. This has been driving me crazy.
"Tibor Karaszi" wrote:
> Files are hidden or something like that?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Dean" <Dean@.discussions.microsoft.com> wrote in message
> news:B0EA84C1-D862-42CA-8C92-9E727982F187@.microsoft.com...
>
>
QA returns different records from SQL Server EM
SQL Server 7.0
If I run the following in Query Analyzer I get no records returned:
exec GetLeadsOutcome_Dealer '1/1/2003','12/2/2003',10, '176, 183'
If, however, I run either :
exec GetLeadsOutcome_Dealer '1/1/2003','12/2/2003',10, '176'
or
exec GetLeadsOutcome_Dealer '1/1/2003','12/2/2003',10, '183'
I get a single record returned in each case (which is what I would
expect).
The SQL for GetLeadsOutcome_Dealer is:
CREATE PROCEDURE GetLeadsOutcome_Dealer
@.FromDate smalldatetime,
@.ToDate smalldatetime,
@.OutcomeTypeID integer,
@.DealerCode varchar(8000)
AS
DECLARE @.TotalLeads integer
BEGIN
SELECT @.TotalLeads=COUNT(fldLeadID) FROM tblLeads WHERE
(tblLeads.fldDealerID IS NOT NULL)
SELECT DISTINCT (dbo.tblDealers.fldDealerName),
COUNT(dbo.tblLeads.fldLeadID) as LeadCount,@.TotalLeads AS TotalLeads
FROM tblLeads LEFT OUTER JOIN
tblOutcome ON tblLeads.fldOutcomeID =
tblOutcome.fldOutcomeID RIGHT OUTER JOIN
tblDealers RIGHT OUTER JOIN
tblRegion ON tblDealers.fldRegionID =
tblRegion.fldRegionID ON tblLeads.fldDealerID = tblDealers.fldDealerID
WHERE (((dbo.tblLeads.fldEntered) BETWEEN @.FromDate And @.ToDate)) AND
tblOutcome.fldOutcomeID=@.OutcomeTypeID AND
(dbo.tblDealers.fldDealerCode in (@.DealerCode))
GROUP BY dbo.tblDealers.fldDealerName
ORDER BY dbo.tblDealers.fldDealerName
END
GO
However, if I open EM, open a table in query view, and paste this into
the SQL window,
SELECT DISTINCT tblDealers.fldDealerName, COUNT(tblLeads.fldLeadID) AS
LeadCount
FROM tblLeads LEFT OUTER JOIN
tblOutcome ON tblLeads.fldOutcomeID =
tblOutcome.fldOutcomeID RIGHT OUTER JOIN
tblDealers RIGHT OUTER JOIN
tblRegion ON tblDealers.fldRegionID =
tblRegion.fldRegionID ON tblLeads.fldDealerID = tblDealers.fldDealerID
WHERE (tblLeads.fldEntered BETWEEN '1/1/2003' AND '12/2/2003') AND
(tblOutcome.fldOutcomeID = 10) AND (tblDealers.fldDealerCode IN (176,
183))
GROUP BY tblDealers.fldDealerName
ORDER BY tblDealers.fldDealerName
I get two records returned.
What is happening?
TIA
Edward
TABLE DEFS:
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[FK_tblLeads_tblDealers]') and OBJECTPROPERTY(id,
N'IsForeignKey') = 1)
ALTER TABLE [dbo].[tblLeads] DROP CONSTRAINT FK_tblLeads_tblDealers
GO
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[FK_tblSystemUsers_tblDealers]') and
OBJECTPROPERTY(id, N'IsForeignKey') = 1)
ALTER TABLE [dbo].[tblSystemUsers] DROP CONSTRAINT
FK_tblSystemUsers_tblDealers
GO
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[FK_tblLeadNotes_tblLeads]') and OBJECTPROPERTY(id,
N'IsForeignKey') = 1)
ALTER TABLE [dbo].[tblLeadNotes] DROP CONSTRAINT
FK_tblLeadNotes_tblLeads
GO
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[FK_tblDealers_tblRegion]') and OBJECTPROPERTY(id,
N'IsForeignKey') = 1)
ALTER TABLE [dbo].[tblDealers] DROP CONSTRAINT FK_tblDealers_tblRegion
GO
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[tblDealers]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
drop table [dbo].[tblDealers]
GO
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[tblLeads]') and OBJECTPROPERTY(id, N'IsUserTable')
= 1)
drop table [dbo].[tblLeads]
GO
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[tblOutcome]') and OBJECTPROPERTY(id,
N'IsUserTable') = 1)
drop table [dbo].[tblOutcome]
GO
if exists (select * from dbo.sysobjects where id =
object_id(N'[dbo].[tblRegion]') and OBJECTPROPERTY(id, N'IsUserTable')
= 1)
drop table [dbo].[tblRegion]
GO
CREATE TABLE [dbo].[tblDealers] (
[fldDealerID] [int] IDENTITY (1, 1) NOT NULL ,
[fldDealerCode] [varchar] (50) NOT NULL ,
[fldDealerName] [varchar] (50) NULL ,
[fldDealerTel] [varchar] (20) NULL ,
[fldDealerEmail] [varchar] (100) NULL ,
[fldDealerContact] [varchar] (50) NULL ,
[fldRegionID] [int] NULL ,
[fldDealerActive] [smallint] NOT NULL ,
[fldHeadOffice] [smallint] NULL
) ON [PRIMARY]
GO
CREATE TABLE [dbo].[tblLeads] (
[fldLeadID] [int] IDENTITY (1, 1) NOT NULL ,
[fldAccountNo] [varchar] (50) NULL ,
[fldDealerID] [int] NULL ,
[fldStatusID] [int] NOT NULL ,
[fldOutcomeID] [int] NOT NULL ,
[fldContacted] [smallint] NOT NULL ,
[fldDateContacted] [smalldatetime] NULL ,
[fldAppointment] [smallint] NULL ,
[fldShowRoom] [smallint] NOT NULL ,
[fldTestDrive] [smallint] NOT NULL ,
[fldSalesPersonID] [int] NULL ,
[fldCustomerName] [varchar] (50) NULL ,
[fldCHouseNo] [varchar] (50) NULL ,
[fldCStreet] [varchar] (50) NULL ,
[fldCDistrict] [varchar] (50) NULL ,
[fldCTown] [varchar] (40) NULL ,
[fldCCounty] [varchar] (50) NULL ,
[fldCPostcode] [varchar] (50) NULL ,
[fldPhoneInd] [varchar] (20) NULL ,
[fldCTel] [varchar] (50) NULL ,
[fldNewBusinessDate] [smalldatetime] NULL ,
[fldAgreementType] [varchar] (50) NULL ,
[fldCashPrice] [smallmoney] NULL ,
[fldBalanceFin] [smallmoney] NULL ,
[fldCustRate] [varchar] (10) NULL ,
[fldOrigTerm] [int] NULL ,
[fldPPPType] [varchar] (10) NULL ,
[fldBalloonValue] [smallmoney] NULL ,
[fldMonthlyInstal] [smallmoney] NULL ,
[fldRegNo] [varchar] (10) NULL ,
[fldRegDate] [smalldatetime] NULL ,
[fldModel] [varchar] (50) NULL ,
[fldDescription] [varchar] (50) NULL ,
[fldTheoPIFDate] [smalldatetime] NULL ,
[fldMonthsToGo] [int] NULL ,
[fldBalanceOS] [smallmoney] NULL ,
[fldLeadPrinted] [smallint] NULL ,
[fldMergeFile] [varchar] (255) NULL ,
[fldTPS] [varchar] (10) NULL ,
[fldMPS] [varchar] (10) NULL ,
[fldUpdated] [smalldatetime] NULL ,
[fldUpdatedBy] [int] NULL ,
[fldEntered] [smalldatetime] NULL ,
[fldReasonLeadNotProgressed] [varchar] (5000) NULL
) ON [PRIMARY]
GO
CREATE TABLE [dbo].[tblOutcome] (
[fldOutcomeID] [int] IDENTITY (1, 1) NOT NULL ,
[fldOutcomeCode] [int] NULL ,
[fldOutcome] [varchar] (100) NULL ,
[fldConvertedSales] [smallint] NULL
) ON [PRIMARY]
GO
CREATE TABLE [dbo].[tblRegion] (
[fldRegionID] [int] IDENTITY (1, 1) NOT NULL ,
[fldRegionCode] [varchar] (10) NULL ,
[fldRegion] [varchar] (50) NULL
) ON [PRIMARY]
GO
ALTER TABLE [dbo].[tblDealers] WITH NOCHECK ADD
CONSTRAINT [PK_tblDealers] PRIMARY KEY CLUSTERED
(
[fldDealerID]
) WITH FILLFACTOR = 90 ON [PRIMARY]
GO
ALTER TABLE [dbo].[tblLeads] WITH NOCHECK ADD
CONSTRAINT [PK_tblLeads] PRIMARY KEY CLUSTERED
(
[fldLeadID]
) WITH FILLFACTOR = 90 ON [PRIMARY]
GO
ALTER TABLE [dbo].[tblOutcome] WITH NOCHECK ADD
CONSTRAINT [PK_tblOutcome] PRIMARY KEY CLUSTERED
(
[fldOutcomeID]
) WITH FILLFACTOR = 90 ON [PRIMARY]
GO
ALTER TABLE [dbo].[tblRegion] WITH NOCHECK ADD
CONSTRAINT [PK_tblArea] PRIMARY KEY CLUSTERED
(
[fldRegionID]
) WITH FILLFACTOR = 90 ON [PRIMARY]
GO
ALTER TABLE [dbo].[tblDealers] WITH NOCHECK ADD
CONSTRAINT [DF_tblDealers_fldActive] DEFAULT ((-1)) FOR
[fldDealerActive],
CONSTRAINT [DF_tblDealers_fldHeadOffice] DEFAULT (0) FOR
[fldHeadOffice],
CONSTRAINT [IX_tblDealers] UNIQUE NONCLUSTERED
(
[fldDealerCode]
) ON [PRIMARY]
GO
ALTER TABLE [dbo].[tblLeads] WITH NOCHECK ADD
CONSTRAINT [DF_tblLeads_fldOutcomeID] DEFAULT (10) FOR
[fldOutcomeID],
CONSTRAINT [DF_tblLeads_fldContacted] DEFAULT (0) FOR [fldContacted],
CONSTRAINT [DF_tblLeads_fldAppointment] DEFAULT (0) FOR
[fldAppointment],
CONSTRAINT [DF_tblLeads_fldShowRoom] DEFAULT (0) FOR [fldShowRoom],
CONSTRAINT [DF_tblLeads_fldTestDrive] DEFAULT (0) FOR [fldTestDrive],
CONSTRAINT [DF_tblLeads_fldLeadPrinted] DEFAULT (0) FOR
[fldLeadPrinted],
CONSTRAINT [DF_tblLeads_fldTPSMatch] DEFAULT ('NO') FOR [fldTPS],
CONSTRAINT [DF_tblLeads_fldMPSMatch] DEFAULT ('NO') FOR [fldMPS]
GO
ALTER TABLE [dbo].[tblOutcome] WITH NOCHECK ADD
CONSTRAINT [DF_tblOutcome_fldConvertedSales] DEFAULT (0) FOR
[fldConvertedSales]
GO
ALTER TABLE [dbo].[tblRegion] WITH NOCHECK ADD
CONSTRAINT [IX_tblRegion] UNIQUE NONCLUSTERED
(
[fldRegionCode]
) ON [PRIMARY]
GO
ALTER TABLE [dbo].[tblDealers] ADD
CONSTRAINT [FK_tblDealers_tblRegion] FOREIGN KEY
(
[fldRegionID]
) REFERENCES [dbo].[tblRegion] (
[fldRegionID]
)
GO
ALTER TABLE [dbo].[tblLeads] ADD
CONSTRAINT [FK_tblLeads_tblDealers] FOREIGN KEY
(
[fldDealerID]
) REFERENCES [dbo].[tblDealers] (
[fldDealerID]
)
GO
alter table [dbo].[tblLeads] nocheck constraint
[FK_tblLeads_tblDealers]
GOEdward (teddysnips@.hotmail.com) writes:
> If I run the following in Query Analyzer I get no records returned:
> exec GetLeadsOutcome_Dealer '1/1/2003','12/2/2003',10, '176, 183'
>...
> The SQL for GetLeadsOutcome_Dealer is:
> ...
> (dbo.tblDealers.fldDealerCode in (@.DealerCode))
Apparently, you dont have any dealer with the code '176, 183'.
> However, if I open EM, open a table in query view, and paste this into
> the SQL window,
>...
> (tblDealers.fldDealerCode IN (176, 183))
Here you have two different values. In the procedure you have only one.
Looks like you need a procedure that unpacks a list of values into
a table. Look at
http://www.algonet.se/~sommar/array...-of-string-proc.
(This brings you to a procedure which is for SQL7. But you have have
to read some other parts of the long text to make sense of it.)
--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||teddysnips@.hotmail.com (Edward) wrote in message news:<25080b60.0312020231.449732c@.posting.google.com>...
> SQL Server 7.0
> If I run the following in Query Analyzer I get no records returned:
> exec GetLeadsOutcome_Dealer '1/1/2003','12/2/2003',10, '176, 183'
> If, however, I run either :
> exec GetLeadsOutcome_Dealer '1/1/2003','12/2/2003',10, '176'
> or
> exec GetLeadsOutcome_Dealer '1/1/2003','12/2/2003',10, '183'
> I get a single record returned in each case (which is what I would
> expect).
<snip
Your first SQL statement essentially comes down to this:
select * from table where column in ('183, 176')
In other words, return the columns with a value of '183, 176'. Since
there aren't any, you get no rows. What you are trying to achieve is
this - return columns with a value of '183' or '176':
select * from table where column in ('183', '176')
When you use a single value for the variable, you get a valid query,
and hence a single result:
select * from table where column in ('183')
You're getting results in EM because you've correctly typed in the
values manually.
See here for a fuller discussion:
http://www.algonet.se/~sommar/dynamic_sql.html#List
Simon
QA Debugger
I need help resolving a problem our developers are having with Query Analyzer
debugger. They get an error "Server: Msg 504, Level 16, State 1, Procedure
sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
on SALESTEMP (Error = 0x800706ba). Ensure that client-side components, such
as SQLDBREG.EXE, are installed and registered on <local pc name>. Debugging
disabled for connection 63." when they attempt to debug stored procedures.
Does anyone have any suggestions?You want to start with the steps in the article in books
online for: Troubleshooting the Transact-SQL Debugger
In addition, if you are using SQL Server 2000 SP 3 you will
want to refer to the following article:
The T-SQL Debugger is turned off by default for earlier
clients after you install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Fri, 14 Jan 2005 06:19:10 -0800, "Ray Kurpiel"
<RayKurpiel@.discussions.microsoft.com> wrote:
>I need help resolving a problem our developers are having with Query Analyzer
>debugger. They get an error "Server: Msg 504, Level 16, State 1, Procedure
>sp_sdidebug, Line 1
>[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
>on SALESTEMP (Error = 0x800706ba). Ensure that client-side components, such
>as SQLDBREG.EXE, are installed and registered on <local pc name>. Debugging
>disabled for connection 63." when they attempt to debug stored procedures.
>Does anyone have any suggestions?
>
debugger. They get an error "Server: Msg 504, Level 16, State 1, Procedure
sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
on SALESTEMP (Error = 0x800706ba). Ensure that client-side components, such
as SQLDBREG.EXE, are installed and registered on <local pc name>. Debugging
disabled for connection 63." when they attempt to debug stored procedures.
Does anyone have any suggestions?You want to start with the steps in the article in books
online for: Troubleshooting the Transact-SQL Debugger
In addition, if you are using SQL Server 2000 SP 3 you will
want to refer to the following article:
The T-SQL Debugger is turned off by default for earlier
clients after you install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Fri, 14 Jan 2005 06:19:10 -0800, "Ray Kurpiel"
<RayKurpiel@.discussions.microsoft.com> wrote:
>I need help resolving a problem our developers are having with Query Analyzer
>debugger. They get an error "Server: Msg 504, Level 16, State 1, Procedure
>sp_sdidebug, Line 1
>[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
>on SALESTEMP (Error = 0x800706ba). Ensure that client-side components, such
>as SQLDBREG.EXE, are installed and registered on <local pc name>. Debugging
>disabled for connection 63." when they attempt to debug stored procedures.
>Does anyone have any suggestions?
>
QA database change take too much time
Hi,
MSSQL 2K, SP4 on XP sp2
While connected to local SQL server, when I click on DatabBase drop down
Combo in Query Analyzer, it takes around 10+ seconds before displaying the
databases to select, however if I connect to another SQL server on my office
LAN, then list appears with no time.
appreciate your help to fix this.
Thanks
Falik
To add on to Kalen;
You might be you have enabled the database option "AUTOCLOSE". THis will
close
the MDF and LDF as soon as the last user logs of the database. Again the MDF
and LDF will be opened once a user logins to the database.
How to check this option is checked:-
1. Enterprise manager -- Databases -- Select the database
2. Right click and select properties -- Choose options
3. Chek whether AUTOCLOSE option is "checked". If yes then remove it
This will ensure that MDF and LDF will never closed as soon as last user
logs off.
Thanks
Hari
"Falik Sher" <faliks@.hotmail.com> wrote in message
news:%23npQHWQFHHA.5104@.TK2MSFTNGP03.phx.gbl...
> Hi,
> MSSQL 2K, SP4 on XP sp2
> While connected to local SQL server, when I click on DatabBase drop down
> Combo in Query Analyzer, it takes around 10+ seconds before displaying the
> databases to select, however if I connect to another SQL server on my
> office LAN, then list appears with no time.
> appreciate your help to fix this.
> Thanks
> Falik
>
MSSQL 2K, SP4 on XP sp2
While connected to local SQL server, when I click on DatabBase drop down
Combo in Query Analyzer, it takes around 10+ seconds before displaying the
databases to select, however if I connect to another SQL server on my office
LAN, then list appears with no time.
appreciate your help to fix this.
Thanks
Falik
To add on to Kalen;
You might be you have enabled the database option "AUTOCLOSE". THis will
close
the MDF and LDF as soon as the last user logs of the database. Again the MDF
and LDF will be opened once a user logins to the database.
How to check this option is checked:-
1. Enterprise manager -- Databases -- Select the database
2. Right click and select properties -- Choose options
3. Chek whether AUTOCLOSE option is "checked". If yes then remove it
This will ensure that MDF and LDF will never closed as soon as last user
logs off.
Thanks
Hari
"Falik Sher" <faliks@.hotmail.com> wrote in message
news:%23npQHWQFHHA.5104@.TK2MSFTNGP03.phx.gbl...
> Hi,
> MSSQL 2K, SP4 on XP sp2
> While connected to local SQL server, when I click on DatabBase drop down
> Combo in Query Analyzer, it takes around 10+ seconds before displaying the
> databases to select, however if I connect to another SQL server on my
> office LAN, then list appears with no time.
> appreciate your help to fix this.
> Thanks
> Falik
>
QA database change take too much time
Hi,
MSSQL 2K, SP4 on XP sp2
While connected to local SQL server, when I click on DatabBase drop down
Combo in Query Analyzer, it takes around 10+ seconds before displaying the
databases to select, however if I connect to another SQL server on my office
LAN, then list appears with no time.
appreciate your help to fix this.
Thanks
FalikAre the databases set to autoclose on your local SQL Server?
HTH
Kalen Delaney, SQL Server MVP
http://sqlblog.com
"Falik Sher" <faliks@.hotmail.com> wrote in message
news:%23npQHWQFHHA.5104@.TK2MSFTNGP03.phx.gbl...
> Hi,
> MSSQL 2K, SP4 on XP sp2
> While connected to local SQL server, when I click on DatabBase drop down
> Combo in Query Analyzer, it takes around 10+ seconds before displaying the
> databases to select, however if I connect to another SQL server on my
> office LAN, then list appears with no time.
> appreciate your help to fix this.
> Thanks
> Falik
>|||To add on to Kalen;
You might be you have enabled the database option "AUTOCLOSE". THis will
close
the MDF and LDF as soon as the last user logs of the database. Again the MDF
and LDF will be opened once a user logins to the database.
How to check this option is checked:-
1. Enterprise manager -- Databases -- Select the database
2. Right click and select properties -- Choose options
3. Chek whether AUTOCLOSE option is "checked". If yes then remove it
This will ensure that MDF and LDF will never closed as soon as last user
logs off.
Thanks
Hari
"Falik Sher" <faliks@.hotmail.com> wrote in message
news:%23npQHWQFHHA.5104@.TK2MSFTNGP03.phx.gbl...
> Hi,
> MSSQL 2K, SP4 on XP sp2
> While connected to local SQL server, when I click on DatabBase drop down
> Combo in Query Analyzer, it takes around 10+ seconds before displaying the
> databases to select, however if I connect to another SQL server on my
> office LAN, then list appears with no time.
> appreciate your help to fix this.
> Thanks
> Falik
>
MSSQL 2K, SP4 on XP sp2
While connected to local SQL server, when I click on DatabBase drop down
Combo in Query Analyzer, it takes around 10+ seconds before displaying the
databases to select, however if I connect to another SQL server on my office
LAN, then list appears with no time.
appreciate your help to fix this.
Thanks
FalikAre the databases set to autoclose on your local SQL Server?
HTH
Kalen Delaney, SQL Server MVP
http://sqlblog.com
"Falik Sher" <faliks@.hotmail.com> wrote in message
news:%23npQHWQFHHA.5104@.TK2MSFTNGP03.phx.gbl...
> Hi,
> MSSQL 2K, SP4 on XP sp2
> While connected to local SQL server, when I click on DatabBase drop down
> Combo in Query Analyzer, it takes around 10+ seconds before displaying the
> databases to select, however if I connect to another SQL server on my
> office LAN, then list appears with no time.
> appreciate your help to fix this.
> Thanks
> Falik
>|||To add on to Kalen;
You might be you have enabled the database option "AUTOCLOSE". THis will
close
the MDF and LDF as soon as the last user logs of the database. Again the MDF
and LDF will be opened once a user logins to the database.
How to check this option is checked:-
1. Enterprise manager -- Databases -- Select the database
2. Right click and select properties -- Choose options
3. Chek whether AUTOCLOSE option is "checked". If yes then remove it
This will ensure that MDF and LDF will never closed as soon as last user
logs off.
Thanks
Hari
"Falik Sher" <faliks@.hotmail.com> wrote in message
news:%23npQHWQFHHA.5104@.TK2MSFTNGP03.phx.gbl...
> Hi,
> MSSQL 2K, SP4 on XP sp2
> While connected to local SQL server, when I click on DatabBase drop down
> Combo in Query Analyzer, it takes around 10+ seconds before displaying the
> databases to select, however if I connect to another SQL server on my
> office LAN, then list appears with no time.
> appreciate your help to fix this.
> Thanks
> Falik
>
QA database change take too much time
Hi,
MSSQL 2K, SP4 on XP sp2
While connected to local SQL server, when I click on DatabBase drop down
Combo in Query Analyzer, it takes around 10+ seconds before displaying the
databases to select, however if I connect to another SQL server on my office
LAN, then list appears with no time.
appreciate your help to fix this.
Thanks
FalikAre the databases set to autoclose on your local SQL Server?
--
HTH
Kalen Delaney, SQL Server MVP
http://sqlblog.com
"Falik Sher" <faliks@.hotmail.com> wrote in message
news:%23npQHWQFHHA.5104@.TK2MSFTNGP03.phx.gbl...
> Hi,
> MSSQL 2K, SP4 on XP sp2
> While connected to local SQL server, when I click on DatabBase drop down
> Combo in Query Analyzer, it takes around 10+ seconds before displaying the
> databases to select, however if I connect to another SQL server on my
> office LAN, then list appears with no time.
> appreciate your help to fix this.
> Thanks
> Falik
>|||To add on to Kalen;
You might be you have enabled the database option "AUTOCLOSE". THis will
close
the MDF and LDF as soon as the last user logs of the database. Again the MDF
and LDF will be opened once a user logins to the database.
How to check this option is checked:-
1. Enterprise manager -- Databases -- Select the database
2. Right click and select properties -- Choose options
3. Chek whether AUTOCLOSE option is "checked". If yes then remove it
This will ensure that MDF and LDF will never closed as soon as last user
logs off.
Thanks
Hari
"Falik Sher" <faliks@.hotmail.com> wrote in message
news:%23npQHWQFHHA.5104@.TK2MSFTNGP03.phx.gbl...
> Hi,
> MSSQL 2K, SP4 on XP sp2
> While connected to local SQL server, when I click on DatabBase drop down
> Combo in Query Analyzer, it takes around 10+ seconds before displaying the
> databases to select, however if I connect to another SQL server on my
> office LAN, then list appears with no time.
> appreciate your help to fix this.
> Thanks
> Falik
>
MSSQL 2K, SP4 on XP sp2
While connected to local SQL server, when I click on DatabBase drop down
Combo in Query Analyzer, it takes around 10+ seconds before displaying the
databases to select, however if I connect to another SQL server on my office
LAN, then list appears with no time.
appreciate your help to fix this.
Thanks
FalikAre the databases set to autoclose on your local SQL Server?
--
HTH
Kalen Delaney, SQL Server MVP
http://sqlblog.com
"Falik Sher" <faliks@.hotmail.com> wrote in message
news:%23npQHWQFHHA.5104@.TK2MSFTNGP03.phx.gbl...
> Hi,
> MSSQL 2K, SP4 on XP sp2
> While connected to local SQL server, when I click on DatabBase drop down
> Combo in Query Analyzer, it takes around 10+ seconds before displaying the
> databases to select, however if I connect to another SQL server on my
> office LAN, then list appears with no time.
> appreciate your help to fix this.
> Thanks
> Falik
>|||To add on to Kalen;
You might be you have enabled the database option "AUTOCLOSE". THis will
close
the MDF and LDF as soon as the last user logs of the database. Again the MDF
and LDF will be opened once a user logins to the database.
How to check this option is checked:-
1. Enterprise manager -- Databases -- Select the database
2. Right click and select properties -- Choose options
3. Chek whether AUTOCLOSE option is "checked". If yes then remove it
This will ensure that MDF and LDF will never closed as soon as last user
logs off.
Thanks
Hari
"Falik Sher" <faliks@.hotmail.com> wrote in message
news:%23npQHWQFHHA.5104@.TK2MSFTNGP03.phx.gbl...
> Hi,
> MSSQL 2K, SP4 on XP sp2
> While connected to local SQL server, when I click on DatabBase drop down
> Combo in Query Analyzer, it takes around 10+ seconds before displaying the
> databases to select, however if I connect to another SQL server on my
> office LAN, then list appears with no time.
> appreciate your help to fix this.
> Thanks
> Falik
>
QA Alternatives
What good alternatives are there to SQL Server Query Analyzer ? I'm
especially interested in lower-cost ones but would be interested in hearing
about anything good
Thanks ...Liz
> What good alternatives are there to SQL Server Query Analyzer ?
To upgrade to SQL Server 2005 and have an Object Explorer :-)))
I think you came from Oracle area , so there is no good alternatives SQL
Server Query Analyzer ...
"Liz" <liz@.tiredofspam.com> wrote in message
news:OtQsNnyfHHA.4552@.TK2MSFTNGP04.phx.gbl...
> What good alternatives are there to SQL Server Query Analyzer ? I'm
> especially interested in lower-cost ones but would be interested in
> hearing about anything good
> Thanks ...
>
>|||Hi Liz/Uri
"Uri Dimant" wrote:
> Liz
> > What good alternatives are there to SQL Server Query Analyzer ?
> To upgrade to SQL Server 2005 and have an Object Explorer :-)))
But Object Explorer is also available in QA!!! F8 works in both QA and SQL
Server Management Studio:) In SSMS the object explorer does incorporate
functionality in Enterprise Manager... so maybe Liz should take a look at
that?
> I think you came from Oracle area , so there is no good alternatives SQL
> Server Query Analyzer ...
Did I miss something... Oracle and good tools are not two phrases I would
expect in the same sentence... Oracle and the requirement for third party
tools seems to be the norm!
> "Liz" <liz@.tiredofspam.com> wrote in message
> news:OtQsNnyfHHA.4552@.TK2MSFTNGP04.phx.gbl...
> >
> > What good alternatives are there to SQL Server Query Analyzer ? I'm
> > especially interested in lower-cost ones but would be interested in
> > hearing about anything good
There is no lower cost than free! What features do you require?
> >
> > Thanks ...
> >
John|||Hi John
> But Object Explorer is also available in QA!!! F8 works in both QA and SQL
> Server Management Studio:) In SSMS the object explorer does incorporate
> functionality in Enterprise Manager... so maybe Liz should take a look at
> that?
Right, but in Object Explorer ( As you press New Query) in SQL Server 2005
you can see all registered servers and as result jobs,mp...
> Did I miss something... Oracle and good tools are not two phrases I would
> expect in the same sentence... Oracle and the requirement for third party
> tools seems to be the norm!
Sorry, what I meant was as an analog of QA in SQL Server , you have to buy
or free download (SQL Developer as I remeber well) a tool to query the
database,
am I right John?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:3F20D1A0-32D4-4489-BF5E-B2F6D62CE117@.microsoft.com...
> Hi Liz/Uri
> "Uri Dimant" wrote:
>> Liz
>> > What good alternatives are there to SQL Server Query Analyzer ?
>> To upgrade to SQL Server 2005 and have an Object Explorer :-)))
> But Object Explorer is also available in QA!!! F8 works in both QA and SQL
> Server Management Studio:) In SSMS the object explorer does incorporate
> functionality in Enterprise Manager... so maybe Liz should take a look at
> that?
>> I think you came from Oracle area , so there is no good alternatives SQL
>> Server Query Analyzer ...
> Did I miss something... Oracle and good tools are not two phrases I would
> expect in the same sentence... Oracle and the requirement for third party
> tools seems to be the norm!
>> "Liz" <liz@.tiredofspam.com> wrote in message
>> news:OtQsNnyfHHA.4552@.TK2MSFTNGP04.phx.gbl...
>> >
>> > What good alternatives are there to SQL Server Query Analyzer ? I'm
>> > especially interested in lower-cost ones but would be interested in
>> > hearing about anything good
> There is no lower cost than free! What features do you require?
>> >
>> > Thanks ...
>> >
> John|||See inline..
"Uri Dimant" wrote:
> Hi John
> > But Object Explorer is also available in QA!!! F8 works in both QA and SQL
> > Server Management Studio:) In SSMS the object explorer does incorporate
> > functionality in Enterprise Manager... so maybe Liz should take a look at
> > that?
> Right, but in Object Explorer ( As you press New Query) in SQL Server 2005
> you can see all registered servers and as result jobs,mp...
That is why I would say look at EM.. but then for querying QA is the better
option
>
> > Did I miss something... Oracle and good tools are not two phrases I would
> > expect in the same sentence... Oracle and the requirement for third party
> > tools seems to be the norm!
> Sorry, what I meant was as an analog of QA in SQL Server , you have to buy
> or free download (SQL Developer as I remeber well) a tool to query the
> database,
> am I right John?
I only used SQL*Plus, so QA spoils me!! :)
I quick Google for "Query Analyzer Alternative" gave
http://discuss.joelonsoftware.com/default.asp?joel.3.180407.9
http://gpoulose.home.att.net/
Toad is a great favourite in the Oracle world so you may want to look at
that http://www.toadsoft.com/toadsqlserver/toad_sqlserver.htm
At $50 the SQL 2005 developer edition could be a good investment especially
if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as well
as SQL 2005.
John|||> At $50 the SQL 2005 developer edition could be a good investment
> especially
> if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as
> well
> as SQL 2005.
Agreed
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:A4E9A194-834B-4E97-A5C8-62383BA14AA1@.microsoft.com...
> See inline..
> "Uri Dimant" wrote:
>> Hi John
>> > But Object Explorer is also available in QA!!! F8 works in both QA and
>> > SQL
>> > Server Management Studio:) In SSMS the object explorer does incorporate
>> > functionality in Enterprise Manager... so maybe Liz should take a look
>> > at
>> > that?
>> Right, but in Object Explorer ( As you press New Query) in SQL Server
>> 2005
>> you can see all registered servers and as result jobs,mp...
> That is why I would say look at EM.. but then for querying QA is the
> better
> option
>>
>> > Did I miss something... Oracle and good tools are not two phrases I
>> > would
>> > expect in the same sentence... Oracle and the requirement for third
>> > party
>> > tools seems to be the norm!
>> Sorry, what I meant was as an analog of QA in SQL Server , you have to
>> buy
>> or free download (SQL Developer as I remeber well) a tool to query the
>> database,
>> am I right John?
> I only used SQL*Plus, so QA spoils me!! :)
> I quick Google for "Query Analyzer Alternative" gave
> http://discuss.joelonsoftware.com/default.asp?joel.3.180407.9
> http://gpoulose.home.att.net/
> Toad is a great favourite in the Oracle world so you may want to look at
> that http://www.toadsoft.com/toadsqlserver/toad_sqlserver.htm
> At $50 the SQL 2005 developer edition could be a good investment
> especially
> if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as
> well
> as SQL 2005.
> John|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ebVAju0fHHA.1252@.TK2MSFTNGP04.phx.gbl...
>> At $50 the SQL 2005 developer edition could be a good investment
>> especially
>> if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as
>> well as SQL 2005.
What does "one user" mean in SQL Developer ? is it possible to test with
multiple connections ? is this an honor system thing where MS expects you
basically not to deploy for production use ?
So everyone uses QA or Management Studio ? I have SQL2005 but have not
really been able to use it much for time reasons; seems to me some of these
third party tools have some useful features like import/export tools (that
are easier/faster to use than DTS), intellisense, .NET code generation,
schema and data diff tools, synchronization, etc. I'm not unhappy with QA
but I do like to keep an eye out for tools that will make me more productive
Liz
especially interested in lower-cost ones but would be interested in hearing
about anything good
Thanks ...Liz
> What good alternatives are there to SQL Server Query Analyzer ?
To upgrade to SQL Server 2005 and have an Object Explorer :-)))
I think you came from Oracle area , so there is no good alternatives SQL
Server Query Analyzer ...
"Liz" <liz@.tiredofspam.com> wrote in message
news:OtQsNnyfHHA.4552@.TK2MSFTNGP04.phx.gbl...
> What good alternatives are there to SQL Server Query Analyzer ? I'm
> especially interested in lower-cost ones but would be interested in
> hearing about anything good
> Thanks ...
>
>|||Hi Liz/Uri
"Uri Dimant" wrote:
> Liz
> > What good alternatives are there to SQL Server Query Analyzer ?
> To upgrade to SQL Server 2005 and have an Object Explorer :-)))
But Object Explorer is also available in QA!!! F8 works in both QA and SQL
Server Management Studio:) In SSMS the object explorer does incorporate
functionality in Enterprise Manager... so maybe Liz should take a look at
that?
> I think you came from Oracle area , so there is no good alternatives SQL
> Server Query Analyzer ...
Did I miss something... Oracle and good tools are not two phrases I would
expect in the same sentence... Oracle and the requirement for third party
tools seems to be the norm!
> "Liz" <liz@.tiredofspam.com> wrote in message
> news:OtQsNnyfHHA.4552@.TK2MSFTNGP04.phx.gbl...
> >
> > What good alternatives are there to SQL Server Query Analyzer ? I'm
> > especially interested in lower-cost ones but would be interested in
> > hearing about anything good
There is no lower cost than free! What features do you require?
> >
> > Thanks ...
> >
John|||Hi John
> But Object Explorer is also available in QA!!! F8 works in both QA and SQL
> Server Management Studio:) In SSMS the object explorer does incorporate
> functionality in Enterprise Manager... so maybe Liz should take a look at
> that?
Right, but in Object Explorer ( As you press New Query) in SQL Server 2005
you can see all registered servers and as result jobs,mp...
> Did I miss something... Oracle and good tools are not two phrases I would
> expect in the same sentence... Oracle and the requirement for third party
> tools seems to be the norm!
Sorry, what I meant was as an analog of QA in SQL Server , you have to buy
or free download (SQL Developer as I remeber well) a tool to query the
database,
am I right John?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:3F20D1A0-32D4-4489-BF5E-B2F6D62CE117@.microsoft.com...
> Hi Liz/Uri
> "Uri Dimant" wrote:
>> Liz
>> > What good alternatives are there to SQL Server Query Analyzer ?
>> To upgrade to SQL Server 2005 and have an Object Explorer :-)))
> But Object Explorer is also available in QA!!! F8 works in both QA and SQL
> Server Management Studio:) In SSMS the object explorer does incorporate
> functionality in Enterprise Manager... so maybe Liz should take a look at
> that?
>> I think you came from Oracle area , so there is no good alternatives SQL
>> Server Query Analyzer ...
> Did I miss something... Oracle and good tools are not two phrases I would
> expect in the same sentence... Oracle and the requirement for third party
> tools seems to be the norm!
>> "Liz" <liz@.tiredofspam.com> wrote in message
>> news:OtQsNnyfHHA.4552@.TK2MSFTNGP04.phx.gbl...
>> >
>> > What good alternatives are there to SQL Server Query Analyzer ? I'm
>> > especially interested in lower-cost ones but would be interested in
>> > hearing about anything good
> There is no lower cost than free! What features do you require?
>> >
>> > Thanks ...
>> >
> John|||See inline..
"Uri Dimant" wrote:
> Hi John
> > But Object Explorer is also available in QA!!! F8 works in both QA and SQL
> > Server Management Studio:) In SSMS the object explorer does incorporate
> > functionality in Enterprise Manager... so maybe Liz should take a look at
> > that?
> Right, but in Object Explorer ( As you press New Query) in SQL Server 2005
> you can see all registered servers and as result jobs,mp...
That is why I would say look at EM.. but then for querying QA is the better
option
>
> > Did I miss something... Oracle and good tools are not two phrases I would
> > expect in the same sentence... Oracle and the requirement for third party
> > tools seems to be the norm!
> Sorry, what I meant was as an analog of QA in SQL Server , you have to buy
> or free download (SQL Developer as I remeber well) a tool to query the
> database,
> am I right John?
I only used SQL*Plus, so QA spoils me!! :)
I quick Google for "Query Analyzer Alternative" gave
http://discuss.joelonsoftware.com/default.asp?joel.3.180407.9
http://gpoulose.home.att.net/
Toad is a great favourite in the Oracle world so you may want to look at
that http://www.toadsoft.com/toadsqlserver/toad_sqlserver.htm
At $50 the SQL 2005 developer edition could be a good investment especially
if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as well
as SQL 2005.
John|||> At $50 the SQL 2005 developer edition could be a good investment
> especially
> if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as
> well
> as SQL 2005.
Agreed
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:A4E9A194-834B-4E97-A5C8-62383BA14AA1@.microsoft.com...
> See inline..
> "Uri Dimant" wrote:
>> Hi John
>> > But Object Explorer is also available in QA!!! F8 works in both QA and
>> > SQL
>> > Server Management Studio:) In SSMS the object explorer does incorporate
>> > functionality in Enterprise Manager... so maybe Liz should take a look
>> > at
>> > that?
>> Right, but in Object Explorer ( As you press New Query) in SQL Server
>> 2005
>> you can see all registered servers and as result jobs,mp...
> That is why I would say look at EM.. but then for querying QA is the
> better
> option
>>
>> > Did I miss something... Oracle and good tools are not two phrases I
>> > would
>> > expect in the same sentence... Oracle and the requirement for third
>> > party
>> > tools seems to be the norm!
>> Sorry, what I meant was as an analog of QA in SQL Server , you have to
>> buy
>> or free download (SQL Developer as I remeber well) a tool to query the
>> database,
>> am I right John?
> I only used SQL*Plus, so QA spoils me!! :)
> I quick Google for "Query Analyzer Alternative" gave
> http://discuss.joelonsoftware.com/default.asp?joel.3.180407.9
> http://gpoulose.home.att.net/
> Toad is a great favourite in the Oracle world so you may want to look at
> that http://www.toadsoft.com/toadsqlserver/toad_sqlserver.htm
> At $50 the SQL 2005 developer edition could be a good investment
> especially
> if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as
> well
> as SQL 2005.
> John|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ebVAju0fHHA.1252@.TK2MSFTNGP04.phx.gbl...
>> At $50 the SQL 2005 developer edition could be a good investment
>> especially
>> if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as
>> well as SQL 2005.
What does "one user" mean in SQL Developer ? is it possible to test with
multiple connections ? is this an honor system thing where MS expects you
basically not to deploy for production use ?
So everyone uses QA or Management Studio ? I have SQL2005 but have not
really been able to use it much for time reasons; seems to me some of these
third party tools have some useful features like import/export tools (that
are easier/faster to use than DTS), intellisense, .NET code generation,
schema and data diff tools, synchronization, etc. I'm not unhappy with QA
but I do like to keep an eye out for tools that will make me more productive
Liz
QA Alternatives
What good alternatives are there to SQL Server Query Analyzer ? I'm
especially interested in lower-cost ones but would be interested in hearing
about anything good
Thanks ...Liz
> What good alternatives are there to SQL Server Query Analyzer ?
To upgrade to SQL Server 2005 and have an Object Explorer :-)))
I think you came from Oracle area , so there is no good alternatives SQL
Server Query Analyzer ...
"Liz" <liz@.tiredofspam.com> wrote in message
news:OtQsNnyfHHA.4552@.TK2MSFTNGP04.phx.gbl...
> What good alternatives are there to SQL Server Query Analyzer ? I'm
> especially interested in lower-cost ones but would be interested in
> hearing about anything good
> Thanks ...
>
>|||Hi Liz/Uri
"Uri Dimant" wrote:
> Liz
>
> To upgrade to SQL Server 2005 and have an Object Explorer :-)))
But Object Explorer is also available in QA!!! F8 works in both QA and SQL
Server Management Studio
In SSMS the object explorer does incorporate
functionality in Enterprise Manager... so maybe Liz should take a look at
that?
> I think you came from Oracle area , so there is no good alternatives SQL
> Server Query Analyzer ...
Did I miss something... Oracle and good tools are not two phrases I would
expect in the same sentence... Oracle and the requirement for third party
tools seems to be the norm!
[vbcol=seagreen]
> "Liz" <liz@.tiredofspam.com> wrote in message
> news:OtQsNnyfHHA.4552@.TK2MSFTNGP04.phx.gbl...
There is no lower cost than free! What features do you require?
[vbcol=seagreen]
John|||Hi John
> But Object Explorer is also available in QA!!! F8 works in both QA and SQL
> Server Management Studio In SSMS the object explorer does incorporate
> functionality in Enterprise Manager... so maybe Liz should take a look at
> that?
Right, but in Object Explorer ( As you press New Query) in SQL Server 2005
you can see all registered servers and as result jobs,mp...
> Did I miss something... Oracle and good tools are not two phrases I would
> expect in the same sentence... Oracle and the requirement for third party
> tools seems to be the norm!
Sorry, what I meant was as an analog of QA in SQL Server , you have to buy
or free download (SQL Developer as I remeber well) a tool to query the
database,
am I right John?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:3F20D1A0-32D4-4489-BF5E-B2F6D62CE117@.microsoft.com...
> Hi Liz/Uri
> "Uri Dimant" wrote:
>
> But Object Explorer is also available in QA!!! F8 works in both QA and SQL
> Server Management Studio In SSMS the object explorer does incorporate
> functionality in Enterprise Manager... so maybe Liz should take a look at
> that?
>
> Did I miss something... Oracle and good tools are not two phrases I would
> expect in the same sentence... Oracle and the requirement for third party
> tools seems to be the norm!
>
> There is no lower cost than free! What features do you require?
>
> John|||See inline..
"Uri Dimant" wrote:
> Hi John
> Right, but in Object Explorer ( As you press New Query) in SQL Server 2005
> you can see all registered servers and as result jobs,mp...
That is why I would say look at EM.. but then for querying QA is the better
option
>
> Sorry, what I meant was as an analog of QA in SQL Server , you have to b
uy
> or free download (SQL Developer as I remeber well) a tool to query the
> database,
> am I right John?
I only used SQL*Plus, so QA spoils me!!
I quick Google for "Query Analyzer Alternative" gave
http://discuss.joelonsoftware.com/d...joel.3.180407.9
http://gpoulose.home.att.net/
Toad is a great favourite in the Oracle world so you may want to look at
that http://www.toadsoft.com/toadsqlserv...d_sqlserver.htm
At $50 the SQL 2005 developer edition could be a good investment especially
if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as well
as SQL 2005.
John|||> At $50 the SQL 2005 developer edition could be a good investment
> especially
> if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as
> well
> as SQL 2005.
Agreed
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:A4E9A194-834B-4E97-A5C8-62383BA14AA1@.microsoft.com...
> See inline..
> "Uri Dimant" wrote:
>
> That is why I would say look at EM.. but then for querying QA is the
> better
> option
>
> I only used SQL*Plus, so QA spoils me!!
> I quick Google for "Query Analyzer Alternative" gave
> http://discuss.joelonsoftware.com/d...joel.3.180407.9
> http://gpoulose.home.att.net/
> Toad is a great favourite in the Oracle world so you may want to look at
> that http://www.toadsoft.com/toadsqlserv...d_sqlserver.htm
> At $50 the SQL 2005 developer edition could be a good investment
> especially
> if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as
> well
> as SQL 2005.
> John|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ebVAju0fHHA.1252@.TK2MSFTNGP04.phx.gbl...[vbcol=seagreen]
What does "one user" mean in SQL Developer ? is it possible to test with
multiple connections ? is this an honor system thing where MS expects you
basically not to deploy for production use ?
So everyone uses QA or Management Studio ? I have SQL2005 but have not
really been able to use it much for time reasons; seems to me some of these
third party tools have some useful features like import/export tools (that
are easier/faster to use than DTS), intellisense, .NET code generation,
schema and data diff tools, synchronization, etc. I'm not unhappy with QA
but I do like to keep an eye out for tools that will make me more productive
Liz
especially interested in lower-cost ones but would be interested in hearing
about anything good
Thanks ...Liz
> What good alternatives are there to SQL Server Query Analyzer ?
To upgrade to SQL Server 2005 and have an Object Explorer :-)))
I think you came from Oracle area , so there is no good alternatives SQL
Server Query Analyzer ...
"Liz" <liz@.tiredofspam.com> wrote in message
news:OtQsNnyfHHA.4552@.TK2MSFTNGP04.phx.gbl...
> What good alternatives are there to SQL Server Query Analyzer ? I'm
> especially interested in lower-cost ones but would be interested in
> hearing about anything good
> Thanks ...
>
>|||Hi Liz/Uri
"Uri Dimant" wrote:
> Liz
>
> To upgrade to SQL Server 2005 and have an Object Explorer :-)))
But Object Explorer is also available in QA!!! F8 works in both QA and SQL
Server Management Studio
In SSMS the object explorer does incorporatefunctionality in Enterprise Manager... so maybe Liz should take a look at
that?
> I think you came from Oracle area , so there is no good alternatives SQL
> Server Query Analyzer ...
Did I miss something... Oracle and good tools are not two phrases I would
expect in the same sentence... Oracle and the requirement for third party
tools seems to be the norm!
[vbcol=seagreen]
> "Liz" <liz@.tiredofspam.com> wrote in message
> news:OtQsNnyfHHA.4552@.TK2MSFTNGP04.phx.gbl...
There is no lower cost than free! What features do you require?
[vbcol=seagreen]
John|||Hi John
> But Object Explorer is also available in QA!!! F8 works in both QA and SQL
> Server Management Studio
In SSMS the object explorer does incorporate> functionality in Enterprise Manager... so maybe Liz should take a look at
> that?
Right, but in Object Explorer ( As you press New Query) in SQL Server 2005
you can see all registered servers and as result jobs,mp...
> Did I miss something... Oracle and good tools are not two phrases I would
> expect in the same sentence... Oracle and the requirement for third party
> tools seems to be the norm!
Sorry, what I meant was as an analog of QA in SQL Server , you have to buy
or free download (SQL Developer as I remeber well) a tool to query the
database,
am I right John?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:3F20D1A0-32D4-4489-BF5E-B2F6D62CE117@.microsoft.com...
> Hi Liz/Uri
> "Uri Dimant" wrote:
>
> But Object Explorer is also available in QA!!! F8 works in both QA and SQL
> Server Management Studio
In SSMS the object explorer does incorporate> functionality in Enterprise Manager... so maybe Liz should take a look at
> that?
>
> Did I miss something... Oracle and good tools are not two phrases I would
> expect in the same sentence... Oracle and the requirement for third party
> tools seems to be the norm!
>
> There is no lower cost than free! What features do you require?
>
> John|||See inline..
"Uri Dimant" wrote:
> Hi John
> Right, but in Object Explorer ( As you press New Query) in SQL Server 2005
> you can see all registered servers and as result jobs,mp...
That is why I would say look at EM.. but then for querying QA is the better
option
>
> Sorry, what I meant was as an analog of QA in SQL Server , you have to b
uy
> or free download (SQL Developer as I remeber well) a tool to query the
> database,
> am I right John?
I only used SQL*Plus, so QA spoils me!!
I quick Google for "Query Analyzer Alternative" gave
http://discuss.joelonsoftware.com/d...joel.3.180407.9
http://gpoulose.home.att.net/
Toad is a great favourite in the Oracle world so you may want to look at
that http://www.toadsoft.com/toadsqlserv...d_sqlserver.htm
At $50 the SQL 2005 developer edition could be a good investment especially
if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as well
as SQL 2005.
John|||> At $50 the SQL 2005 developer edition could be a good investment
> especially
> if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as
> well
> as SQL 2005.
Agreed
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:A4E9A194-834B-4E97-A5C8-62383BA14AA1@.microsoft.com...
> See inline..
> "Uri Dimant" wrote:
>
> That is why I would say look at EM.. but then for querying QA is the
> better
> option
>
> I only used SQL*Plus, so QA spoils me!!
> I quick Google for "Query Analyzer Alternative" gave
> http://discuss.joelonsoftware.com/d...joel.3.180407.9
> http://gpoulose.home.att.net/
> Toad is a great favourite in the Oracle world so you may want to look at
> that http://www.toadsoft.com/toadsqlserv...d_sqlserver.htm
> At $50 the SQL 2005 developer edition could be a good investment
> especially
> if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as
> well
> as SQL 2005.
> John|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ebVAju0fHHA.1252@.TK2MSFTNGP04.phx.gbl...[vbcol=seagreen]
What does "one user" mean in SQL Developer ? is it possible to test with
multiple connections ? is this an honor system thing where MS expects you
basically not to deploy for production use ?
So everyone uses QA or Management Studio ? I have SQL2005 but have not
really been able to use it much for time reasons; seems to me some of these
third party tools have some useful features like import/export tools (that
are easier/faster to use than DTS), intellisense, .NET code generation,
schema and data diff tools, synchronization, etc. I'm not unhappy with QA
but I do like to keep an eye out for tools that will make me more productive
Liz
QA Alternatives
What good alternatives are there to SQL Server Query Analyzer ? I'm
especially interested in lower-cost ones but would be interested in hearing
about anything good
Thanks ...
Liz
> What good alternatives are there to SQL Server Query Analyzer ?
To upgrade to SQL Server 2005 and have an Object Explorer :-)))
I think you came from Oracle area , so there is no good alternatives SQL
Server Query Analyzer ...
"Liz" <liz@.tiredofspam.com> wrote in message
news:OtQsNnyfHHA.4552@.TK2MSFTNGP04.phx.gbl...
> What good alternatives are there to SQL Server Query Analyzer ? I'm
> especially interested in lower-cost ones but would be interested in
> hearing about anything good
> Thanks ...
>
>
|||Hi Liz/Uri
"Uri Dimant" wrote:
> Liz
>
> To upgrade to SQL Server 2005 and have an Object Explorer :-)))
But Object Explorer is also available in QA!!! F8 works in both QA and SQL
Server Management Studio In SSMS the object explorer does incorporate
functionality in Enterprise Manager... so maybe Liz should take a look at
that?
> I think you came from Oracle area , so there is no good alternatives SQL
> Server Query Analyzer ...
Did I miss something... Oracle and good tools are not two phrases I would
expect in the same sentence... Oracle and the requirement for third party
tools seems to be the norm!
[vbcol=seagreen]
> "Liz" <liz@.tiredofspam.com> wrote in message
> news:OtQsNnyfHHA.4552@.TK2MSFTNGP04.phx.gbl...
There is no lower cost than free! What features do you require?
[vbcol=seagreen]
John
|||Hi John
> But Object Explorer is also available in QA!!! F8 works in both QA and SQL
> Server Management Studio In SSMS the object explorer does incorporate
> functionality in Enterprise Manager... so maybe Liz should take a look at
> that?
Right, but in Object Explorer ( As you press New Query) in SQL Server 2005
you can see all registered servers and as result jobs,mp...
> Did I miss something... Oracle and good tools are not two phrases I would
> expect in the same sentence... Oracle and the requirement for third party
> tools seems to be the norm!
Sorry, what I meant was as an analog of QA in SQL Server , you have to buy
or free download (SQL Developer as I remeber well) a tool to query the
database,
am I right John?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:3F20D1A0-32D4-4489-BF5E-B2F6D62CE117@.microsoft.com...
> Hi Liz/Uri
> "Uri Dimant" wrote:
> But Object Explorer is also available in QA!!! F8 works in both QA and SQL
> Server Management Studio In SSMS the object explorer does incorporate
> functionality in Enterprise Manager... so maybe Liz should take a look at
> that?
> Did I miss something... Oracle and good tools are not two phrases I would
> expect in the same sentence... Oracle and the requirement for third party
> tools seems to be the norm!
>
> There is no lower cost than free! What features do you require?
>
> John
|||See inline..
"Uri Dimant" wrote:
> Hi John
> Right, but in Object Explorer ( As you press New Query) in SQL Server 2005
> you can see all registered servers and as result jobs,mp...
That is why I would say look at EM.. but then for querying QA is the better
option
>
> Sorry, what I meant was as an analog of QA in SQL Server , you have to buy
> or free download (SQL Developer as I remeber well) a tool to query the
> database,
> am I right John?
I only used SQL*Plus, so QA spoils me!!
I quick Google for "Query Analyzer Alternative" gave
http://discuss.joelonsoftware.com/default.asp?joel.3.180407.9
http://gpoulose.home.att.net/
Toad is a great favourite in the Oracle world so you may want to look at
that http://www.toadsoft.com/toadsqlserver/toad_sqlserver.htm
At $50 the SQL 2005 developer edition could be a good investment especially
if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as well
as SQL 2005.
John
|||> At $50 the SQL 2005 developer edition could be a good investment
> especially
> if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as
> well
> as SQL 2005.
Agreed
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:A4E9A194-834B-4E97-A5C8-62383BA14AA1@.microsoft.com...
> See inline..
> "Uri Dimant" wrote:
>
> That is why I would say look at EM.. but then for querying QA is the
> better
> option
> I only used SQL*Plus, so QA spoils me!!
> I quick Google for "Query Analyzer Alternative" gave
> http://discuss.joelonsoftware.com/default.asp?joel.3.180407.9
> http://gpoulose.home.att.net/
> Toad is a great favourite in the Oracle world so you may want to look at
> that http://www.toadsoft.com/toadsqlserver/toad_sqlserver.htm
> At $50 the SQL 2005 developer edition could be a good investment
> especially
> if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as
> well
> as SQL 2005.
> John
|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ebVAju0fHHA.1252@.TK2MSFTNGP04.phx.gbl...[vbcol=seagreen]
What does "one user" mean in SQL Developer ? is it possible to test with
multiple connections ? is this an honor system thing where MS expects you
basically not to deploy for production use ?
So everyone uses QA or Management Studio ? I have SQL2005 but have not
really been able to use it much for time reasons; seems to me some of these
third party tools have some useful features like import/export tools (that
are easier/faster to use than DTS), intellisense, .NET code generation,
schema and data diff tools, synchronization, etc. I'm not unhappy with QA
but I do like to keep an eye out for tools that will make me more productive
Liz
especially interested in lower-cost ones but would be interested in hearing
about anything good
Thanks ...
Liz
> What good alternatives are there to SQL Server Query Analyzer ?
To upgrade to SQL Server 2005 and have an Object Explorer :-)))
I think you came from Oracle area , so there is no good alternatives SQL
Server Query Analyzer ...
"Liz" <liz@.tiredofspam.com> wrote in message
news:OtQsNnyfHHA.4552@.TK2MSFTNGP04.phx.gbl...
> What good alternatives are there to SQL Server Query Analyzer ? I'm
> especially interested in lower-cost ones but would be interested in
> hearing about anything good
> Thanks ...
>
>
|||Hi Liz/Uri
"Uri Dimant" wrote:
> Liz
>
> To upgrade to SQL Server 2005 and have an Object Explorer :-)))
But Object Explorer is also available in QA!!! F8 works in both QA and SQL
Server Management Studio
In SSMS the object explorer does incorporatefunctionality in Enterprise Manager... so maybe Liz should take a look at
that?
> I think you came from Oracle area , so there is no good alternatives SQL
> Server Query Analyzer ...
Did I miss something... Oracle and good tools are not two phrases I would
expect in the same sentence... Oracle and the requirement for third party
tools seems to be the norm!
[vbcol=seagreen]
> "Liz" <liz@.tiredofspam.com> wrote in message
> news:OtQsNnyfHHA.4552@.TK2MSFTNGP04.phx.gbl...
There is no lower cost than free! What features do you require?
[vbcol=seagreen]
John
|||Hi John
> But Object Explorer is also available in QA!!! F8 works in both QA and SQL
> Server Management Studio
In SSMS the object explorer does incorporate> functionality in Enterprise Manager... so maybe Liz should take a look at
> that?
Right, but in Object Explorer ( As you press New Query) in SQL Server 2005
you can see all registered servers and as result jobs,mp...
> Did I miss something... Oracle and good tools are not two phrases I would
> expect in the same sentence... Oracle and the requirement for third party
> tools seems to be the norm!
Sorry, what I meant was as an analog of QA in SQL Server , you have to buy
or free download (SQL Developer as I remeber well) a tool to query the
database,
am I right John?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:3F20D1A0-32D4-4489-BF5E-B2F6D62CE117@.microsoft.com...
> Hi Liz/Uri
> "Uri Dimant" wrote:
> But Object Explorer is also available in QA!!! F8 works in both QA and SQL
> Server Management Studio
In SSMS the object explorer does incorporate> functionality in Enterprise Manager... so maybe Liz should take a look at
> that?
> Did I miss something... Oracle and good tools are not two phrases I would
> expect in the same sentence... Oracle and the requirement for third party
> tools seems to be the norm!
>
> There is no lower cost than free! What features do you require?
>
> John
|||See inline..
"Uri Dimant" wrote:
> Hi John
> Right, but in Object Explorer ( As you press New Query) in SQL Server 2005
> you can see all registered servers and as result jobs,mp...
That is why I would say look at EM.. but then for querying QA is the better
option
>
> Sorry, what I meant was as an analog of QA in SQL Server , you have to buy
> or free download (SQL Developer as I remeber well) a tool to query the
> database,
> am I right John?
I only used SQL*Plus, so QA spoils me!!
I quick Google for "Query Analyzer Alternative" gave
http://discuss.joelonsoftware.com/default.asp?joel.3.180407.9
http://gpoulose.home.att.net/
Toad is a great favourite in the Oracle world so you may want to look at
that http://www.toadsoft.com/toadsqlserver/toad_sqlserver.htm
At $50 the SQL 2005 developer edition could be a good investment especially
if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as well
as SQL 2005.
John
|||> At $50 the SQL 2005 developer edition could be a good investment
> especially
> if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as
> well
> as SQL 2005.
Agreed
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:A4E9A194-834B-4E97-A5C8-62383BA14AA1@.microsoft.com...
> See inline..
> "Uri Dimant" wrote:
>
> That is why I would say look at EM.. but then for querying QA is the
> better
> option
> I only used SQL*Plus, so QA spoils me!!
> I quick Google for "Query Analyzer Alternative" gave
> http://discuss.joelonsoftware.com/default.asp?joel.3.180407.9
> http://gpoulose.home.att.net/
> Toad is a great favourite in the Oracle world so you may want to look at
> that http://www.toadsoft.com/toadsqlserver/toad_sqlserver.htm
> At $50 the SQL 2005 developer edition could be a good investment
> especially
> if you plan to upgrade. SSMS can be used to manage SQL 2000 systems as
> well
> as SQL 2005.
> John
|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ebVAju0fHHA.1252@.TK2MSFTNGP04.phx.gbl...[vbcol=seagreen]
What does "one user" mean in SQL Developer ? is it possible to test with
multiple connections ? is this an honor system thing where MS expects you
basically not to deploy for production use ?
So everyone uses QA or Management Studio ? I have SQL2005 but have not
really been able to use it much for time reasons; seems to me some of these
third party tools have some useful features like import/export tools (that
are easier/faster to use than DTS), intellisense, .NET code generation,
schema and data diff tools, synchronization, etc. I'm not unhappy with QA
but I do like to keep an eye out for tools that will make me more productive
Liz
Wednesday, March 7, 2012
q; output to a text file
Is it possible to send the output of a query to a text file in a stored
procedure? When I run stored procedure in Query Analyzer I am able to do that
and I am wondering if this is possible in a automated way?Not directly. But indirectly, you can use xp_cmdshell and BCP or OSQL. Note that the file is created
by the database server. If you are on 2005, you can also call an Assembly, if that suits you better.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:33A04A73-5811-4479-A181-67A3F999C770@.microsoft.com...
> Is it possible to send the output of a query to a text file in a stored
> procedure? When I run stored procedure in Query Analyzer I am able to do that
> and I am wondering if this is possible in a automated way?|||In order to output to a file, you would have to use ( xp_cmdshell and OSQL )
OR bcp.
Check [ BCP Utility ] or [OSQL ] in Book Online
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:33A04A73-5811-4479-A181-67A3F999C770@.microsoft.com...
> Is it possible to send the output of a query to a text file in a stored
> procedure? When I run stored procedure in Query Analyzer I am able to do
> that
> and I am wondering if this is possible in a automated way?
procedure? When I run stored procedure in Query Analyzer I am able to do that
and I am wondering if this is possible in a automated way?Not directly. But indirectly, you can use xp_cmdshell and BCP or OSQL. Note that the file is created
by the database server. If you are on 2005, you can also call an Assembly, if that suits you better.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:33A04A73-5811-4479-A181-67A3F999C770@.microsoft.com...
> Is it possible to send the output of a query to a text file in a stored
> procedure? When I run stored procedure in Query Analyzer I am able to do that
> and I am wondering if this is possible in a automated way?|||In order to output to a file, you would have to use ( xp_cmdshell and OSQL )
OR bcp.
Check [ BCP Utility ] or [OSQL ] in Book Online
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:33A04A73-5811-4479-A181-67A3F999C770@.microsoft.com...
> Is it possible to send the output of a query to a text file in a stored
> procedure? When I run stored procedure in Query Analyzer I am able to do
> that
> and I am wondering if this is possible in a automated way?
q; output to a text file
Is it possible to send the output of a query to a text file in a stored
procedure? When I run stored procedure in Query Analyzer I am able to do tha
t
and I am wondering if this is possible in a automated way?Not directly. But indirectly, you can use xp_cmdshell and BCP or OSQL. Note
that the file is created
by the database server. If you are on 2005, you can also call an Assembly, i
f that suits you better.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:33A04A73-5811-4479-A181-67A3F999C770@.microsoft.com...
> Is it possible to send the output of a query to a text file in a stored
> procedure? When I run stored procedure in Query Analyzer I am able to do t
hat
> and I am wondering if this is possible in a automated way?|||In order to output to a file, you would have to use ( xp_cmdshell and OSQL )
OR bcp.
Check [ BCP Utility ] or [OSQL ] in Book Online
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:33A04A73-5811-4479-A181-67A3F999C770@.microsoft.com...
> Is it possible to send the output of a query to a text file in a stored
> procedure? When I run stored procedure in Query Analyzer I am able to do
> that
> and I am wondering if this is possible in a automated way?
procedure? When I run stored procedure in Query Analyzer I am able to do tha
t
and I am wondering if this is possible in a automated way?Not directly. But indirectly, you can use xp_cmdshell and BCP or OSQL. Note
that the file is created
by the database server. If you are on 2005, you can also call an Assembly, i
f that suits you better.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:33A04A73-5811-4479-A181-67A3F999C770@.microsoft.com...
> Is it possible to send the output of a query to a text file in a stored
> procedure? When I run stored procedure in Query Analyzer I am able to do t
hat
> and I am wondering if this is possible in a automated way?|||In order to output to a file, you would have to use ( xp_cmdshell and OSQL )
OR bcp.
Check [ BCP Utility ] or [OSQL ] in Book Online
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:33A04A73-5811-4479-A181-67A3F999C770@.microsoft.com...
> Is it possible to send the output of a query to a text file in a stored
> procedure? When I run stored procedure in Query Analyzer I am able to do
> that
> and I am wondering if this is possible in a automated way?
Saturday, February 25, 2012
Q: where to find download of "SQL Query Analyzer"?
yup, another newbie Q <smile>
Q: where to find download of "SQL Query Analyzer"?
thanks in advance
howard_nyc@.yahoo.com
<<RE-POST>> <<RE-WORDED>>
yup, another newbie Q <smile>
Q: where to find download of "SQL Query Analyzer"?
since I am using MSDE there is no CD available to me... I would prefer
to download the SQL-QA utility
thanks in advance
howard_nyc@.yahoo.com
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||You can't, it's not available separate from SQL Server and you are not
allowed to use it against an MADE database 99% of the time. Please have a
look at one of Aaron Bertrand's excellent Fads:
http://www.aspfaq.com/show.asp?id=2442. It includes a list of 3rd-party
applications that you can use.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Howard Wertenteil" <howard_nyc@.yahoo.com> wrote in message
news:%23qccSwHjEHA.3696@.TK2MSFTNGP15.phx.gbl...
> <<RE-POST>> <<RE-WORDED>>
>
> yup, another newbie Q <smile>
> Q: where to find download of "SQL Query Analyzer"?
> since I am using MSDE there is no CD available to me... I would prefer
> to download the SQL-QA utility
> thanks in advance
> howard_nyc@.yahoo.com
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Uh, MSDE database, not MADE database. :-)
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:%23dMVPjIjEHA.3536@.TK2MSFTNGP10.phx.gbl...
> You can't, it's not available separate from SQL Server and you are not
> allowed to use it against an MADE database 99% of the time. Please have a
> look at one of Aaron Bertrand's excellent Fads:
> http://www.aspfaq.com/show.asp?id=2442. It includes a list of 3rd-party
> applications that you can use.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Howard Wertenteil" <howard_nyc@.yahoo.com> wrote in message
> news:%23qccSwHjEHA.3696@.TK2MSFTNGP15.phx.gbl...
>
|||And FAQ not FAD<g>.
Andrew J. Kelly SQL MVP
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:Op8n50IjEHA.1048@.tk2msftngp13.phx.gbl...
> Uh, MSDE database, not MADE database. :-)
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.[vbcol=seagreen]
> "Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
> news:%23dMVPjIjEHA.3536@.TK2MSFTNGP10.phx.gbl...
a
>
|||Oh man... I'd like to blame an over zealous spell checker, but I don't think
I used one. :-)
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:ORUzSQJjEHA.644@.tk2msftngp13.phx.gbl...
> And FAQ not FAD<g>.
> --
> Andrew J. Kelly SQL MVP
>
> "Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
> news:Op8n50IjEHA.1048@.tk2msftngp13.phx.gbl...
> rights.
> a
>
Q: where to find download of "SQL Query Analyzer"?
thanks in advance
howard_nyc@.yahoo.com
<<RE-POST>> <<RE-WORDED>>
yup, another newbie Q <smile>
Q: where to find download of "SQL Query Analyzer"?
since I am using MSDE there is no CD available to me... I would prefer
to download the SQL-QA utility
thanks in advance
howard_nyc@.yahoo.com
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||You can't, it's not available separate from SQL Server and you are not
allowed to use it against an MADE database 99% of the time. Please have a
look at one of Aaron Bertrand's excellent Fads:
http://www.aspfaq.com/show.asp?id=2442. It includes a list of 3rd-party
applications that you can use.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Howard Wertenteil" <howard_nyc@.yahoo.com> wrote in message
news:%23qccSwHjEHA.3696@.TK2MSFTNGP15.phx.gbl...
> <<RE-POST>> <<RE-WORDED>>
>
> yup, another newbie Q <smile>
> Q: where to find download of "SQL Query Analyzer"?
> since I am using MSDE there is no CD available to me... I would prefer
> to download the SQL-QA utility
> thanks in advance
> howard_nyc@.yahoo.com
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Uh, MSDE database, not MADE database. :-)
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:%23dMVPjIjEHA.3536@.TK2MSFTNGP10.phx.gbl...
> You can't, it's not available separate from SQL Server and you are not
> allowed to use it against an MADE database 99% of the time. Please have a
> look at one of Aaron Bertrand's excellent Fads:
> http://www.aspfaq.com/show.asp?id=2442. It includes a list of 3rd-party
> applications that you can use.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Howard Wertenteil" <howard_nyc@.yahoo.com> wrote in message
> news:%23qccSwHjEHA.3696@.TK2MSFTNGP15.phx.gbl...
>
|||And FAQ not FAD<g>.
Andrew J. Kelly SQL MVP
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:Op8n50IjEHA.1048@.tk2msftngp13.phx.gbl...
> Uh, MSDE database, not MADE database. :-)
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.[vbcol=seagreen]
> "Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
> news:%23dMVPjIjEHA.3536@.TK2MSFTNGP10.phx.gbl...
a
>
|||Oh man... I'd like to blame an over zealous spell checker, but I don't think
I used one. :-)
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:ORUzSQJjEHA.644@.tk2msftngp13.phx.gbl...
> And FAQ not FAD<g>.
> --
> Andrew J. Kelly SQL MVP
>
> "Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
> news:Op8n50IjEHA.1048@.tk2msftngp13.phx.gbl...
> rights.
> a
>
Monday, February 20, 2012
Q: this strange problem
I am having this strange problem, when I run my query in Query Analyzer, I
see the result is ok. But my report based on the same query shows first filed
repeats itself instead of showing right values. What might the problem be?Is this in development? In development the report data is cached (look for a
file with an extension called .data). If you change the paramter it will
requery. If no parameter then you can manually delete this file if you care.
The designer does this so when previewing you are not waiting for the query
to run.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:9E917150-64CD-43FA-8E80-84E716FC6AFE@.microsoft.com...
>I am having this strange problem, when I run my query in Query Analyzer, I
> see the result is ok. But my report based on the same query shows first
> filed
> repeats itself instead of showing right values. What might the problem be?
see the result is ok. But my report based on the same query shows first filed
repeats itself instead of showing right values. What might the problem be?Is this in development? In development the report data is cached (look for a
file with an extension called .data). If you change the paramter it will
requery. If no parameter then you can manually delete this file if you care.
The designer does this so when previewing you are not waiting for the query
to run.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"JIM.H." <JIMH@.discussions.microsoft.com> wrote in message
news:9E917150-64CD-43FA-8E80-84E716FC6AFE@.microsoft.com...
>I am having this strange problem, when I run my query in Query Analyzer, I
> see the result is ok. But my report based on the same query shows first
> filed
> repeats itself instead of showing right values. What might the problem be?
Subscribe to:
Posts (Atom)