Query 6.5 db

I know that 2005 does not support dbs with 6.5 compatibility level. However,
I can see the db and I can run a query against it. If this is possible and
works great, why can't I view/edit the SPs that are on those dbs? It is
basically the same thing as running a query, depending of course on the
difficulty of the SPs. I realize that not all new commands will work on
those older dbs, but still it would be a major help when trying to convert or
rewrite code to new standards before upgrading. Any thoughts on whether or
not I am missing something or if it is not possible no matter how hard I
would like to have it?
Thanks in advance.
cd
Hi Chris
It sounds like you are not using version control software, as this would not
be an issue if you were!
Have you tried sp_helptext?
John
"ChrisD" wrote:

> I know that 2005 does not support dbs with 6.5 compatibility level. However,
> I can see the db and I can run a query against it. If this is possible and
> works great, why can't I view/edit the SPs that are on those dbs? It is
> basically the same thing as running a query, depending of course on the
> difficulty of the SPs. I realize that not all new commands will work on
> those older dbs, but still it would be a major help when trying to convert or
> rewrite code to new standards before upgrading. Any thoughts on whether or
> not I am missing something or if it is not possible no matter how hard I
> would like to have it?
> Thanks in advance.
> cd
|||Let me clarify a little more. We have a program and database which are stuck
currently on level 6.5. Within the SSMS you can see those databases only has
their name and the classification (6.5 compatibility). You cannot drill down
into them. You can right click and choose new query. With this you can use
T-SQL to go and do anything that you can do through Enterprise Manager on the
same db. You cannot however, do anything with the SPs. You cannot even see
them. The question more clearly is whether or not it is possible to view and
edit Stored Procedures despite the limitations?
I am not writing SPs in 6.5, just needing to view and edit without having to
install 2000 tools on subsequent admin machines.
Thanks...cd
"John Bell" wrote:
[vbcol=seagreen]
> Hi Chris
> It sounds like you are not using version control software, as this would not
> be an issue if you were!
> Have you tried sp_helptext?
> John
> "ChrisD" wrote:
|||Chris
You will need to have a separate machine to do this.
John
"ChrisD" wrote:
[vbcol=seagreen]
> Let me clarify a little more. We have a program and database which are stuck
> currently on level 6.5. Within the SSMS you can see those databases only has
> their name and the classification (6.5 compatibility). You cannot drill down
> into them. You can right click and choose new query. With this you can use
> T-SQL to go and do anything that you can do through Enterprise Manager on the
> same db. You cannot however, do anything with the SPs. You cannot even see
> them. The question more clearly is whether or not it is possible to view and
> edit Stored Procedures despite the limitations?
> I am not writing SPs in 6.5, just needing to view and edit without having to
> install 2000 tools on subsequent admin machines.
> Thanks...cd
> "John Bell" wrote:

Query 6.5 db

