The following query ERRORs out with this >>
Server: Msg 170, Level 15, State 1, Line 14
Line 14: Incorrect syntax near '@.DBname'.
What can I do to get it to accept the cursor name to change DBs
SET NOCOUNT ON
DECLARE @.DBname varchar(11)
declare db_cursor cursor for
select master.dbo.sysdatabases.name from master.dbo.sysdatabases
order by name
open DB_Cursor
fetch next from DB_Cursor
into @.DBname
WHILE @.@.FETCH_STATUS = 0
BEGIN
use @.DBname
select 'Owner' = user_name(uid), 'Table' = name, 'Date' = crdate
from sysobjects
where user_name(uid) !='DBO'
order by uid, name
fetch next from DB_Cursor
into @.DBname
END
CLOSE db_cursor
DEALLOCATE db_cursor
Thanks.Try this...
SET NOCOUNT ON
DECLARE @.DBname varchar(11)
declare db_cursor cursor for
select master.dbo.sysdatabases.name from master.dbo.sysdatabases
order by name
open DB_Cursor
fetch next from DB_Cursor
into @.DBname
WHILE @.@.FETCH_STATUS = 0
BEGIN
declare @.sql varchar(500)
Set @.sql = 'use ' + @.DBname +'
select ''Owner'' = user_name(uid), ''Table'' = name, ''Date'' = crdate
from sysobjects
where user_name(uid) !=''DBO''
order by uid, name'
Exec (@.sql)
fetch next from DB_Cursor
into @.DBname
END
CLOSE db_cursor
DEALLOCATE db_cursor|||You can't say USE @.dbName because USE can't take a variable.
The following is undocumented and unsupported, so use at your own risk and
not in production code, but should work fine for occasional ad hoc usage:
EXEC sp_msForEachDB 'SELECT [Owner] = user_name(uid), [Table] = name
, [Date]
= crdate
FROM ?.dbo.sysobjects
WHERE user_name(uid) != ''dbo''
ORDER BY uid, name'
You can do it in a more structured way using your own cursor instead of the
one in sp_msForEachDB, if this is a requirement, please post back.
"WANNABE" <breichenbach AT istate DOT com> wrote in message
news:eOL7zkF$GHA.4316@.TK2MSFTNGP03.phx.gbl...
> The following query ERRORs out with this >>
> Server: Msg 170, Level 15, State 1, Line 14
> Line 14: Incorrect syntax near '@.DBname'.
> What can I do to get it to accept the cursor name to change DBs
> SET NOCOUNT ON
> DECLARE @.DBname varchar(11)
> declare db_cursor cursor for
> select master.dbo.sysdatabases.name from master.dbo.sysdatabases
> order by name
> open DB_Cursor
> fetch next from DB_Cursor
> into @.DBname
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> use @.DBname
> select 'Owner' = user_name(uid), 'Table' = name, 'Date' = crdate
> from sysobjects
> where user_name(uid) !='DBO'
> order by uid, name
> fetch next from DB_Cursor
> into @.DBname
> END
> CLOSE db_cursor
> DEALLOCATE db_cursor
> Thanks.
>|||Thanks Barry that looks great, but when I apply your changes I get this
error >>
Server: Msg 207, Level 16, State 3, Line 2
Invalid column name 'DBO'.
and the error is displayed once for every DB on that server.
===================================
"Barry" <barry.oconnor@.manx.net> wrote in message
news:1162237261.528489.238930@.b28g2000cwb.googlegroups.com...
> Try this...
>
> SET NOCOUNT ON
> DECLARE @.DBname varchar(11)
> declare db_cursor cursor for
> select master.dbo.sysdatabases.name from master.dbo.sysdatabases
> order by name
> open DB_Cursor
> fetch next from DB_Cursor
> into @.DBname
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> declare @.sql varchar(500)
> Set @.sql = 'use ' + @.DBname +'
> select ''Owner'' = user_name(uid), ''Table'' = name, ''Date'' = crdate
> from sysobjects
> where user_name(uid) !=''DBO''
> order by uid, name'
> Exec (@.sql)
> fetch next from DB_Cursor
> into @.DBname
> END
> CLOSE db_cursor
> DEALLOCATE db_cursor
>|||I just figured out tit to be a double quote issue, and I think I can find a
fix... Thanks
===================================
"WANNABE" <breichenbach AT istate DOT com> wrote in message
news:%23UFjjAG$GHA.3860@.TK2MSFTNGP02.phx.gbl...
> Thanks Barry that looks great, but when I apply your changes I get this
> error >>
> Server: Msg 207, Level 16, State 3, Line 2
> Invalid column name 'DBO'.
> and the error is displayed once for every DB on that server.
> ===================================
> "Barry" <barry.oconnor@.manx.net> wrote in message
> news:1162237261.528489.238930@.b28g2000cwb.googlegroups.com...
>
Showing posts with label errors. Show all posts
Showing posts with label errors. Show all posts
Sunday, March 25, 2012
cursor How to >> use @dbname
The following query ERRORs out with this >>
Server: Msg 170, Level 15, State 1, Line 14
Line 14: Incorrect syntax near '@.DBname'.
What can I do to get it to accept the cursor name to change DBs
SET NOCOUNT ON
DECLARE @.DBname varchar(11)
declare db_cursor cursor for
select master.dbo.sysdatabases.name from master.dbo.sysdatabases
order by name
open DB_Cursor
fetch next from DB_Cursor
into @.DBname
WHILE @.@.FETCH_STATUS = 0
BEGIN
use @.DBname
select 'Owner' = user_name(uid), 'Table' = name, 'Date' = crdate
from sysobjects
where user_name(uid) !='DBO'
order by uid, name
fetch next from DB_Cursor
into @.DBname
END
CLOSE db_cursor
DEALLOCATE db_cursor
Thanks.Try this...
SET NOCOUNT ON
DECLARE @.DBname varchar(11)
declare db_cursor cursor for
select master.dbo.sysdatabases.name from master.dbo.sysdatabases
order by name
open DB_Cursor
fetch next from DB_Cursor
into @.DBname
WHILE @.@.FETCH_STATUS = 0
BEGIN
declare @.sql varchar(500)
Set @.sql = 'use ' + @.DBname +'
select ''Owner'' = user_name(uid), ''Table'' = name, ''Date'' = crdate
from sysobjects
where user_name(uid) !=''DBO''
order by uid, name'
Exec (@.sql)
fetch next from DB_Cursor
into @.DBname
END
CLOSE db_cursor
DEALLOCATE db_cursor|||You can't say USE @.dbName because USE can't take a variable.
The following is undocumented and unsupported, so use at your own risk and
not in production code, but should work fine for occasional ad hoc usage:
EXEC sp_msForEachDB 'SELECT [Owner] = user_name(uid), [Table] = name, [Date]
= crdate
FROM ?.dbo.sysobjects
WHERE user_name(uid) != ''dbo''
ORDER BY uid, name'
You can do it in a more structured way using your own cursor instead of the
one in sp_msForEachDB, if this is a requirement, please post back.
"WANNABE" <breichenbach AT istate DOT com> wrote in message
news:eOL7zkF$GHA.4316@.TK2MSFTNGP03.phx.gbl...
> The following query ERRORs out with this >>
> Server: Msg 170, Level 15, State 1, Line 14
> Line 14: Incorrect syntax near '@.DBname'.
> What can I do to get it to accept the cursor name to change DBs
> SET NOCOUNT ON
> DECLARE @.DBname varchar(11)
> declare db_cursor cursor for
> select master.dbo.sysdatabases.name from master.dbo.sysdatabases
> order by name
> open DB_Cursor
> fetch next from DB_Cursor
> into @.DBname
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> use @.DBname
> select 'Owner' = user_name(uid), 'Table' = name, 'Date' = crdate
> from sysobjects
> where user_name(uid) !='DBO'
> order by uid, name
> fetch next from DB_Cursor
> into @.DBname
> END
> CLOSE db_cursor
> DEALLOCATE db_cursor
> Thanks.
>|||Thanks Barry that looks great, but when I apply your changes I get this
error >>
Server: Msg 207, Level 16, State 3, Line 2
Invalid column name 'DBO'.
and the error is displayed once for every DB on that server.
==================================="Barry" <barry.oconnor@.manx.net> wrote in message
news:1162237261.528489.238930@.b28g2000cwb.googlegroups.com...
> Try this...
>
> SET NOCOUNT ON
> DECLARE @.DBname varchar(11)
> declare db_cursor cursor for
> select master.dbo.sysdatabases.name from master.dbo.sysdatabases
> order by name
> open DB_Cursor
> fetch next from DB_Cursor
> into @.DBname
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> declare @.sql varchar(500)
> Set @.sql = 'use ' + @.DBname +'
> select ''Owner'' = user_name(uid), ''Table'' = name, ''Date'' = crdate
> from sysobjects
> where user_name(uid) !=''DBO''
> order by uid, name'
> Exec (@.sql)
> fetch next from DB_Cursor
> into @.DBname
> END
> CLOSE db_cursor
> DEALLOCATE db_cursor
>|||I just figured out tit to be a double quote issue, and I think I can find a
fix... Thanks
==================================="WANNABE" <breichenbach AT istate DOT com> wrote in message
news:%23UFjjAG$GHA.3860@.TK2MSFTNGP02.phx.gbl...
> Thanks Barry that looks great, but when I apply your changes I get this
> error >>
> Server: Msg 207, Level 16, State 3, Line 2
> Invalid column name 'DBO'.
> and the error is displayed once for every DB on that server.
> ===================================> "Barry" <barry.oconnor@.manx.net> wrote in message
> news:1162237261.528489.238930@.b28g2000cwb.googlegroups.com...
>> Try this...
>>
>> SET NOCOUNT ON
>> DECLARE @.DBname varchar(11)
>> declare db_cursor cursor for
>> select master.dbo.sysdatabases.name from master.dbo.sysdatabases
>> order by name
>> open DB_Cursor
>> fetch next from DB_Cursor
>> into @.DBname
>> WHILE @.@.FETCH_STATUS = 0
>> BEGIN
>> declare @.sql varchar(500)
>> Set @.sql = 'use ' + @.DBname +'
>> select ''Owner'' = user_name(uid), ''Table'' = name, ''Date'' = crdate
>> from sysobjects
>> where user_name(uid) !=''DBO''
>> order by uid, name'
>> Exec (@.sql)
>> fetch next from DB_Cursor
>> into @.DBname
>> END
>> CLOSE db_cursor
>> DEALLOCATE db_cursor
>
Server: Msg 170, Level 15, State 1, Line 14
Line 14: Incorrect syntax near '@.DBname'.
What can I do to get it to accept the cursor name to change DBs
SET NOCOUNT ON
DECLARE @.DBname varchar(11)
declare db_cursor cursor for
select master.dbo.sysdatabases.name from master.dbo.sysdatabases
order by name
open DB_Cursor
fetch next from DB_Cursor
into @.DBname
WHILE @.@.FETCH_STATUS = 0
BEGIN
use @.DBname
select 'Owner' = user_name(uid), 'Table' = name, 'Date' = crdate
from sysobjects
where user_name(uid) !='DBO'
order by uid, name
fetch next from DB_Cursor
into @.DBname
END
CLOSE db_cursor
DEALLOCATE db_cursor
Thanks.Try this...
SET NOCOUNT ON
DECLARE @.DBname varchar(11)
declare db_cursor cursor for
select master.dbo.sysdatabases.name from master.dbo.sysdatabases
order by name
open DB_Cursor
fetch next from DB_Cursor
into @.DBname
WHILE @.@.FETCH_STATUS = 0
BEGIN
declare @.sql varchar(500)
Set @.sql = 'use ' + @.DBname +'
select ''Owner'' = user_name(uid), ''Table'' = name, ''Date'' = crdate
from sysobjects
where user_name(uid) !=''DBO''
order by uid, name'
Exec (@.sql)
fetch next from DB_Cursor
into @.DBname
END
CLOSE db_cursor
DEALLOCATE db_cursor|||You can't say USE @.dbName because USE can't take a variable.
The following is undocumented and unsupported, so use at your own risk and
not in production code, but should work fine for occasional ad hoc usage:
EXEC sp_msForEachDB 'SELECT [Owner] = user_name(uid), [Table] = name, [Date]
= crdate
FROM ?.dbo.sysobjects
WHERE user_name(uid) != ''dbo''
ORDER BY uid, name'
You can do it in a more structured way using your own cursor instead of the
one in sp_msForEachDB, if this is a requirement, please post back.
"WANNABE" <breichenbach AT istate DOT com> wrote in message
news:eOL7zkF$GHA.4316@.TK2MSFTNGP03.phx.gbl...
> The following query ERRORs out with this >>
> Server: Msg 170, Level 15, State 1, Line 14
> Line 14: Incorrect syntax near '@.DBname'.
> What can I do to get it to accept the cursor name to change DBs
> SET NOCOUNT ON
> DECLARE @.DBname varchar(11)
> declare db_cursor cursor for
> select master.dbo.sysdatabases.name from master.dbo.sysdatabases
> order by name
> open DB_Cursor
> fetch next from DB_Cursor
> into @.DBname
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> use @.DBname
> select 'Owner' = user_name(uid), 'Table' = name, 'Date' = crdate
> from sysobjects
> where user_name(uid) !='DBO'
> order by uid, name
> fetch next from DB_Cursor
> into @.DBname
> END
> CLOSE db_cursor
> DEALLOCATE db_cursor
> Thanks.
>|||Thanks Barry that looks great, but when I apply your changes I get this
error >>
Server: Msg 207, Level 16, State 3, Line 2
Invalid column name 'DBO'.
and the error is displayed once for every DB on that server.
==================================="Barry" <barry.oconnor@.manx.net> wrote in message
news:1162237261.528489.238930@.b28g2000cwb.googlegroups.com...
> Try this...
>
> SET NOCOUNT ON
> DECLARE @.DBname varchar(11)
> declare db_cursor cursor for
> select master.dbo.sysdatabases.name from master.dbo.sysdatabases
> order by name
> open DB_Cursor
> fetch next from DB_Cursor
> into @.DBname
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> declare @.sql varchar(500)
> Set @.sql = 'use ' + @.DBname +'
> select ''Owner'' = user_name(uid), ''Table'' = name, ''Date'' = crdate
> from sysobjects
> where user_name(uid) !=''DBO''
> order by uid, name'
> Exec (@.sql)
> fetch next from DB_Cursor
> into @.DBname
> END
> CLOSE db_cursor
> DEALLOCATE db_cursor
>|||I just figured out tit to be a double quote issue, and I think I can find a
fix... Thanks
==================================="WANNABE" <breichenbach AT istate DOT com> wrote in message
news:%23UFjjAG$GHA.3860@.TK2MSFTNGP02.phx.gbl...
> Thanks Barry that looks great, but when I apply your changes I get this
> error >>
> Server: Msg 207, Level 16, State 3, Line 2
> Invalid column name 'DBO'.
> and the error is displayed once for every DB on that server.
> ===================================> "Barry" <barry.oconnor@.manx.net> wrote in message
> news:1162237261.528489.238930@.b28g2000cwb.googlegroups.com...
>> Try this...
>>
>> SET NOCOUNT ON
>> DECLARE @.DBname varchar(11)
>> declare db_cursor cursor for
>> select master.dbo.sysdatabases.name from master.dbo.sysdatabases
>> order by name
>> open DB_Cursor
>> fetch next from DB_Cursor
>> into @.DBname
>> WHILE @.@.FETCH_STATUS = 0
>> BEGIN
>> declare @.sql varchar(500)
>> Set @.sql = 'use ' + @.DBname +'
>> select ''Owner'' = user_name(uid), ''Table'' = name, ''Date'' = crdate
>> from sysobjects
>> where user_name(uid) !=''DBO''
>> order by uid, name'
>> Exec (@.sql)
>> fetch next from DB_Cursor
>> into @.DBname
>> END
>> CLOSE db_cursor
>> DEALLOCATE db_cursor
>
Thursday, March 22, 2012
Current_Date function
Has any one been able to use the CURRENT_DATE function?
I'm in the middle of a very simple SQL query, and I keep
getting errors when I try and use CURRENT_DATE. Here is
my SQL QUERY:
Select * from Cal where ONDATE >= (CURRENT_DATE - 3)
Sounds simple enough but it always returns "Syntax Error
near 'CURRENT_DATE' I can't see any syntax error in the
above statement.
I'm running SQL server 2000
Use either GETDATE() or CURRENT_TIMESTAMP and convert if you just want the
date part.
You need to escape calls to CURRENT_DATE e.g
select {fn CURRENT_DATE()}
Note this returns a varchar so you need to convert to datetime
select * from orders where OrderDate < (cast({fn CURRENT_DATE()} as
datetime)-3)
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Pierre" <pmitham@.pbviews.com> wrote in message
news:085001c48479$1871ffd0$a301280a@.phx.gbl...
> Has any one been able to use the CURRENT_DATE function?
> I'm in the middle of a very simple SQL query, and I keep
> getting errors when I try and use CURRENT_DATE. Here is
> my SQL QUERY:
> Select * from Cal where ONDATE >= (CURRENT_DATE - 3)
> Sounds simple enough but it always returns "Syntax Error
> near 'CURRENT_DATE' I can't see any syntax error in the
> above statement.
> I'm running SQL server 2000
|||Wonderfuil. But that's a bit different from what MS says
the Syntax is ;-) figures.
>--Original Message--
>Use either GETDATE() or CURRENT_TIMESTAMP and convert if
you just want the
>date part.
>You need to escape calls to CURRENT_DATE e.g
>select {fn CURRENT_DATE()}
>Note this returns a varchar so you need to convert to
datetime
>select * from orders where OrderDate < (cast({fn
CURRENT_DATE()} as[vbcol=seagreen]
>datetime)-3)
>--
>HTH
>Jasper Smith (SQL Server MVP)
>http://www.sqldbatips.com
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>"Pierre" <pmitham@.pbviews.com> wrote in message
>news:085001c48479$1871ffd0$a301280a@.phx.gbl...
keep
>
>.
>
|||If you can post to where MS documents the syntax you tried, we can feedback to them...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Pierre mitham" <pmitham@.pbviews.com> wrote in message
news:7e1101c48495$be2ab540$a401280a@.phx.gbl...[vbcol=seagreen]
> Wonderfuil. But that's a bit different from what MS says
> the Syntax is ;-) figures.
>
> you just want the
> datetime
> CURRENT_DATE()} as
> keep
I'm in the middle of a very simple SQL query, and I keep
getting errors when I try and use CURRENT_DATE. Here is
my SQL QUERY:
Select * from Cal where ONDATE >= (CURRENT_DATE - 3)
Sounds simple enough but it always returns "Syntax Error
near 'CURRENT_DATE' I can't see any syntax error in the
above statement.
I'm running SQL server 2000
Use either GETDATE() or CURRENT_TIMESTAMP and convert if you just want the
date part.
You need to escape calls to CURRENT_DATE e.g
select {fn CURRENT_DATE()}
Note this returns a varchar so you need to convert to datetime
select * from orders where OrderDate < (cast({fn CURRENT_DATE()} as
datetime)-3)
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Pierre" <pmitham@.pbviews.com> wrote in message
news:085001c48479$1871ffd0$a301280a@.phx.gbl...
> Has any one been able to use the CURRENT_DATE function?
> I'm in the middle of a very simple SQL query, and I keep
> getting errors when I try and use CURRENT_DATE. Here is
> my SQL QUERY:
> Select * from Cal where ONDATE >= (CURRENT_DATE - 3)
> Sounds simple enough but it always returns "Syntax Error
> near 'CURRENT_DATE' I can't see any syntax error in the
> above statement.
> I'm running SQL server 2000
|||Wonderfuil. But that's a bit different from what MS says
the Syntax is ;-) figures.
>--Original Message--
>Use either GETDATE() or CURRENT_TIMESTAMP and convert if
you just want the
>date part.
>You need to escape calls to CURRENT_DATE e.g
>select {fn CURRENT_DATE()}
>Note this returns a varchar so you need to convert to
datetime
>select * from orders where OrderDate < (cast({fn
CURRENT_DATE()} as[vbcol=seagreen]
>datetime)-3)
>--
>HTH
>Jasper Smith (SQL Server MVP)
>http://www.sqldbatips.com
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>"Pierre" <pmitham@.pbviews.com> wrote in message
>news:085001c48479$1871ffd0$a301280a@.phx.gbl...
keep
>
>.
>
|||If you can post to where MS documents the syntax you tried, we can feedback to them...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Pierre mitham" <pmitham@.pbviews.com> wrote in message
news:7e1101c48495$be2ab540$a401280a@.phx.gbl...[vbcol=seagreen]
> Wonderfuil. But that's a bit different from what MS says
> the Syntax is ;-) figures.
>
> you just want the
> datetime
> CURRENT_DATE()} as
> keep
Sunday, March 11, 2012
Cumulative update packages for Post-SP2 changes in SQL2005
Hi !
I see there are quite a few cumulated post-SP2 packages that have been
built, some of which fix errors that I have been experiencing in my
environment.
I have doubts if that's good practice to apply those cumulative packages to
my life production servers... is it ?
Any idea on how long we have to wait until SP3 will be built ?
Palli
Hi
I can't say if/when SP3 is due, but most of the post SP2 hotfixes require
you to contact PSS for them. In general hotfixes are cumulative so you only
need to apply the last one.
John
"Pall Bjornsson" <palli@.kvos.is> wrote in message
news:etaKos7cIHA.4936@.TK2MSFTNGP03.phx.gbl...
> Hi !
> I see there are quite a few cumulated post-SP2 packages that have been
> built, some of which fix errors that I have been experiencing in my
> environment.
> I have doubts if that's good practice to apply those cumulative packages
> to my life production servers... is it ?
> Any idea on how long we have to wait until SP3 will be built ?
> Palli
>
|||>
> I can't say if/when SP3 is due, but most of the post SP2 hotfixes require
> you to contact PSS for them. In general hotfixes are cumulative so you
> only need to apply the last one.
>
I did contact MS about the cumulative packages, and I did receive one from
them for 1 or 2 weeks ago, I think it's number 5.
1) I haven't had the guts yet to apply them, so the question is, should I
apply them to my production servers ?
2) Will I have to uninstall them before applying SP3 ?
Palli
|||Hi
You should apply any service pack or hotfixes to a test machine and make
sure they work as expected and don't break anything else, once satisfied you
can then apply them to a production system, but make sure that you have a
rollback process and recovery procedures in place to copy with any
eventuality.
You should be able to apply any new hotfix/service pack ontop of the one you
have providing the version number is higher.
John
"Pall Bjornsson" <palli@.kvos.is> wrote in message
news:eQEm4A8cIHA.2268@.TK2MSFTNGP02.phx.gbl...
> I did contact MS about the cumulative packages, and I did receive one from
> them for 1 or 2 weeks ago, I think it's number 5.
> 1) I haven't had the guts yet to apply them, so the question is, should I
> apply them to my production servers ?
> 2) Will I have to uninstall them before applying SP3 ?
> Palli
>
|||Palli,
If you are registered on Connect then vote here:-
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=326575
We are running CU2 on one production system and are looking at upgrading to
either CU5 or CU6 but only after fully testing on Development and Acceptance
servers first. On one server we get mini dumps associated with a fix
included in CU4.
Chris
"Pall Bjornsson" <palli@.kvos.is> wrote in message
news:eQEm4A8cIHA.2268@.TK2MSFTNGP02.phx.gbl...
> I did contact MS about the cumulative packages, and I did receive one from
> them for 1 or 2 weeks ago, I think it's number 5.
> 1) I haven't had the guts yet to apply them, so the question is, should I
> apply them to my production servers ?
> 2) Will I have to uninstall them before applying SP3 ?
> Palli
>
I see there are quite a few cumulated post-SP2 packages that have been
built, some of which fix errors that I have been experiencing in my
environment.
I have doubts if that's good practice to apply those cumulative packages to
my life production servers... is it ?
Any idea on how long we have to wait until SP3 will be built ?
Palli
Hi
I can't say if/when SP3 is due, but most of the post SP2 hotfixes require
you to contact PSS for them. In general hotfixes are cumulative so you only
need to apply the last one.
John
"Pall Bjornsson" <palli@.kvos.is> wrote in message
news:etaKos7cIHA.4936@.TK2MSFTNGP03.phx.gbl...
> Hi !
> I see there are quite a few cumulated post-SP2 packages that have been
> built, some of which fix errors that I have been experiencing in my
> environment.
> I have doubts if that's good practice to apply those cumulative packages
> to my life production servers... is it ?
> Any idea on how long we have to wait until SP3 will be built ?
> Palli
>
|||>
> I can't say if/when SP3 is due, but most of the post SP2 hotfixes require
> you to contact PSS for them. In general hotfixes are cumulative so you
> only need to apply the last one.
>
I did contact MS about the cumulative packages, and I did receive one from
them for 1 or 2 weeks ago, I think it's number 5.
1) I haven't had the guts yet to apply them, so the question is, should I
apply them to my production servers ?
2) Will I have to uninstall them before applying SP3 ?
Palli
|||Hi
You should apply any service pack or hotfixes to a test machine and make
sure they work as expected and don't break anything else, once satisfied you
can then apply them to a production system, but make sure that you have a
rollback process and recovery procedures in place to copy with any
eventuality.
You should be able to apply any new hotfix/service pack ontop of the one you
have providing the version number is higher.
John
"Pall Bjornsson" <palli@.kvos.is> wrote in message
news:eQEm4A8cIHA.2268@.TK2MSFTNGP02.phx.gbl...
> I did contact MS about the cumulative packages, and I did receive one from
> them for 1 or 2 weeks ago, I think it's number 5.
> 1) I haven't had the guts yet to apply them, so the question is, should I
> apply them to my production servers ?
> 2) Will I have to uninstall them before applying SP3 ?
> Palli
>
|||Palli,
If you are registered on Connect then vote here:-
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=326575
We are running CU2 on one production system and are looking at upgrading to
either CU5 or CU6 but only after fully testing on Development and Acceptance
servers first. On one server we get mini dumps associated with a fix
included in CU4.
Chris
"Pall Bjornsson" <palli@.kvos.is> wrote in message
news:eQEm4A8cIHA.2268@.TK2MSFTNGP02.phx.gbl...
> I did contact MS about the cumulative packages, and I did receive one from
> them for 1 or 2 weeks ago, I think it's number 5.
> 1) I haven't had the guts yet to apply them, so the question is, should I
> apply them to my production servers ?
> 2) Will I have to uninstall them before applying SP3 ?
> Palli
>
Cumulative update packages for Post-SP2 changes in SQL2005
Hi !
I see there are quite a few cumulated post-SP2 packages that have been
built, some of which fix errors that I have been experiencing in my
environment.
I have doubts if that's good practice to apply those cumulative packages to
my life production servers... is it ?
Any idea on how long we have to wait until SP3 will be built ?
PalliHi
I can't say if/when SP3 is due, but most of the post SP2 hotfixes require
you to contact PSS for them. In general hotfixes are cumulative so you only
need to apply the last one.
John
"Pall Bjornsson" <palli@.kvos.is> wrote in message
news:etaKos7cIHA.4936@.TK2MSFTNGP03.phx.gbl...
> Hi !
> I see there are quite a few cumulated post-SP2 packages that have been
> built, some of which fix errors that I have been experiencing in my
> environment.
> I have doubts if that's good practice to apply those cumulative packages
> to my life production servers... is it ?
> Any idea on how long we have to wait until SP3 will be built ?
> Palli
>|||>
> I can't say if/when SP3 is due, but most of the post SP2 hotfixes require
> you to contact PSS for them. In general hotfixes are cumulative so you
> only need to apply the last one.
>
I did contact MS about the cumulative packages, and I did receive one from
them for 1 or 2 weeks ago, I think it's number 5.
1) I haven't had the guts yet to apply them, so the question is, should I
apply them to my production servers ?
2) Will I have to uninstall them before applying SP3 ?
Palli|||Hi
You should apply any service pack or hotfixes to a test machine and make
sure they work as expected and don't break anything else, once satisfied you
can then apply them to a production system, but make sure that you have a
rollback process and recovery procedures in place to copy with any
eventuality.
You should be able to apply any new hotfix/service pack ontop of the one you
have providing the version number is higher.
John
"Pall Bjornsson" <palli@.kvos.is> wrote in message
news:eQEm4A8cIHA.2268@.TK2MSFTNGP02.phx.gbl...
> >
>> I can't say if/when SP3 is due, but most of the post SP2 hotfixes require
>> you to contact PSS for them. In general hotfixes are cumulative so you
>> only need to apply the last one.
> I did contact MS about the cumulative packages, and I did receive one from
> them for 1 or 2 weeks ago, I think it's number 5.
> 1) I haven't had the guts yet to apply them, so the question is, should I
> apply them to my production servers ?
> 2) Will I have to uninstall them before applying SP3 ?
> Palli
>|||Palli,
If you are registered on Connect then vote here:-
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=326575
We are running CU2 on one production system and are looking at upgrading to
either CU5 or CU6 but only after fully testing on Development and Acceptance
servers first. On one server we get mini dumps associated with a fix
included in CU4.
Chris
"Pall Bjornsson" <palli@.kvos.is> wrote in message
news:eQEm4A8cIHA.2268@.TK2MSFTNGP02.phx.gbl...
> >
>> I can't say if/when SP3 is due, but most of the post SP2 hotfixes require
>> you to contact PSS for them. In general hotfixes are cumulative so you
>> only need to apply the last one.
> I did contact MS about the cumulative packages, and I did receive one from
> them for 1 or 2 weeks ago, I think it's number 5.
> 1) I haven't had the guts yet to apply them, so the question is, should I
> apply them to my production servers ?
> 2) Will I have to uninstall them before applying SP3 ?
> Palli
>|||On Wed, 20 Feb 2008 12:21:42 -0000, Pall Bjornsson wrote:
>Hi !
>I see there are quite a few cumulated post-SP2 packages that have been
>built, some of which fix errors that I have been experiencing in my
>environment.
>I have doubts if that's good practice to apply those cumulative packages to
>my life production servers... is it ?
>Any idea on how long we have to wait until SP3 will be built ?
Hi Palli,
Read
http://sqlblog.com/blogs/hugo_kornelis/archive/2008/02/01/want-a-service-pack-ask-for-it.aspx
Then make yourself heard at
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=326575
--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
I see there are quite a few cumulated post-SP2 packages that have been
built, some of which fix errors that I have been experiencing in my
environment.
I have doubts if that's good practice to apply those cumulative packages to
my life production servers... is it ?
Any idea on how long we have to wait until SP3 will be built ?
PalliHi
I can't say if/when SP3 is due, but most of the post SP2 hotfixes require
you to contact PSS for them. In general hotfixes are cumulative so you only
need to apply the last one.
John
"Pall Bjornsson" <palli@.kvos.is> wrote in message
news:etaKos7cIHA.4936@.TK2MSFTNGP03.phx.gbl...
> Hi !
> I see there are quite a few cumulated post-SP2 packages that have been
> built, some of which fix errors that I have been experiencing in my
> environment.
> I have doubts if that's good practice to apply those cumulative packages
> to my life production servers... is it ?
> Any idea on how long we have to wait until SP3 will be built ?
> Palli
>|||>
> I can't say if/when SP3 is due, but most of the post SP2 hotfixes require
> you to contact PSS for them. In general hotfixes are cumulative so you
> only need to apply the last one.
>
I did contact MS about the cumulative packages, and I did receive one from
them for 1 or 2 weeks ago, I think it's number 5.
1) I haven't had the guts yet to apply them, so the question is, should I
apply them to my production servers ?
2) Will I have to uninstall them before applying SP3 ?
Palli|||Hi
You should apply any service pack or hotfixes to a test machine and make
sure they work as expected and don't break anything else, once satisfied you
can then apply them to a production system, but make sure that you have a
rollback process and recovery procedures in place to copy with any
eventuality.
You should be able to apply any new hotfix/service pack ontop of the one you
have providing the version number is higher.
John
"Pall Bjornsson" <palli@.kvos.is> wrote in message
news:eQEm4A8cIHA.2268@.TK2MSFTNGP02.phx.gbl...
> >
>> I can't say if/when SP3 is due, but most of the post SP2 hotfixes require
>> you to contact PSS for them. In general hotfixes are cumulative so you
>> only need to apply the last one.
> I did contact MS about the cumulative packages, and I did receive one from
> them for 1 or 2 weeks ago, I think it's number 5.
> 1) I haven't had the guts yet to apply them, so the question is, should I
> apply them to my production servers ?
> 2) Will I have to uninstall them before applying SP3 ?
> Palli
>|||Palli,
If you are registered on Connect then vote here:-
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=326575
We are running CU2 on one production system and are looking at upgrading to
either CU5 or CU6 but only after fully testing on Development and Acceptance
servers first. On one server we get mini dumps associated with a fix
included in CU4.
Chris
"Pall Bjornsson" <palli@.kvos.is> wrote in message
news:eQEm4A8cIHA.2268@.TK2MSFTNGP02.phx.gbl...
> >
>> I can't say if/when SP3 is due, but most of the post SP2 hotfixes require
>> you to contact PSS for them. In general hotfixes are cumulative so you
>> only need to apply the last one.
> I did contact MS about the cumulative packages, and I did receive one from
> them for 1 or 2 weeks ago, I think it's number 5.
> 1) I haven't had the guts yet to apply them, so the question is, should I
> apply them to my production servers ?
> 2) Will I have to uninstall them before applying SP3 ?
> Palli
>|||On Wed, 20 Feb 2008 12:21:42 -0000, Pall Bjornsson wrote:
>Hi !
>I see there are quite a few cumulated post-SP2 packages that have been
>built, some of which fix errors that I have been experiencing in my
>environment.
>I have doubts if that's good practice to apply those cumulative packages to
>my life production servers... is it ?
>Any idea on how long we have to wait until SP3 will be built ?
Hi Palli,
Read
http://sqlblog.com/blogs/hugo_kornelis/archive/2008/02/01/want-a-service-pack-ask-for-it.aspx
Then make yourself heard at
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=326575
--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
Sunday, February 19, 2012
ct_connect errors in xp_cmdshell
I am running a bcp from xp_cmdshell, it was working good
EXEC master.dbo.xp_cmdshell 'bcp DATABASE1..V_TMP_KEYWORDSMMS2 out
c:\Keywords\KEYWORD_00000115_16_12_2004_17_47_27.t xt -c -t~ -SSYN0001
-UUserName -Ppassword '
The server is Microsoft SQL Server 2000 - 8.00.760
Then I installed sybase client in the PC inorder to get replication from
sybase to sql server.
It is giving the following error message.
CTLIB Message: - L6/O8/S5/N3/5/0:
ct_connect(): directory service layer: internal directory control layer
error: Requested server name not found.
Establishing connection failed.
NULL
Any help why is this happenning?
The server, username, password are all correct and I am able to work through
the enterprise manager and query analyser, its gving error only in the
xp_cmdshell and bcp.
After the install, the xp_cmdshell and bcp is not working anymore.
Hi
The Sybase BCP.exe is now being used by your call due to the environment
path settings written by the Sybase setup.
Fully qualify the BCP.exe path in the call and it will work. osql.exe is
also affected in the same way.
Regards
Mike
"Yog" wrote:
> I am running a bcp from xp_cmdshell, it was working good
> EXEC master.dbo.xp_cmdshell 'bcp DATABASE1..V_TMP_KEYWORDSMMS2 out
> c:\Keywords\KEYWORD_00000115_16_12_2004_17_47_27.t xt -c -t~ -SSYN0001
> -UUserName -Ppassword '
> The server is Microsoft SQL Server 2000 - 8.00.760
> Then I installed sybase client in the PC inorder to get replication from
> sybase to sql server.
> It is giving the following error message.
> CTLIB Message: - L6/O8/S5/N3/5/0:
> ct_connect(): directory service layer: internal directory control layer
> error: Requested server name not found.
> Establishing connection failed.
> NULL
> Any help why is this happenning?
> The server, username, password are all correct and I am able to work through
> the enterprise manager and query analyser, its gving error only in the
> xp_cmdshell and bcp.
> After the install, the xp_cmdshell and bcp is not working anymore.
>
>
|||Thank you Mike, that worked.
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> The Sybase BCP.exe is now being used by your call due to the environment
> path settings written by the Sybase setup.
> Fully qualify the BCP.exe path in the call and it will work. osql.exe is
> also affected in the same way.
> Regards
> Mike
> "Yog" wrote:
EXEC master.dbo.xp_cmdshell 'bcp DATABASE1..V_TMP_KEYWORDSMMS2 out
c:\Keywords\KEYWORD_00000115_16_12_2004_17_47_27.t xt -c -t~ -SSYN0001
-UUserName -Ppassword '
The server is Microsoft SQL Server 2000 - 8.00.760
Then I installed sybase client in the PC inorder to get replication from
sybase to sql server.
It is giving the following error message.
CTLIB Message: - L6/O8/S5/N3/5/0:
ct_connect(): directory service layer: internal directory control layer
error: Requested server name not found.
Establishing connection failed.
NULL
Any help why is this happenning?
The server, username, password are all correct and I am able to work through
the enterprise manager and query analyser, its gving error only in the
xp_cmdshell and bcp.
After the install, the xp_cmdshell and bcp is not working anymore.
Hi
The Sybase BCP.exe is now being used by your call due to the environment
path settings written by the Sybase setup.
Fully qualify the BCP.exe path in the call and it will work. osql.exe is
also affected in the same way.
Regards
Mike
"Yog" wrote:
> I am running a bcp from xp_cmdshell, it was working good
> EXEC master.dbo.xp_cmdshell 'bcp DATABASE1..V_TMP_KEYWORDSMMS2 out
> c:\Keywords\KEYWORD_00000115_16_12_2004_17_47_27.t xt -c -t~ -SSYN0001
> -UUserName -Ppassword '
> The server is Microsoft SQL Server 2000 - 8.00.760
> Then I installed sybase client in the PC inorder to get replication from
> sybase to sql server.
> It is giving the following error message.
> CTLIB Message: - L6/O8/S5/N3/5/0:
> ct_connect(): directory service layer: internal directory control layer
> error: Requested server name not found.
> Establishing connection failed.
> NULL
> Any help why is this happenning?
> The server, username, password are all correct and I am able to work through
> the enterprise manager and query analyser, its gving error only in the
> xp_cmdshell and bcp.
> After the install, the xp_cmdshell and bcp is not working anymore.
>
>
|||Thank you Mike, that worked.
"Mike Epprecht (SQL MVP)" wrote:
[vbcol=seagreen]
> Hi
> The Sybase BCP.exe is now being used by your call due to the environment
> path settings written by the Sybase setup.
> Fully qualify the BCP.exe path in the call and it will work. osql.exe is
> also affected in the same way.
> Regards
> Mike
> "Yog" wrote:
ct_connect errors in xp_cmdshell
I am running a bcp from xp_cmdshell, it was working good
EXEC master.dbo.xp_cmdshell 'bcp DATABASE1..V_TMP_KEYWORDSMMS2 out
c:\Keywords\KEYWORD_00000115_16_12_2004_17_47_27.txt -c -t~ -SSYN0001
-UUserName -Ppassword '
The server is Microsoft SQL Server 2000 - 8.00.760
Then I installed sybase client in the PC inorder to get replication from
sybase to sql server.
It is giving the following error message.
CTLIB Message: - L6/O8/S5/N3/5/0:
ct_connect(): directory service layer: internal directory control layer
error: Requested server name not found.
Establishing connection failed.
NULL
Any help why is this happenning?
The server, username, password are all correct and I am able to work through
the enterprise manager and query analyser, its gving error only in the
xp_cmdshell and bcp.
After the install, the xp_cmdshell and bcp is not working anymore.Hi
The Sybase BCP.exe is now being used by your call due to the environment
path settings written by the Sybase setup.
Fully qualify the BCP.exe path in the call and it will work. osql.exe is
also affected in the same way.
Regards
Mike
"Yog" wrote:
> I am running a bcp from xp_cmdshell, it was working good
> EXEC master.dbo.xp_cmdshell 'bcp DATABASE1..V_TMP_KEYWORDSMMS2 out
> c:\Keywords\KEYWORD_00000115_16_12_2004_17_47_27.txt -c -t~ -SSYN0001
> -UUserName -Ppassword '
> The server is Microsoft SQL Server 2000 - 8.00.760
> Then I installed sybase client in the PC inorder to get replication from
> sybase to sql server.
> It is giving the following error message.
> CTLIB Message: - L6/O8/S5/N3/5/0:
> ct_connect(): directory service layer: internal directory control layer
> error: Requested server name not found.
> Establishing connection failed.
> NULL
> Any help why is this happenning?
> The server, username, password are all correct and I am able to work through
> the enterprise manager and query analyser, its gving error only in the
> xp_cmdshell and bcp.
> After the install, the xp_cmdshell and bcp is not working anymore.
>
>|||Thank you Mike, that worked.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> The Sybase BCP.exe is now being used by your call due to the environment
> path settings written by the Sybase setup.
> Fully qualify the BCP.exe path in the call and it will work. osql.exe is
> also affected in the same way.
> Regards
> Mike
> "Yog" wrote:
> > I am running a bcp from xp_cmdshell, it was working good
> >
> > EXEC master.dbo.xp_cmdshell 'bcp DATABASE1..V_TMP_KEYWORDSMMS2 out
> > c:\Keywords\KEYWORD_00000115_16_12_2004_17_47_27.txt -c -t~ -SSYN0001
> > -UUserName -Ppassword '
> >
> > The server is Microsoft SQL Server 2000 - 8.00.760
> >
> > Then I installed sybase client in the PC inorder to get replication from
> > sybase to sql server.
> >
> > It is giving the following error message.
> >
> > CTLIB Message: - L6/O8/S5/N3/5/0:
> > ct_connect(): directory service layer: internal directory control layer
> > error: Requested server name not found.
> > Establishing connection failed.
> > NULL
> >
> > Any help why is this happenning?
> >
> > The server, username, password are all correct and I am able to work through
> > the enterprise manager and query analyser, its gving error only in the
> > xp_cmdshell and bcp.
> >
> > After the install, the xp_cmdshell and bcp is not working anymore.
> >
> >
> >
EXEC master.dbo.xp_cmdshell 'bcp DATABASE1..V_TMP_KEYWORDSMMS2 out
c:\Keywords\KEYWORD_00000115_16_12_2004_17_47_27.txt -c -t~ -SSYN0001
-UUserName -Ppassword '
The server is Microsoft SQL Server 2000 - 8.00.760
Then I installed sybase client in the PC inorder to get replication from
sybase to sql server.
It is giving the following error message.
CTLIB Message: - L6/O8/S5/N3/5/0:
ct_connect(): directory service layer: internal directory control layer
error: Requested server name not found.
Establishing connection failed.
NULL
Any help why is this happenning?
The server, username, password are all correct and I am able to work through
the enterprise manager and query analyser, its gving error only in the
xp_cmdshell and bcp.
After the install, the xp_cmdshell and bcp is not working anymore.Hi
The Sybase BCP.exe is now being used by your call due to the environment
path settings written by the Sybase setup.
Fully qualify the BCP.exe path in the call and it will work. osql.exe is
also affected in the same way.
Regards
Mike
"Yog" wrote:
> I am running a bcp from xp_cmdshell, it was working good
> EXEC master.dbo.xp_cmdshell 'bcp DATABASE1..V_TMP_KEYWORDSMMS2 out
> c:\Keywords\KEYWORD_00000115_16_12_2004_17_47_27.txt -c -t~ -SSYN0001
> -UUserName -Ppassword '
> The server is Microsoft SQL Server 2000 - 8.00.760
> Then I installed sybase client in the PC inorder to get replication from
> sybase to sql server.
> It is giving the following error message.
> CTLIB Message: - L6/O8/S5/N3/5/0:
> ct_connect(): directory service layer: internal directory control layer
> error: Requested server name not found.
> Establishing connection failed.
> NULL
> Any help why is this happenning?
> The server, username, password are all correct and I am able to work through
> the enterprise manager and query analyser, its gving error only in the
> xp_cmdshell and bcp.
> After the install, the xp_cmdshell and bcp is not working anymore.
>
>|||Thank you Mike, that worked.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> The Sybase BCP.exe is now being used by your call due to the environment
> path settings written by the Sybase setup.
> Fully qualify the BCP.exe path in the call and it will work. osql.exe is
> also affected in the same way.
> Regards
> Mike
> "Yog" wrote:
> > I am running a bcp from xp_cmdshell, it was working good
> >
> > EXEC master.dbo.xp_cmdshell 'bcp DATABASE1..V_TMP_KEYWORDSMMS2 out
> > c:\Keywords\KEYWORD_00000115_16_12_2004_17_47_27.txt -c -t~ -SSYN0001
> > -UUserName -Ppassword '
> >
> > The server is Microsoft SQL Server 2000 - 8.00.760
> >
> > Then I installed sybase client in the PC inorder to get replication from
> > sybase to sql server.
> >
> > It is giving the following error message.
> >
> > CTLIB Message: - L6/O8/S5/N3/5/0:
> > ct_connect(): directory service layer: internal directory control layer
> > error: Requested server name not found.
> > Establishing connection failed.
> > NULL
> >
> > Any help why is this happenning?
> >
> > The server, username, password are all correct and I am able to work through
> > the enterprise manager and query analyser, its gving error only in the
> > xp_cmdshell and bcp.
> >
> > After the install, the xp_cmdshell and bcp is not working anymore.
> >
> >
> >
Subscribe to:
Posts (Atom)