I took the back from Enterprise version of sql server and trying to restore
at MSDE Version... it restored successfully but after that when I try to see
the tables and procedures it gave an error and like the database is not the
valid schema.. can any one tell me what I have to do ?
Could you please paste the exact error message?
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"msnews.microsoft.com" <Noor> wrote in message
news:uR$POQujFHA.1464@.TK2MSFTNGP14.phx.gbl...
>I took the back from Enterprise version of sql server and trying to restore
>at MSDE Version... it restored successfully but after that when I try to
>see the tables and procedures it gave an error and like the database is not
>the valid schema.. can any one tell me what I have to do ?
>
Showing posts with label enterprise. Show all posts
Showing posts with label enterprise. Show all posts
Monday, March 26, 2012
Invalid Primary Key error during table linking
Hi,
Something strange has happened to my table. I used Enterprise Manager today to delete 3 columns. When I went to re-link the table using Access Linked Table Manager, it gave me an error. I then deleted the link to the table, and tried to Link it again using 'Get External Data--Link Tables'. I am getting an error (no surprise!):
" 'dbo.tblSpaceUse.PK_RoomID' is not a valid name. Make sure that it does not include invalid characters or punctuation and that it is not too long".
When I go into Enterprise Manager to 'manage Indexes' on the table, it shows me that the existing index is in fact dbo.tblSpaceUse.PK_RoomID.
About a month ago, I had to rename the index, because it had been pointing to the wrong table. The SQL I used to rename it (in Query Analyzer) is:
EXEC sp_rename 'dbo.tblSpaceUse.PK_RoomID', 'tblSpaceUse.PK_RoomID', 'INDEX'
I have been using the table successfully since then, until today. I have not done anything with the index; the only change I attempted was to delete 3 columns (not related to the index). I do not think I have made any changes to the table since I renamed the index.
I tried to run the rename SQL again (a desperate attempt!) and get the error message:
Server: Msg 15248, Level 11, State 1, Procedure sp_rename, Line 192
Either the parameter @.objname is ambiguous or the claimed @.objtype (INDEX) is wrong.
Any ideas on what went wrong and what I can do to fix it?
Thanks,
Lorihave fixed the problem by creating the table anew. thanks anyway.
Something strange has happened to my table. I used Enterprise Manager today to delete 3 columns. When I went to re-link the table using Access Linked Table Manager, it gave me an error. I then deleted the link to the table, and tried to Link it again using 'Get External Data--Link Tables'. I am getting an error (no surprise!):
" 'dbo.tblSpaceUse.PK_RoomID' is not a valid name. Make sure that it does not include invalid characters or punctuation and that it is not too long".
When I go into Enterprise Manager to 'manage Indexes' on the table, it shows me that the existing index is in fact dbo.tblSpaceUse.PK_RoomID.
About a month ago, I had to rename the index, because it had been pointing to the wrong table. The SQL I used to rename it (in Query Analyzer) is:
EXEC sp_rename 'dbo.tblSpaceUse.PK_RoomID', 'tblSpaceUse.PK_RoomID', 'INDEX'
I have been using the table successfully since then, until today. I have not done anything with the index; the only change I attempted was to delete 3 columns (not related to the index). I do not think I have made any changes to the table since I renamed the index.
I tried to run the rename SQL again (a desperate attempt!) and get the error message:
Server: Msg 15248, Level 11, State 1, Procedure sp_rename, Line 192
Either the parameter @.objname is ambiguous or the claimed @.objtype (INDEX) is wrong.
Any ideas on what went wrong and what I can do to fix it?
Thanks,
Lorihave fixed the problem by creating the table anew. thanks anyway.
Wednesday, March 21, 2012
Invalid Object
I'm running a simple select statement.
Select TestSchema From TestDB where DbName = 'TEST'
It runs fine when I run it in Enterprise Manager.
But I get an error message when I run it in Query Analyser.
Error: Invalid object name 'TestDB'
Help!DBNAME is a built-in function. If your table has a column of that name,
try:
Select TestSchema From TestDB where [DbName] = 'TEST'
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"sql" <sql@.discussions.microsoft.com> wrote in message
news:DC485C69-107A-4A63-8B1B-6B71BCBA75AE@.microsoft.com...
I'm running a simple select statement.
Select TestSchema From TestDB where DbName = 'TEST'
It runs fine when I run it in Enterprise Manager.
But I get an error message when I run it in Query Analyser.
Error: Invalid object name 'TestDB'
Help!|||Tom:
I tried with the square brackets, but I still get the same error message.
"Tom Moreau" wrote:
> DBNAME is a built-in function. If your table has a column of that name,
> try:
> Select TestSchema From TestDB where [DbName] = 'TEST'
>
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "sql" <sql@.discussions.microsoft.com> wrote in message
> news:DC485C69-107A-4A63-8B1B-6B71BCBA75AE@.microsoft.com...
> I'm running a simple select statement.
> Select TestSchema From TestDB where DbName = 'TEST'
> It runs fine when I run it in Enterprise Manager.
> But I get an error message when I run it in Query Analyser.
>
> Error: Invalid object name 'TestDB'
> Help!
>|||Tom,
Isn't the function db_name()?
I'm suspicious that the table may be under a different owner name. Try owner qualify the table to see what you get.
Richard
--
Message posted via http://www.sqlmonster.com|||Oops, you're right. I'd be tempted to run the profiler and see what's being
sent when he runs it (successfully) through Enterprise Manager. That may
give a clue.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Richard Ding via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:d534a166a789418e873d7ab25b41a525@.SQLMonster.com...
Tom,
Isn't the function db_name()?
I'm suspicious that the table may be under a different owner name. Try owner
qualify the table to see what you get.
Richard
--
Message posted via http://www.sqlmonster.com
Select TestSchema From TestDB where DbName = 'TEST'
It runs fine when I run it in Enterprise Manager.
But I get an error message when I run it in Query Analyser.
Error: Invalid object name 'TestDB'
Help!DBNAME is a built-in function. If your table has a column of that name,
try:
Select TestSchema From TestDB where [DbName] = 'TEST'
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"sql" <sql@.discussions.microsoft.com> wrote in message
news:DC485C69-107A-4A63-8B1B-6B71BCBA75AE@.microsoft.com...
I'm running a simple select statement.
Select TestSchema From TestDB where DbName = 'TEST'
It runs fine when I run it in Enterprise Manager.
But I get an error message when I run it in Query Analyser.
Error: Invalid object name 'TestDB'
Help!|||Tom:
I tried with the square brackets, but I still get the same error message.
"Tom Moreau" wrote:
> DBNAME is a built-in function. If your table has a column of that name,
> try:
> Select TestSchema From TestDB where [DbName] = 'TEST'
>
> --
> Tom
> ---
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "sql" <sql@.discussions.microsoft.com> wrote in message
> news:DC485C69-107A-4A63-8B1B-6B71BCBA75AE@.microsoft.com...
> I'm running a simple select statement.
> Select TestSchema From TestDB where DbName = 'TEST'
> It runs fine when I run it in Enterprise Manager.
> But I get an error message when I run it in Query Analyser.
>
> Error: Invalid object name 'TestDB'
> Help!
>|||Tom,
Isn't the function db_name()?
I'm suspicious that the table may be under a different owner name. Try owner qualify the table to see what you get.
Richard
--
Message posted via http://www.sqlmonster.com|||Oops, you're right. I'd be tempted to run the profiler and see what's being
sent when he runs it (successfully) through Enterprise Manager. That may
give a clue.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Richard Ding via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:d534a166a789418e873d7ab25b41a525@.SQLMonster.com...
Tom,
Isn't the function db_name()?
I'm suspicious that the table may be under a different owner name. Try owner
qualify the table to see what you get.
Richard
--
Message posted via http://www.sqlmonster.com
Invalid Object
I'm running a simple select statement.
Select TestSchema From TestDB where DbName = 'TEST'
It runs fine when I run it in Enterprise Manager.
But I get an error message when I run it in Query Analyser.
Error: Invalid object name 'TestDB'
Help!
DBNAME is a built-in function. If your table has a column of that name,
try:
Select TestSchema From TestDB where [DbName] = 'TEST'
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"sql" <sql@.discussions.microsoft.com> wrote in message
news:DC485C69-107A-4A63-8B1B-6B71BCBA75AE@.microsoft.com...
I'm running a simple select statement.
Select TestSchema From TestDB where DbName = 'TEST'
It runs fine when I run it in Enterprise Manager.
But I get an error message when I run it in Query Analyser.
Error: Invalid object name 'TestDB'
Help!
|||Tom:
I tried with the square brackets, but I still get the same error message.
"Tom Moreau" wrote:
> DBNAME is a built-in function. If your table has a column of that name,
> try:
> Select TestSchema From TestDB where [DbName] = 'TEST'
>
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "sql" <sql@.discussions.microsoft.com> wrote in message
> news:DC485C69-107A-4A63-8B1B-6B71BCBA75AE@.microsoft.com...
> I'm running a simple select statement.
> Select TestSchema From TestDB where DbName = 'TEST'
> It runs fine when I run it in Enterprise Manager.
> But I get an error message when I run it in Query Analyser.
>
> Error: Invalid object name 'TestDB'
> Help!
>
|||Tom,
Isn't the function db_name()?
I'm suspicious that the table may be under a different owner name. Try owner qualify the table to see what you get.
Richard
Message posted via http://www.sqlmonster.com
|||Oops, you're right. I'd be tempted to run the profiler and see what's being
sent when he runs it (successfully) through Enterprise Manager. That may
give a clue.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Richard Ding via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:d534a166a789418e873d7ab25b41a525@.SQLMonster.c om...
Tom,
Isn't the function db_name()?
I'm suspicious that the table may be under a different owner name. Try owner
qualify the table to see what you get.
Richard
Message posted via http://www.sqlmonster.com
Select TestSchema From TestDB where DbName = 'TEST'
It runs fine when I run it in Enterprise Manager.
But I get an error message when I run it in Query Analyser.
Error: Invalid object name 'TestDB'
Help!
DBNAME is a built-in function. If your table has a column of that name,
try:
Select TestSchema From TestDB where [DbName] = 'TEST'
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"sql" <sql@.discussions.microsoft.com> wrote in message
news:DC485C69-107A-4A63-8B1B-6B71BCBA75AE@.microsoft.com...
I'm running a simple select statement.
Select TestSchema From TestDB where DbName = 'TEST'
It runs fine when I run it in Enterprise Manager.
But I get an error message when I run it in Query Analyser.
Error: Invalid object name 'TestDB'
Help!
|||Tom:
I tried with the square brackets, but I still get the same error message.
"Tom Moreau" wrote:
> DBNAME is a built-in function. If your table has a column of that name,
> try:
> Select TestSchema From TestDB where [DbName] = 'TEST'
>
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com
>
> "sql" <sql@.discussions.microsoft.com> wrote in message
> news:DC485C69-107A-4A63-8B1B-6B71BCBA75AE@.microsoft.com...
> I'm running a simple select statement.
> Select TestSchema From TestDB where DbName = 'TEST'
> It runs fine when I run it in Enterprise Manager.
> But I get an error message when I run it in Query Analyser.
>
> Error: Invalid object name 'TestDB'
> Help!
>
|||Tom,
Isn't the function db_name()?
I'm suspicious that the table may be under a different owner name. Try owner qualify the table to see what you get.
Richard
Message posted via http://www.sqlmonster.com
|||Oops, you're right. I'd be tempted to run the profiler and see what's being
sent when he runs it (successfully) through Enterprise Manager. That may
give a clue.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
"Richard Ding via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:d534a166a789418e873d7ab25b41a525@.SQLMonster.c om...
Tom,
Isn't the function db_name()?
I'm suspicious that the table may be under a different owner name. Try owner
qualify the table to see what you get.
Richard
Message posted via http://www.sqlmonster.com
Monday, March 19, 2012
'Invalid cursor state' error when saving table changes
I've created a small DB (one table so far, 0 records as yet). When I try to
change the table structure via Enterprise Manager, I get the following
error:
/*
05 August 2004 16:02:36
User:
Server: HYPERION
Database: TADB
Application: MS SQLEM - Data Tools
*/
'TANumbers' table
- Unable to rename column from 'AdviceNoteID' to 'AdviceNote'.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
The actual change I was trying to do worked, or at least it appears to have
done.
BOL suggest that this error might be due to the fact that the DB or the Tlog
is full. With no data an no transactions so far, that is unlikely. Plus EM
reports that there is 8.43 Mb free out of 10Mb!
Any ideas anyone?
Thanks
ChrisHi CJM,
From your descriptions, I understood you could not rename your column name
by SQL Server Enterprise Manager. Have I understood you? If there is
anything I misunderstood, please feel free to let me know.
Admittedly, it is a known issue for us when using SQL Server Enterprise
Manager. You will have to use sp_rename in Query Analyzer instead. I am
sorry for the inconvenience you may encounter.
More information of how to use sp_rename could be found in BooksOnline or
MSDN Online
sp_rename
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_
sp_ra-rz_3ns5.asp
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
Microsoft Developer Community Support
---
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,
I'm just curious as to why *this* table on *this* DB suffers from this
problem?
I've never had a problem on this server before, so what is it about this DB
that is so different?
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:v5%23isS4eEHA.1060@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> From your descriptions, I understood you could not rename your column name
> by SQL Server Enterprise Manager. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Admittedly, it is a known issue for us when using SQL Server Enterprise
> Manager. You will have to use sp_rename in Query Analyzer instead. I am
> sorry for the inconvenience you may encounter.
> More information of how to use sp_rename could be found in BooksOnline or
> MSDN Online
> sp_rename
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_
> sp_ra-rz_3ns5.asp
>|||Hi CJM,
This issue was reported in SP3 and higher version, it was fixed in SQL
Server 8.00.902
It is very possible that changes of columns are made successfully before
you upgrade to SQL Server SP3 .
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
Microsoft Developer Community Support
---
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!|||""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:k37x%23bDfEHA.3212@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> This issue was reported in SP3 and higher version, it was fixed in SQL
> Server 8.00.902
> It is very possible that changes of columns are made successfully before
> you upgrade to SQL Server SP3 .
>
I'm a bit confused...
How do I get hold of v8.00.902? I thought I was up to date with SP3a...
Chris|||Hi Chris,
Thanks for your prompt updates!
For 8.00.0902 or higher, a supported fix is now available from Microsoft,
but it is only intended to correct the problem that is described in this
article. Apply it only to systems that are experiencing this specific
problem.
To resolve this problem, please contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support
Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
Asking hotfix will be a FREE case. If PSS staff asking a KB for this issue,
please show me the link and KB No below
FIX: Profiler RPC events truncate parameters that have a text data type to
16 characters
http://support.microsoft.com/?id=839688
You will receive Build 8.00.0927 instead from PSS, based on my testing,
this hotfix could resolved the problm as you described. BTW, I cannot find
excatly Build 8.00.0902 and its relative KB internal:(
If you want PSS Staff be notified of this newsgroup thread, show him the
following information
Tomcat IssueID: 24064701
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
Microsoft Developer Community Support
---
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!|||Mingqing,
I've downloaded, installed & tested the patch and everything works fine now.
Thanks
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:c6mfgnofEHA.1200@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> Thanks for your prompt updates!
> For 8.00.0902 or higher, a supported fix is now available from Microsoft,
> but it is only intended to correct the problem that is described in this
> article. Apply it only to systems that are experiencing this specific
> problem.
>|||Hi Chris,
It's great to hear that you have resolved it! Thanks for your kindest reply
letting me know the status of your issue.
If you encounter any questions or difficulties using SQL Server, please
feel free to post here. We are always here to be of assistance!
Thanks again for using MSDN Managed Newsgroup!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
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!
change the table structure via Enterprise Manager, I get the following
error:
/*
05 August 2004 16:02:36
User:
Server: HYPERION
Database: TADB
Application: MS SQLEM - Data Tools
*/
'TANumbers' table
- Unable to rename column from 'AdviceNoteID' to 'AdviceNote'.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
The actual change I was trying to do worked, or at least it appears to have
done.
BOL suggest that this error might be due to the fact that the DB or the Tlog
is full. With no data an no transactions so far, that is unlikely. Plus EM
reports that there is 8.43 Mb free out of 10Mb!
Any ideas anyone?
Thanks
ChrisHi CJM,
From your descriptions, I understood you could not rename your column name
by SQL Server Enterprise Manager. Have I understood you? If there is
anything I misunderstood, please feel free to let me know.
Admittedly, it is a known issue for us when using SQL Server Enterprise
Manager. You will have to use sp_rename in Query Analyzer instead. I am
sorry for the inconvenience you may encounter.
More information of how to use sp_rename could be found in BooksOnline or
MSDN Online
sp_rename
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_
sp_ra-rz_3ns5.asp
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
Microsoft Developer Community Support
---
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,
I'm just curious as to why *this* table on *this* DB suffers from this
problem?
I've never had a problem on this server before, so what is it about this DB
that is so different?
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:v5%23isS4eEHA.1060@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> From your descriptions, I understood you could not rename your column name
> by SQL Server Enterprise Manager. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Admittedly, it is a known issue for us when using SQL Server Enterprise
> Manager. You will have to use sp_rename in Query Analyzer instead. I am
> sorry for the inconvenience you may encounter.
> More information of how to use sp_rename could be found in BooksOnline or
> MSDN Online
> sp_rename
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_
> sp_ra-rz_3ns5.asp
>|||Hi CJM,
This issue was reported in SP3 and higher version, it was fixed in SQL
Server 8.00.902
It is very possible that changes of columns are made successfully before
you upgrade to SQL Server SP3 .
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
Microsoft Developer Community Support
---
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!|||""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:k37x%23bDfEHA.3212@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> This issue was reported in SP3 and higher version, it was fixed in SQL
> Server 8.00.902
> It is very possible that changes of columns are made successfully before
> you upgrade to SQL Server SP3 .
>
I'm a bit confused...
How do I get hold of v8.00.902? I thought I was up to date with SP3a...
Chris|||Hi Chris,
Thanks for your prompt updates!
For 8.00.0902 or higher, a supported fix is now available from Microsoft,
but it is only intended to correct the problem that is described in this
article. Apply it only to systems that are experiencing this specific
problem.
To resolve this problem, please contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support
Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
Asking hotfix will be a FREE case. If PSS staff asking a KB for this issue,
please show me the link and KB No below
FIX: Profiler RPC events truncate parameters that have a text data type to
16 characters
http://support.microsoft.com/?id=839688
You will receive Build 8.00.0927 instead from PSS, based on my testing,
this hotfix could resolved the problm as you described. BTW, I cannot find
excatly Build 8.00.0902 and its relative KB internal:(
If you want PSS Staff be notified of this newsgroup thread, show him the
following information
Tomcat IssueID: 24064701
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
Microsoft Developer Community Support
---
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!|||Mingqing,
I've downloaded, installed & tested the patch and everything works fine now.
Thanks
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:c6mfgnofEHA.1200@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> Thanks for your prompt updates!
> For 8.00.0902 or higher, a supported fix is now available from Microsoft,
> but it is only intended to correct the problem that is described in this
> article. Apply it only to systems that are experiencing this specific
> problem.
>|||Hi Chris,
It's great to hear that you have resolved it! Thanks for your kindest reply
letting me know the status of your issue.
If you encounter any questions or difficulties using SQL Server, please
feel free to post here. We are always here to be of assistance!
Thanks again for using MSDN Managed Newsgroup!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
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!
'Invalid cursor state' error when saving table changes
I've created a small DB (one table so far, 0 records as yet). When I try to
change the table structure via Enterprise Manager, I get the following
error:
/*
05 August 2004 16:02:36
User:
Server: HYPERION
Database: TADB
Application: MS SQLEM - Data Tools
*/
'TANumbers' table
- Unable to rename column from 'AdviceNoteID' to 'AdviceNote'.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
The actual change I was trying to do worked, or at least it appears to have
done.
BOL suggest that this error might be due to the fact that the DB or the Tlog
is full. With no data an no transactions so far, that is unlikely. Plus EM
reports that there is 8.43 Mb free out of 10Mb!
Any ideas anyone?
Thanks
ChrisHi CJM,
From your descriptions, I understood you could not rename your column name
by SQL Server Enterprise Manager. Have I understood you? If there is
anything I misunderstood, please feel free to let me know.
Admittedly, it is a known issue for us when using SQL Server Enterprise
Manager. You will have to use sp_rename in Query Analyzer instead. I am
sorry for the inconvenience you may encounter.
More information of how to use sp_rename could be found in BooksOnline or
MSDN Online
sp_rename
http://msdn.microsoft.com/library/d...-us/tsqlref/ts_
sp_ra-rz_3ns5.asp
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
Microsoft Developer Community Support
---
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,
I'm just curious as to why *this* table on *this* DB suffers from this
problem?
I've never had a problem on this server before, so what is it about this DB
that is so different?
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:v5%23isS4eEHA.1060@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> From your descriptions, I understood you could not rename your column name
> by SQL Server Enterprise Manager. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Admittedly, it is a known issue for us when using SQL Server Enterprise
> Manager. You will have to use sp_rename in Query Analyzer instead. I am
> sorry for the inconvenience you may encounter.
> More information of how to use sp_rename could be found in BooksOnline or
> MSDN Online
> sp_rename
>
http://msdn.microsoft.com/library/d...-us/tsqlref/ts_
> sp_ra-rz_3ns5.asp
>|||Hi CJM,
This issue was reported in SP3 and higher version, it was fixed in SQL
Server 8.00.902
It is very possible that changes of columns are made successfully before
you upgrade to SQL Server SP3 .
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
Microsoft Developer Community Support
---
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!|||""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:k37x%23bDfEHA.3212@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> This issue was reported in SP3 and higher version, it was fixed in SQL
> Server 8.00.902
> It is very possible that changes of columns are made successfully before
> you upgrade to SQL Server SP3 .
>
I'm a bit confused...
How do I get hold of v8.00.902? I thought I was up to date with SP3a...
Chris|||Hi Chris,
Thanks for your prompt updates!
For 8.00.0902 or higher, a supported fix is now available from Microsoft,
but it is only intended to correct the problem that is described in this
article. Apply it only to systems that are experiencing this specific
problem.
To resolve this problem, please contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support
Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/defaul...;EN-US;CNTACTMS
Asking hotfix will be a FREE case. If PSS staff asking a KB for this issue,
please show me the link and KB No below
FIX: Profiler RPC events truncate parameters that have a text data type to
16 characters
http://support.microsoft.com/?id=839688
You will receive Build 8.00.0927 instead from PSS, based on my testing,
this hotfix could resolved the problm as you described. BTW, I cannot find
excatly Build 8.00.0902 and its relative KB internal
If you want PSS Staff be notified of this newsgroup thread, show him the
following information
Tomcat IssueID: 24064701
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
Microsoft Developer Community Support
---
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!|||Mingqing,
I've downloaded, installed & tested the patch and everything works fine now.
Thanks
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:c6mfgnofEHA.1200@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> Thanks for your prompt updates!
> For 8.00.0902 or higher, a supported fix is now available from Microsoft,
> but it is only intended to correct the problem that is described in this
> article. Apply it only to systems that are experiencing this specific
> problem.
>|||Hi Chris,
It's great to hear that you have resolved it! Thanks for your kindest reply
letting me know the status of your issue.
If you encounter any questions or difficulties using SQL Server, please
feel free to post here. We are always here to be of assistance!
Thanks again for using MSDN Managed Newsgroup!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
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!
change the table structure via Enterprise Manager, I get the following
error:
/*
05 August 2004 16:02:36
User:
Server: HYPERION
Database: TADB
Application: MS SQLEM - Data Tools
*/
'TANumbers' table
- Unable to rename column from 'AdviceNoteID' to 'AdviceNote'.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
The actual change I was trying to do worked, or at least it appears to have
done.
BOL suggest that this error might be due to the fact that the DB or the Tlog
is full. With no data an no transactions so far, that is unlikely. Plus EM
reports that there is 8.43 Mb free out of 10Mb!
Any ideas anyone?
Thanks
ChrisHi CJM,
From your descriptions, I understood you could not rename your column name
by SQL Server Enterprise Manager. Have I understood you? If there is
anything I misunderstood, please feel free to let me know.
Admittedly, it is a known issue for us when using SQL Server Enterprise
Manager. You will have to use sp_rename in Query Analyzer instead. I am
sorry for the inconvenience you may encounter.
More information of how to use sp_rename could be found in BooksOnline or
MSDN Online
sp_rename
http://msdn.microsoft.com/library/d...-us/tsqlref/ts_
sp_ra-rz_3ns5.asp
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
Microsoft Developer Community Support
---
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,
I'm just curious as to why *this* table on *this* DB suffers from this
problem?
I've never had a problem on this server before, so what is it about this DB
that is so different?
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:v5%23isS4eEHA.1060@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> From your descriptions, I understood you could not rename your column name
> by SQL Server Enterprise Manager. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Admittedly, it is a known issue for us when using SQL Server Enterprise
> Manager. You will have to use sp_rename in Query Analyzer instead. I am
> sorry for the inconvenience you may encounter.
> More information of how to use sp_rename could be found in BooksOnline or
> MSDN Online
> sp_rename
>
http://msdn.microsoft.com/library/d...-us/tsqlref/ts_
> sp_ra-rz_3ns5.asp
>|||Hi CJM,
This issue was reported in SP3 and higher version, it was fixed in SQL
Server 8.00.902
It is very possible that changes of columns are made successfully before
you upgrade to SQL Server SP3 .
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
Microsoft Developer Community Support
---
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!|||""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:k37x%23bDfEHA.3212@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> This issue was reported in SP3 and higher version, it was fixed in SQL
> Server 8.00.902
> It is very possible that changes of columns are made successfully before
> you upgrade to SQL Server SP3 .
>
I'm a bit confused...
How do I get hold of v8.00.902? I thought I was up to date with SP3a...
Chris|||Hi Chris,
Thanks for your prompt updates!
For 8.00.0902 or higher, a supported fix is now available from Microsoft,
but it is only intended to correct the problem that is described in this
article. Apply it only to systems that are experiencing this specific
problem.
To resolve this problem, please contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support
Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/defaul...;EN-US;CNTACTMS
Asking hotfix will be a FREE case. If PSS staff asking a KB for this issue,
please show me the link and KB No below
FIX: Profiler RPC events truncate parameters that have a text data type to
16 characters
http://support.microsoft.com/?id=839688
You will receive Build 8.00.0927 instead from PSS, based on my testing,
this hotfix could resolved the problm as you described. BTW, I cannot find
excatly Build 8.00.0902 and its relative KB internal
If you want PSS Staff be notified of this newsgroup thread, show him the
following information
Tomcat IssueID: 24064701
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
Microsoft Developer Community Support
---
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!|||Mingqing,
I've downloaded, installed & tested the patch and everything works fine now.
Thanks
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:c6mfgnofEHA.1200@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> Thanks for your prompt updates!
> For 8.00.0902 or higher, a supported fix is now available from Microsoft,
> but it is only intended to correct the problem that is described in this
> article. Apply it only to systems that are experiencing this specific
> problem.
>|||Hi Chris,
It's great to hear that you have resolved it! Thanks for your kindest reply
letting me know the status of your issue.
If you encounter any questions or difficulties using SQL Server, please
feel free to post here. We are always here to be of assistance!
Thanks again for using MSDN Managed Newsgroup!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
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!
'Invalid cursor state' error when saving table changes
I've created a small DB (one table so far, 0 records as yet). When I try to
change the table structure via Enterprise Manager, I get the following
error:
/*
05 August 2004 16:02:36
User:
Server: HYPERION
Database: TADB
Application: MS SQLEM - Data Tools
*/
'TANumbers' table
- Unable to rename column from 'AdviceNoteID' to 'AdviceNote'.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
The actual change I was trying to do worked, or at least it appears to have
done.
BOL suggest that this error might be due to the fact that the DB or the Tlog
is full. With no data an no transactions so far, that is unlikely. Plus EM
reports that there is 8.43 Mb free out of 10Mb!
Any ideas anyone?
Thanks
Chris
Hi CJM,
From your descriptions, I understood you could not rename your column name
by SQL Server Enterprise Manager. Have I understood you? If there is
anything I misunderstood, please feel free to let me know.
Admittedly, it is a known issue for us when using SQL Server Enterprise
Manager. You will have to use sp_rename in Query Analyzer instead. I am
sorry for the inconvenience you may encounter.
More information of how to use sp_rename could be found in BooksOnline or
MSDN Online
sp_rename
http://msdn.microsoft.com/library/de...us/tsqlref/ts_
sp_ra-rz_3ns5.asp
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
Microsoft Developer Community Support
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,
I'm just curious as to why *this* table on *this* DB suffers from this
problem?
I've never had a problem on this server before, so what is it about this DB
that is so different?
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:v5%23isS4eEHA.1060@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> From your descriptions, I understood you could not rename your column name
> by SQL Server Enterprise Manager. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Admittedly, it is a known issue for us when using SQL Server Enterprise
> Manager. You will have to use sp_rename in Query Analyzer instead. I am
> sorry for the inconvenience you may encounter.
> More information of how to use sp_rename could be found in BooksOnline or
> MSDN Online
> sp_rename
>
http://msdn.microsoft.com/library/de...us/tsqlref/ts_
> sp_ra-rz_3ns5.asp
>
|||Hi CJM,
This issue was reported in SP3 and higher version, it was fixed in SQL
Server 8.00.902
It is very possible that changes of columns are made successfully before
you upgrade to SQL Server SP3 .
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
Microsoft Developer Community Support
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!
|||""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:k37x%23bDfEHA.3212@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> This issue was reported in SP3 and higher version, it was fixed in SQL
> Server 8.00.902
> It is very possible that changes of columns are made successfully before
> you upgrade to SQL Server SP3 .
>
I'm a bit confused...
How do I get hold of v8.00.902? I thought I was up to date with SP3a...
Chris
|||Hi Chris,
Thanks for your prompt updates!
For 8.00.0902 or higher, a supported fix is now available from Microsoft,
but it is only intended to correct the problem that is described in this
article. Apply it only to systems that are experiencing this specific
problem.
To resolve this problem, please contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support
Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/default...EN-US;CNTACTMS
Asking hotfix will be a FREE case. If PSS staff asking a KB for this issue,
please show me the link and KB No below
FIX: Profiler RPC events truncate parameters that have a text data type to
16 characters
http://support.microsoft.com/?id=839688
You will receive Build 8.00.0927 instead from PSS, based on my testing,
this hotfix could resolved the problm as you described. BTW, I cannot find
excatly Build 8.00.0902 and its relative KB internal
If you want PSS Staff be notified of this newsgroup thread, show him the
following information
Tomcat IssueID: 24064701
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
Microsoft Developer Community Support
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!
|||Mingqing,
I've downloaded, installed & tested the patch and everything works fine now.
Thanks
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:c6mfgnofEHA.1200@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> Thanks for your prompt updates!
> For 8.00.0902 or higher, a supported fix is now available from Microsoft,
> but it is only intended to correct the problem that is described in this
> article. Apply it only to systems that are experiencing this specific
> problem.
>
|||Hi Chris,
It's great to hear that you have resolved it! Thanks for your kindest reply
letting me know the status of your issue.
If you encounter any questions or difficulties using SQL Server, please
feel free to post here. We are always here to be of assistance!
Thanks again for using MSDN Managed Newsgroup!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
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!
change the table structure via Enterprise Manager, I get the following
error:
/*
05 August 2004 16:02:36
User:
Server: HYPERION
Database: TADB
Application: MS SQLEM - Data Tools
*/
'TANumbers' table
- Unable to rename column from 'AdviceNoteID' to 'AdviceNote'.
ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state
The actual change I was trying to do worked, or at least it appears to have
done.
BOL suggest that this error might be due to the fact that the DB or the Tlog
is full. With no data an no transactions so far, that is unlikely. Plus EM
reports that there is 8.43 Mb free out of 10Mb!
Any ideas anyone?
Thanks
Chris
Hi CJM,
From your descriptions, I understood you could not rename your column name
by SQL Server Enterprise Manager. Have I understood you? If there is
anything I misunderstood, please feel free to let me know.
Admittedly, it is a known issue for us when using SQL Server Enterprise
Manager. You will have to use sp_rename in Query Analyzer instead. I am
sorry for the inconvenience you may encounter.
More information of how to use sp_rename could be found in BooksOnline or
MSDN Online
sp_rename
http://msdn.microsoft.com/library/de...us/tsqlref/ts_
sp_ra-rz_3ns5.asp
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
Microsoft Developer Community Support
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,
I'm just curious as to why *this* table on *this* DB suffers from this
problem?
I've never had a problem on this server before, so what is it about this DB
that is so different?
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:v5%23isS4eEHA.1060@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> From your descriptions, I understood you could not rename your column name
> by SQL Server Enterprise Manager. Have I understood you? If there is
> anything I misunderstood, please feel free to let me know.
> Admittedly, it is a known issue for us when using SQL Server Enterprise
> Manager. You will have to use sp_rename in Query Analyzer instead. I am
> sorry for the inconvenience you may encounter.
> More information of how to use sp_rename could be found in BooksOnline or
> MSDN Online
> sp_rename
>
http://msdn.microsoft.com/library/de...us/tsqlref/ts_
> sp_ra-rz_3ns5.asp
>
|||Hi CJM,
This issue was reported in SP3 and higher version, it was fixed in SQL
Server 8.00.902
It is very possible that changes of columns are made successfully before
you upgrade to SQL Server SP3 .
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
Microsoft Developer Community Support
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!
|||""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:k37x%23bDfEHA.3212@.cpmsftngxa06.phx.gbl...
> Hi CJM,
> This issue was reported in SP3 and higher version, it was fixed in SQL
> Server 8.00.902
> It is very possible that changes of columns are made successfully before
> you upgrade to SQL Server SP3 .
>
I'm a bit confused...
How do I get hold of v8.00.902? I thought I was up to date with SP3a...
Chris
|||Hi Chris,
Thanks for your prompt updates!
For 8.00.0902 or higher, a supported fix is now available from Microsoft,
but it is only intended to correct the problem that is described in this
article. Apply it only to systems that are experiencing this specific
problem.
To resolve this problem, please contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support
Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/default...EN-US;CNTACTMS
Asking hotfix will be a FREE case. If PSS staff asking a KB for this issue,
please show me the link and KB No below
FIX: Profiler RPC events truncate parameters that have a text data type to
16 characters
http://support.microsoft.com/?id=839688
You will receive Build 8.00.0927 instead from PSS, based on my testing,
this hotfix could resolved the problm as you described. BTW, I cannot find
excatly Build 8.00.0902 and its relative KB internal
If you want PSS Staff be notified of this newsgroup thread, show him the
following information
Tomcat IssueID: 24064701
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
Microsoft Developer Community Support
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!
|||Mingqing,
I've downloaded, installed & tested the patch and everything works fine now.
Thanks
Chris
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:c6mfgnofEHA.1200@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> Thanks for your prompt updates!
> For 8.00.0902 or higher, a supported fix is now available from Microsoft,
> but it is only intended to correct the problem that is described in this
> article. Apply it only to systems that are experiencing this specific
> problem.
>
|||Hi Chris,
It's great to hear that you have resolved it! Thanks for your kindest reply
letting me know the status of your issue.
If you encounter any questions or difficulties using SQL Server, please
feel free to post here. We are always here to be of assistance!
Thanks again for using MSDN Managed Newsgroup!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
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!
Invalid cursor state @ Distribution Agent
Hi! When i create a Transactional Replication between two SQL Server 2000 (with no additional Service Pack or Update) with the Enterprise Manager, i get this error (also when i restart the agent):
Invalid cursor state
(Source: ODBC Driver Manager [ODBC]; Error number: 24000)
I think it the MDAC is not the problem, because i never updated the SQL Server 2000 and there the error is from the ODBC SQL Driver. But here it′s from the Driver Manager.
Please help me!! I really despair!
Thanks
Does this apply to your case:
http://support.microsoft.com/default.aspx?kbid=831997?
HTH,
Paul Ibison
Invalid cursor state
(Source: ODBC Driver Manager [ODBC]; Error number: 24000)
I think it the MDAC is not the problem, because i never updated the SQL Server 2000 and there the error is from the ODBC SQL Driver. But here it′s from the Driver Manager.
Please help me!! I really despair!
Thanks
Does this apply to your case:
http://support.microsoft.com/default.aspx?kbid=831997?
HTH,
Paul Ibison
Friday, March 9, 2012
Invalid class string in Enterprise manager
Hi, Sorry to be cross-posting, but I'm not getting much response to this...
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=807314&SiteID=1
...which I don't even think is in the right forum anyway. can anyone help?
Basically, I get a error box saying "Invalid class string" in Enterprise Manager whenever I try to run a query.
Apologies if this is the DTS-related article that you've already tried, but have you looked at this KB article? Even though you're not using DTS, the installer seems to have some problems during the upgrade to 2005. I haven't seen this issue before so I'm interested to see if this solves your problem.
http://support.microsoft.com/?kbid=912421
CAUSE
During the SQL Server 2005 installation, the support for the Analysis Services Processing task in SQL Server 2000 DTS is installed as the Msmdtsp.dll file. The Msmdtsp.dll file is not correctly registered after the SQL Server 2005 installation.
WORKAROUND
To work around this problem, click Start, click Run, type the following command, and then click OK:
regsvr32 "C:\Program Files\Microsoft Analysis Services\Bin\msmdtsp.dll"
Thanks,
Sam Lester (MSFT)
nope didn't work.
I installed the Analytical services, ran the regsvr line (which worked) but still having the same problem.
btw, I used to have some version of SQL Server 2005 installed (as part of Visual Studio 2005) but removed this, as I though this was causing the problem.
I tried a repair of Visual Studio 2005 hoping this might help, which took about an hour and the failed (twice). I can run queries through Server Explorer, so I can live with this for now, but I'd still like to have it fixed, SQL Server 2000 is a important tool for a developer!
|||Samuel,
I got this reply on the other thread..
Please file a defect report on http://connect.microsoft.com.
I suspect one of the designer components is corrupt or missing on your machine. Can you design Views in SQL Enterprise Manager? The Open Table designer and View designer are packaged in the same component, so it would be helpful to know that.
Thanks,
Steve
I have filed a defect report
|||Thanks for the update!
Sam
Invalid authorization specification
Hi:
I'm trying to connect to a data base of "sql server 2005 enterprise" named BCR.
The server name is "server1"
I'm using Windows Authentication to connect to server
The operating system is Windows Server 2003 Enterprise Edition Service Pack 1
When I run the aspx I get this error at line 21
System.Data.OleDb.OleDbException: Invalid authorization specification Invalid connection string attribute at System.Data.OleDb.OleDbConnection.ProcessResults(Int32 hr) at System.Data.OleDb.OleDbConnection.InitializeProvider() at System.Data.OleDb.OleDbConnection.Open() at ASP.pruebaLeeSqlServer_aspx.__Render__control1(HtmlTextWriter __output, Control parameterContainer) in Z:\Digital\pruebaLeeSqlServer.aspx:line 21
This is my code:
Dim str2 As String = "Provider=SQLNCLI; Server = server1; Database = BCR"
Dim cnn2 As OleDbConnection = New OleDbConnection(str2)
Dim cmd2 As New OleDbCommand()
Dim drd2 As OleDbDataReader
Try
cnn2.Open()
cmd2.Connection = cnn2''''line 21
cmd2.CommandText ="SELECT LastName FROM Employees"
drd2 = cmd2.ExecuteReader
Do While drd2.Read
%>
<%=drd2.GetString(0)%><br>
<%
Loop
drd2.Close()
Catch exc1 As Exception
%>
<%=exc1.ToString()%>
<%
Finally
cnn2.Close()
End Try
What could be wrong?
Do I need enable permission for asp.net in sql server?
how I can do it?
Thanks!!
You should be using the objects in the System.Data.SqlClient namespace to connect to MS SQL Server, not System.Data.OleDb. That should fix your issue given that there is no problem with your connection string.
HTH,
Ryan
I are right, I had to use System.Data.SqlClient namespace instead of System.Data.OleDb. And I just change my connection string to
"Server=server1; Database=BCR; Trusted_Connection=True;"
Thanks!
Wednesday, March 7, 2012
Invalid attribute/option identifier - SQL Server 2000 SP2
From the Enterprise Manager on the server machine, we saw a disconnection to
a SQL Server Group. The SQL Server is running and the client worksations are
able to run applications against the databases. We got the following error,
Invalid attribute/option identifier when trying to register a new server.
Any help would be appricated. EliHi
If I were you, I would apply SQL Server SP3a or SP4 immediately to your
installation.
Ever heard of the virus "slammer"? You are seriously exposed.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> From the Enterprise Manager on the server machine, we saw a disconnection
> to
> a SQL Server Group. The SQL Server is running and the client worksations
> are
> able to run applications against the databases. We got the following
> error,
> Invalid attribute/option identifier when trying to register a new server.
> Any help would be appricated. Eli
>|||Mike,
Have fixed the issue. Thanks for your reminder. Will have it updated with
SP4 very soon.
Best Regards,
Eli
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> Hi
> If I were you, I would apply SQL Server SP3a or SP4 immediately to your
> installation.
> Ever heard of the virus "slammer"? You are seriously exposed.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Eli Feng" <efeng@.kerisys.com> wrote in message
> news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
disconnection[vbcol=seagreen]
server.[vbcol=seagreen]
>|||Hi Eli,
I have the same problem. Can you tell me how you solve this problem?
Thanks in advance,
Patrick
"Eli Feng" wrote:
> Mike,
> Have fixed the issue. Thanks for your reminder. Will have it updated with
> SP4 very soon.
> Best Regards,
> Eli
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> disconnection
> server.
>
>
a SQL Server Group. The SQL Server is running and the client worksations are
able to run applications against the databases. We got the following error,
Invalid attribute/option identifier when trying to register a new server.
Any help would be appricated. EliHi
If I were you, I would apply SQL Server SP3a or SP4 immediately to your
installation.
Ever heard of the virus "slammer"? You are seriously exposed.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> From the Enterprise Manager on the server machine, we saw a disconnection
> to
> a SQL Server Group. The SQL Server is running and the client worksations
> are
> able to run applications against the databases. We got the following
> error,
> Invalid attribute/option identifier when trying to register a new server.
> Any help would be appricated. Eli
>|||Mike,
Have fixed the issue. Thanks for your reminder. Will have it updated with
SP4 very soon.
Best Regards,
Eli
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> Hi
> If I were you, I would apply SQL Server SP3a or SP4 immediately to your
> installation.
> Ever heard of the virus "slammer"? You are seriously exposed.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Eli Feng" <efeng@.kerisys.com> wrote in message
> news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
disconnection[vbcol=seagreen]
server.[vbcol=seagreen]
>|||Hi Eli,
I have the same problem. Can you tell me how you solve this problem?
Thanks in advance,
Patrick
"Eli Feng" wrote:
> Mike,
> Have fixed the issue. Thanks for your reminder. Will have it updated with
> SP4 very soon.
> Best Regards,
> Eli
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> disconnection
> server.
>
>
Invalid attribute/option identifier - SQL Server 2000 SP2
From the Enterprise Manager on the server machine, we saw a disconnection to
a SQL Server Group. The SQL Server is running and the client worksations are
able to run applications against the databases. We got the following error,
Invalid attribute/option identifier when trying to register a new server.
Any help would be appricated. EliHi
If I were you, I would apply SQL Server SP3a or SP4 immediately to your
installation.
Ever heard of the virus "slammer"? You are seriously exposed.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> From the Enterprise Manager on the server machine, we saw a disconnection
> to
> a SQL Server Group. The SQL Server is running and the client worksations
> are
> able to run applications against the databases. We got the following
> error,
> Invalid attribute/option identifier when trying to register a new server.
> Any help would be appricated. Eli
>|||Mike,
Have fixed the issue. Thanks for your reminder. Will have it updated with
SP4 very soon.
Best Regards,
Eli
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> Hi
> If I were you, I would apply SQL Server SP3a or SP4 immediately to your
> installation.
> Ever heard of the virus "slammer"? You are seriously exposed.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Eli Feng" <efeng@.kerisys.com> wrote in message
> news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> > From the Enterprise Manager on the server machine, we saw a
disconnection
> > to
> > a SQL Server Group. The SQL Server is running and the client worksations
> > are
> > able to run applications against the databases. We got the following
> > error,
> > Invalid attribute/option identifier when trying to register a new
server.
> > Any help would be appricated. Eli
> >
> >
>|||Hi Eli,
I have the same problem. Can you tell me how you solve this problem?
Thanks in advance,
Patrick
"Eli Feng" wrote:
> Mike,
> Have fixed the issue. Thanks for your reminder. Will have it updated with
> SP4 very soon.
> Best Regards,
> Eli
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> > Hi
> >
> > If I were you, I would apply SQL Server SP3a or SP4 immediately to your
> > installation.
> > Ever heard of the virus "slammer"? You are seriously exposed.
> >
> > Regards
> > --
> > Mike Epprecht, Microsoft SQL Server MVP
> > Zurich, Switzerland
> >
> > IM: mike@.epprecht.net
> >
> > MVP Program: http://www.microsoft.com/mvp
> >
> > Blog: http://www.msmvps.com/epprecht/
> >
> > "Eli Feng" <efeng@.kerisys.com> wrote in message
> > news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> > > From the Enterprise Manager on the server machine, we saw a
> disconnection
> > > to
> > > a SQL Server Group. The SQL Server is running and the client worksations
> > > are
> > > able to run applications against the databases. We got the following
> > > error,
> > > Invalid attribute/option identifier when trying to register a new
> server.
> > > Any help would be appricated. Eli
> > >
> > >
> >
> >
>
>
a SQL Server Group. The SQL Server is running and the client worksations are
able to run applications against the databases. We got the following error,
Invalid attribute/option identifier when trying to register a new server.
Any help would be appricated. EliHi
If I were you, I would apply SQL Server SP3a or SP4 immediately to your
installation.
Ever heard of the virus "slammer"? You are seriously exposed.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> From the Enterprise Manager on the server machine, we saw a disconnection
> to
> a SQL Server Group. The SQL Server is running and the client worksations
> are
> able to run applications against the databases. We got the following
> error,
> Invalid attribute/option identifier when trying to register a new server.
> Any help would be appricated. Eli
>|||Mike,
Have fixed the issue. Thanks for your reminder. Will have it updated with
SP4 very soon.
Best Regards,
Eli
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> Hi
> If I were you, I would apply SQL Server SP3a or SP4 immediately to your
> installation.
> Ever heard of the virus "slammer"? You are seriously exposed.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Eli Feng" <efeng@.kerisys.com> wrote in message
> news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> > From the Enterprise Manager on the server machine, we saw a
disconnection
> > to
> > a SQL Server Group. The SQL Server is running and the client worksations
> > are
> > able to run applications against the databases. We got the following
> > error,
> > Invalid attribute/option identifier when trying to register a new
server.
> > Any help would be appricated. Eli
> >
> >
>|||Hi Eli,
I have the same problem. Can you tell me how you solve this problem?
Thanks in advance,
Patrick
"Eli Feng" wrote:
> Mike,
> Have fixed the issue. Thanks for your reminder. Will have it updated with
> SP4 very soon.
> Best Regards,
> Eli
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> > Hi
> >
> > If I were you, I would apply SQL Server SP3a or SP4 immediately to your
> > installation.
> > Ever heard of the virus "slammer"? You are seriously exposed.
> >
> > Regards
> > --
> > Mike Epprecht, Microsoft SQL Server MVP
> > Zurich, Switzerland
> >
> > IM: mike@.epprecht.net
> >
> > MVP Program: http://www.microsoft.com/mvp
> >
> > Blog: http://www.msmvps.com/epprecht/
> >
> > "Eli Feng" <efeng@.kerisys.com> wrote in message
> > news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> > > From the Enterprise Manager on the server machine, we saw a
> disconnection
> > > to
> > > a SQL Server Group. The SQL Server is running and the client worksations
> > > are
> > > able to run applications against the databases. We got the following
> > > error,
> > > Invalid attribute/option identifier when trying to register a new
> server.
> > > Any help would be appricated. Eli
> > >
> > >
> >
> >
>
>
Invalid attribute/option identifier - SQL Server 2000 SP2
From the Enterprise Manager on the server machine, we saw a disconnection to
a SQL Server Group. The SQL Server is running and the client worksations are
able to run applications against the databases. We got the following error,
Invalid attribute/option identifier when trying to register a new server.
Any help would be appricated. Eli
Hi
If I were you, I would apply SQL Server SP3a or SP4 immediately to your
installation.
Ever heard of the virus "slammer"? You are seriously exposed.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> From the Enterprise Manager on the server machine, we saw a disconnection
> to
> a SQL Server Group. The SQL Server is running and the client worksations
> are
> able to run applications against the databases. We got the following
> error,
> Invalid attribute/option identifier when trying to register a new server.
> Any help would be appricated. Eli
>
|||Mike,
Have fixed the issue. Thanks for your reminder. Will have it updated with
SP4 very soon.
Best Regards,
Eli
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Hi
> If I were you, I would apply SQL Server SP3a or SP4 immediately to your
> installation.
> Ever heard of the virus "slammer"? You are seriously exposed.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Eli Feng" <efeng@.kerisys.com> wrote in message
> news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
disconnection[vbcol=seagreen]
server.
>
|||Hi Eli,
I have the same problem. Can you tell me how you solve this problem?
Thanks in advance,
Patrick
"Eli Feng" wrote:
> Mike,
> Have fixed the issue. Thanks for your reminder. Will have it updated with
> SP4 very soon.
> Best Regards,
> Eli
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> disconnection
> server.
>
>
a SQL Server Group. The SQL Server is running and the client worksations are
able to run applications against the databases. We got the following error,
Invalid attribute/option identifier when trying to register a new server.
Any help would be appricated. Eli
Hi
If I were you, I would apply SQL Server SP3a or SP4 immediately to your
installation.
Ever heard of the virus "slammer"? You are seriously exposed.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Eli Feng" <efeng@.kerisys.com> wrote in message
news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
> From the Enterprise Manager on the server machine, we saw a disconnection
> to
> a SQL Server Group. The SQL Server is running and the client worksations
> are
> able to run applications against the databases. We got the following
> error,
> Invalid attribute/option identifier when trying to register a new server.
> Any help would be appricated. Eli
>
|||Mike,
Have fixed the issue. Thanks for your reminder. Will have it updated with
SP4 very soon.
Best Regards,
Eli
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Hi
> If I were you, I would apply SQL Server SP3a or SP4 immediately to your
> installation.
> Ever heard of the virus "slammer"? You are seriously exposed.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Eli Feng" <efeng@.kerisys.com> wrote in message
> news:OXXfLx6%23FHA.1248@.TK2MSFTNGP14.phx.gbl...
disconnection[vbcol=seagreen]
server.
>
|||Hi Eli,
I have the same problem. Can you tell me how you solve this problem?
Thanks in advance,
Patrick
"Eli Feng" wrote:
> Mike,
> Have fixed the issue. Thanks for your reminder. Will have it updated with
> SP4 very soon.
> Best Regards,
> Eli
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:uiKhoT$%23FHA.1256@.TK2MSFTNGP15.phx.gbl...
> disconnection
> server.
>
>
Invalid attribute/option identifier
Hello all
I am getting this message when connecting to SQL Server through Enterprise Manager. However all my DSNs work without any problems.
================
A Connection could not be established to DBSERVER.
Reason: Invalid attribute/option identifier.
Please verify SQL Server is running and check your SQL Server registration properties (by right-clicking on the DBSERVER node) and try again.
================
I have reinstalled SQL Server 2000 and MDAC (ver 2.6) but no success.
Please help!MDAC 2.8 is out - try that.
Also try using NT authentiocation.|||Do not install MDAC by itself. Use SP3 to alter MDAC level.
I am getting this message when connecting to SQL Server through Enterprise Manager. However all my DSNs work without any problems.
================
A Connection could not be established to DBSERVER.
Reason: Invalid attribute/option identifier.
Please verify SQL Server is running and check your SQL Server registration properties (by right-clicking on the DBSERVER node) and try again.
================
I have reinstalled SQL Server 2000 and MDAC (ver 2.6) but no success.
Please help!MDAC 2.8 is out - try that.
Also try using NT authentiocation.|||Do not install MDAC by itself. Use SP3 to alter MDAC level.
intrusion detection, etc. for sql server
Does SQL Server 2000 Enterprise Edition have any built-in security features
for account management, such as logging user logins and locking an account w
hen a user uses the wrong password X number of times. If there is no built i
n functionality, has anyone
implemented these kinds of security features?
Thanks,
KatieThe only thing that SQL has is auditing for successfull and failed logins.
To protect your SQL Server and/or restrict access to it, you could put it
behind ISA server and only allow certain computers to connect.
We don't check for NT policies on password attempts.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi! The functionality you are looking for (account lockouts) is already avai
lable on the OS side which I think is why it is no longer built into SQL Ser
ver. Just use Windows authentication if you need this functionality, but of
course you already knew tha
t..... HTH. =)|||Ricky - With the OS security, it can detect when someone tries to access SQL
Server with a SQL login and fails? I am not so worried about Windows logins
, but I want to prevent people opening up QA and trying to run a script on a
database using their appli
cation's SQL login.
Kevin - I found the SQL Server security feature on the Security tab of Serve
r Properties in EM, and I have checked the box to audit failed logins, but w
here do the failed logins get logged?
Thanks for all your help guys!|||Failed logins would be logged to the SQL Errorlogs and the NT Application
Event log. But you'll need to restart MSSQLServer to enable the changes.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
for account management, such as logging user logins and locking an account w
hen a user uses the wrong password X number of times. If there is no built i
n functionality, has anyone
implemented these kinds of security features?
Thanks,
KatieThe only thing that SQL has is auditing for successfull and failed logins.
To protect your SQL Server and/or restrict access to it, you could put it
behind ISA server and only allow certain computers to connect.
We don't check for NT policies on password attempts.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi! The functionality you are looking for (account lockouts) is already avai
lable on the OS side which I think is why it is no longer built into SQL Ser
ver. Just use Windows authentication if you need this functionality, but of
course you already knew tha
t..... HTH. =)|||Ricky - With the OS security, it can detect when someone tries to access SQL
Server with a SQL login and fails? I am not so worried about Windows logins
, but I want to prevent people opening up QA and trying to run a script on a
database using their appli
cation's SQL login.
Kevin - I found the SQL Server security feature on the Security tab of Serve
r Properties in EM, and I have checked the box to audit failed logins, but w
here do the failed logins get logged?
Thanks for all your help guys!|||Failed logins would be logged to the SQL Errorlogs and the NT Application
Event log. But you'll need to restart MSSQLServer to enable the changes.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Subscribe to:
Comments (Atom)