I know that 2005 does not support dbs with 6.5 compatibility level. However,
I can see the db and I can run a query against it. If this is possible and
works great, why can't I view/edit the SPs that are on those dbs? It is
basically the same thing as running a query, depending of course on the
difficulty of the SPs. I realize that not all new commands will work on
those older dbs, but still it would be a major help when trying to convert or
rewrite code to new standards before upgrading. Any thoughts on whether or
not I am missing something or if it is not possible no matter how hard I
would like to have it?
Thanks in advance.
cdHi Chris
It sounds like you are not using version control software, as this would not
be an issue if you were!
Have you tried sp_helptext?
John
"ChrisD" wrote:
> I know that 2005 does not support dbs with 6.5 compatibility level. However,
> I can see the db and I can run a query against it. If this is possible and
> works great, why can't I view/edit the SPs that are on those dbs? It is
> basically the same thing as running a query, depending of course on the
> difficulty of the SPs. I realize that not all new commands will work on
> those older dbs, but still it would be a major help when trying to convert or
> rewrite code to new standards before upgrading. Any thoughts on whether or
> not I am missing something or if it is not possible no matter how hard I
> would like to have it?
> Thanks in advance.
> cd|||Let me clarify a little more. We have a program and database which are stuck
currently on level 6.5. Within the SSMS you can see those databases only has
their name and the classification (6.5 compatibility). You cannot drill down
into them. You can right click and choose new query. With this you can use
T-SQL to go and do anything that you can do through Enterprise Manager on the
same db. You cannot however, do anything with the SPs. You cannot even see
them. The question more clearly is whether or not it is possible to view and
edit Stored Procedures despite the limitations?
I am not writing SPs in 6.5, just needing to view and edit without having to
install 2000 tools on subsequent admin machines.
Thanks...cd
"John Bell" wrote:
> Hi Chris
> It sounds like you are not using version control software, as this would not
> be an issue if you were!
> Have you tried sp_helptext?
> John
> "ChrisD" wrote:
> > I know that 2005 does not support dbs with 6.5 compatibility level. However,
> > I can see the db and I can run a query against it. If this is possible and
> > works great, why can't I view/edit the SPs that are on those dbs? It is
> > basically the same thing as running a query, depending of course on the
> > difficulty of the SPs. I realize that not all new commands will work on
> > those older dbs, but still it would be a major help when trying to convert or
> > rewrite code to new standards before upgrading. Any thoughts on whether or
> > not I am missing something or if it is not possible no matter how hard I
> > would like to have it?
> >
> > Thanks in advance.
> >
> > cd|||Chris
You will need to have a separate machine to do this.
John
"ChrisD" wrote:
> Let me clarify a little more. We have a program and database which are stuck
> currently on level 6.5. Within the SSMS you can see those databases only has
> their name and the classification (6.5 compatibility). You cannot drill down
> into them. You can right click and choose new query. With this you can use
> T-SQL to go and do anything that you can do through Enterprise Manager on the
> same db. You cannot however, do anything with the SPs. You cannot even see
> them. The question more clearly is whether or not it is possible to view and
> edit Stored Procedures despite the limitations?
> I am not writing SPs in 6.5, just needing to view and edit without having to
> install 2000 tools on subsequent admin machines.
> Thanks...cd
> "John Bell" wrote:
> > Hi Chris
> >
> > It sounds like you are not using version control software, as this would not
> > be an issue if you were!
> >
> > Have you tried sp_helptext?
> >
> > John
> >
> > "ChrisD" wrote:
> >
> > > I know that 2005 does not support dbs with 6.5 compatibility level. However,
> > > I can see the db and I can run a query against it. If this is possible and
> > > works great, why can't I view/edit the SPs that are on those dbs? It is
> > > basically the same thing as running a query, depending of course on the
> > > difficulty of the SPs. I realize that not all new commands will work on
> > > those older dbs, but still it would be a major help when trying to convert or
> > > rewrite code to new standards before upgrading. Any thoughts on whether or
> > > not I am missing something or if it is not possible no matter how hard I
> > > would like to have it?
> > >
> > > Thanks in advance.
> > >
> > > cd

Query 6.5 db

I know that 2005 does not support dbs with 6.5 compatibility level. However
,
I can see the db and I can run a query against it. If this is possible and
works great, why can't I view/edit the SPs that are on those dbs? It is
basically the same thing as running a query, depending of course on the
difficulty of the SPs. I realize that not all new commands will work on
those older dbs, but still it would be a major help when trying to convert o
r
rewrite code to new standards before upgrading. Any thoughts on whether or
not I am missing something or if it is not possible no matter how hard I
would like to have it?
Thanks in advance.
cdHi Chris
It sounds like you are not using version control software, as this would not
be an issue if you were!
Have you tried sp_helptext?
John
"ChrisD" wrote:

> I know that 2005 does not support dbs with 6.5 compatibility level. Howev
er,
> I can see the db and I can run a query against it. If this is possible an
d
> works great, why can't I view/edit the SPs that are on those dbs? It is
> basically the same thing as running a query, depending of course on the
> difficulty of the SPs. I realize that not all new commands will work on
> those older dbs, but still it would be a major help when trying to convert
or
> rewrite code to new standards before upgrading. Any thoughts on whether o
r
> not I am missing something or if it is not possible no matter how hard I
> would like to have it?
> Thanks in advance.
> cd|||Let me clarify a little more. We have a program and database which are stuc
k
currently on level 6.5. Within the SSMS you can see those databases only ha
s
their name and the classification (6.5 compatibility). You cannot drill dow
n
into them. You can right click and choose new query. With this you can use
T-SQL to go and do anything that you can do through Enterprise Manager on th
e
same db. You cannot however, do anything with the SPs. You cannot even see
them. The question more clearly is whether or not it is possible to view an
d
edit Stored Procedures despite the limitations?
I am not writing SPs in 6.5, just needing to view and edit without having to
install 2000 tools on subsequent admin machines.
Thanks...cd
"John Bell" wrote:
[vbcol=seagreen]
> Hi Chris
> It sounds like you are not using version control software, as this would n
ot
> be an issue if you were!
> Have you tried sp_helptext?
> John
> "ChrisD" wrote:
>|||Chris
You will need to have a separate machine to do this.
John
"ChrisD" wrote:
[vbcol=seagreen]
> Let me clarify a little more. We have a program and database which are st
uck
> currently on level 6.5. Within the SSMS you can see those databases only
has
> their name and the classification (6.5 compatibility). You cannot drill d
own
> into them. You can right click and choose new query. With this you can u
se
> T-SQL to go and do anything that you can do through Enterprise Manager on
the
> same db. You cannot however, do anything with the SPs. You cannot even s
ee
> them. The question more clearly is whether or not it is possible to view
and
> edit Stored Procedures despite the limitations?
> I am not writing SPs in 6.5, just needing to view and edit without having
to
> install 2000 tools on subsequent admin machines.
> Thanks...cd
> "John Bell" wrote:
>sql

QUERY

QUERY
select enddate EDT
NEW_TIME(ENDDATE, 'EDT','PDT'
FROM PROJEC
ERROR
Server: Msg 195, Level 15, State 10, Line
'NEW_TIME' is not a recognized function nameRMSANDS (whoever you are)
You are posting many functions that are not defined in SQL-Server. You
are probably converting code from a different RDBMS.
You should really explain what each function is supposed to do. In
addition to that, it wouldn't hurt to take a look at the SQL-Server
Books Online (a download link has been posted by Ray Higdon) to see what
functions SQL-Server does support.
Gert-Jan
RMSANDS wrote:
> QUERY:
> select enddate EDT,
> NEW_TIME(ENDDATE, 'EDT','PDT')
> FROM PROJECT
> ERROR:
> Server: Msg 195, Level 15, State 10, Line 2
> 'NEW_TIME' is not a recognized function name.
--
(Please reply only to the newsgroup)

Query

Using sql 2000
Query
SELECT enddate,last_day(enddate
FROM Project;
Error
Server: Msg 195, Level 15, State 10, Line
'last_day' is not a recognized function nameWhat is last_day? Is enddate the column and you want the max value? If so,
SELECT max(enddate)
FROM Project
HTH
--
Ray Higdon MCSE, MCDBA, CCNA
--
"rmsands" <anonymous@.discussions.microsoft.com> wrote in message
news:43EAC36D-FC2A-4616-B2EE-2F9EE97E915A@.microsoft.com...
> Using sql 2000:
> Query:
> SELECT enddate,last_day(enddate)
> FROM Project;
> Error:
> Server: Msg 195, Level 15, State 10, Line 1
> 'last_day' is not a recognized function name.
>
>|||If your last_day is a user defined function you need to put the owner in
front of it
SELECT enddate,dbo.last_day(enddate)
FROM Project;
--
Dandy Weyn, Belgium
MCSE, MCSA, MCDBA, MCT
http://www.dandyman.net
Check my SQL Server resource pages (currently under construction)
http://www.dandyman.net/sql
"Ray Higdon" <sqlhigdon@.nospam.yahoo.com> wrote in message
news:uaj1z9X#DHA.3816@.tk2msftngp13.phx.gbl...
> What is last_day? Is enddate the column and you want the max value? If so,
> SELECT max(enddate)
> FROM Project
> HTH
> --
> Ray Higdon MCSE, MCDBA, CCNA
> --
> "rmsands" <anonymous@.discussions.microsoft.com> wrote in message
> news:43EAC36D-FC2A-4616-B2EE-2F9EE97E915A@.microsoft.com...
> > Using sql 2000:
> >
> > Query:
> >
> > SELECT enddate,last_day(enddate)
> > FROM Project;
> >
> > Error:
> >
> > Server: Msg 195, Level 15, State 10, Line 1
> > 'last_day' is not a recognized function name.
> >
> >
> >
>|||I WANT TO KNOW WHAT THE LAST DAY OF THE MONTH IS IN THE COLUMN ENDDATE.|||Date of the last day of the month of Enddate:
SELECT DATEADD(MONTH,1,DATEADD(DAY,-DAY(enddate),enddate))
FROM Project
Last day of the month of Enddate:
SELECT DAY(DATEADD(MONTH,1,DATEADD(DAY,-DAY(enddate),enddate)))
FROM Project
--
David Portas
SQL Server MVP
--

Query

Using sql 2000:
Query:
SELECT enddate,last_day(enddate)
FROM Project;
Error:
Server: Msg 195, Level 15, State 10, Line 1
'last_day' is not a recognized function name.What is last_day? Is enddate the column and you want the max value? If so,
SELECT max(enddate)
FROM Project
HTH
Ray Higdon MCSE, MCDBA, CCNA
--
"rmsands" <anonymous@.discussions.microsoft.com> wrote in message
news:43EAC36D-FC2A-4616-B2EE-2F9EE97E915A@.microsoft.com...
> Using sql 2000:
> Query:
> SELECT enddate,last_day(enddate)
> FROM Project;
> Error:
> Server: Msg 195, Level 15, State 10, Line 1
> 'last_day' is not a recognized function name.
>
>|||If your last_day is a user defined function you need to put the owner in
front of it
SELECT enddate,dbo.last_day(enddate)
FROM Project;
--
Dandy Weyn, Belgium
MCSE, MCSA, MCDBA, MCT
http://www.dandyman.net
Check my SQL Server resource pages (currently under construction)
http://www.dandyman.net/sql
"Ray Higdon" <sqlhigdon@.nospam.yahoo.com> wrote in message
news:uaj1z9X#DHA.3816@.tk2msftngp13.phx.gbl...
> What is last_day? Is enddate the column and you want the max value? If so,
> SELECT max(enddate)
> FROM Project
> HTH
> --
> Ray Higdon MCSE, MCDBA, CCNA
> --
> "rmsands" <anonymous@.discussions.microsoft.com> wrote in message
> news:43EAC36D-FC2A-4616-B2EE-2F9EE97E915A@.microsoft.com...
>|||I WANT TO KNOW WHAT THE LAST DAY OF THE MONTH IS IN THE COLUMN ENDDATE.|||Date of the last day of the month of Enddate:
SELECT DATEADD(MONTH,1,DATEADD(DAY,-DAY(enddate),enddate))
FROM Project
Last day of the month of Enddate:
SELECT DAY(DATEADD(MONTH,1,DATEADD(DAY,-DAY(enddate),enddate)))
FROM Project
David Portas
SQL Server MVP
--sql

QUERY

QUERY:
select enddate EDT,
NEW_TIME(ENDDATE, 'EDT','PDT')
FROM PROJECT
ERROR:
Server: Msg 195, Level 15, State 10, Line 2
'NEW_TIME' is not a recognized function name.RMSANDS (whoever you are)
You are posting many functions that are not defined in SQL-Server. You
are probably converting code from a different RDBMS.
You should really explain what each function is supposed to do. In
addition to that, it wouldn't hurt to take a look at the SQL-Server
Books Online (a download link has been posted by Ray Higdon) to see what
functions SQL-Server does support.
Gert-Jan
RMSANDS wrote:
> QUERY:
> select enddate EDT,
> NEW_TIME(ENDDATE, 'EDT','PDT')
> FROM PROJECT
> ERROR:
> Server: Msg 195, Level 15, State 10, Line 2
> 'NEW_TIME' is not a recognized function name.
(Please reply only to the newsgroup)

QA simple question

Hi
I'm a new MS SQL user. When I'm using QA it shows erros in such a way:
"Server: Msg 156, Level 15, State 1, Procedure XX_IMPORT, Line 45
Incorrect syntax near the keyword 'select'."
I wonder how to force it to show correct line. In the example above I
checked line 45 and there is no "select" statement.
I suspect that it ignores lines with comments and blank lines. So debugging
where the error occurs is very difficult.
Best Regards
(and sorry for the simplicity of the question)
Darek T.Dariusz Tomon,
Go to the messages window and double click over the error message. QA will
take you directly to the line where the error is.
AMB
"Dariusz Tomon" wrote:
> Hi
> I'm a new MS SQL user. When I'm using QA it shows erros in such a way:
> "Server: Msg 156, Level 15, State 1, Procedure XX_IMPORT, Line 45
> Incorrect syntax near the keyword 'select'."
> I wonder how to force it to show correct line. In the example above I
> checked line 45 and there is no "select" statement.
> I suspect that it ignores lines with comments and blank lines. So debugging
> where the error occurs is very difficult.
> Best Regards
> (and sorry for the simplicity of the question)
> Darek T.
>
>|||Hi Darek
You can double-click on the error message, and QA will take you to the line
in the Query Window where the error is.
--
HTH
Kalen Delaney, SQL Server MVP
"Dariusz Tomon" <d.tomon@.mazars.pl> wrote in message
news:esH%23a97jGHA.4884@.TK2MSFTNGP03.phx.gbl...
> Hi
> I'm a new MS SQL user. When I'm using QA it shows erros in such a way:
> "Server: Msg 156, Level 15, State 1, Procedure XX_IMPORT, Line 45
> Incorrect syntax near the keyword 'select'."
> I wonder how to force it to show correct line. In the example above I
> checked line 45 and there is no "select" statement.
> I suspect that it ignores lines with comments and blank lines. So
> debugging where the error occurs is very difficult.
> Best Regards
> (and sorry for the simplicity of the question)
> Darek T.
>
>|||"Alejandro Mesa" <AlejandroMesa@.discussions.microsoft.com> wrote in message
news:95A3E7C1-AAAA-46B6-BEAC-74AE111023E4@.microsoft.com...
> Dariusz Tomon,
> Go to the messages window and double click over the error message. QA will
> take you directly to the line where the error is.
>
> AMB
Thank you - I did not know that it's so simple :)
>
> "Dariusz Tomon" wrote:
>> Hi
>> I'm a new MS SQL user. When I'm using QA it shows erros in such a way:
>> "Server: Msg 156, Level 15, State 1, Procedure XX_IMPORT, Line 45
>> Incorrect syntax near the keyword 'select'."
>> I wonder how to force it to show correct line. In the example above I
>> checked line 45 and there is no "select" statement.
>> I suspect that it ignores lines with comments and blank lines. So
>> debugging
>> where the error occurs is very difficult.
>> Best Regards
>> (and sorry for the simplicity of the question)
>> Darek T.
>>
>>|||"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:umPIQL8jGHA.1640@.TK2MSFTNGP02.phx.gbl...
> Hi Darek
> You can double-click on the error message, and QA will take you to the
line
> in the Query Window where the error is.
Dang, in all these years, I never realized that.
Thanks.
> --
> HTH
> Kalen Delaney, SQL Server MVP
>
> "Dariusz Tomon" <d.tomon@.mazars.pl> wrote in message
> news:esH%23a97jGHA.4884@.TK2MSFTNGP03.phx.gbl...
> > Hi
> >
> > I'm a new MS SQL user. When I'm using QA it shows erros in such a way:
> >
> > "Server: Msg 156, Level 15, State 1, Procedure XX_IMPORT, Line 45
> > Incorrect syntax near the keyword 'select'."
> >
> > I wonder how to force it to show correct line. In the example above I
> > checked line 45 and there is no "select" statement.
> > I suspect that it ignores lines with comments and blank lines. So
> > debugging where the error occurs is very difficult.
> >
> > Best Regards
> > (and sorry for the simplicity of the question)
> >
> > Darek T.
> >
> >
> >
>

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?
>

QA Debugger

I need help resolving a problem our developers are having with Query Analyze
r
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 Analyz
er
>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 connec
t 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 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?
>