I am creating an invoicing structure in our database. Our system allows
multiple companies to be setup within the one database. Each company should
have seperate invoice number sequences. E.g.
Company One's last invoice number was 10000
Company Two generates a new invoice. They should be given either 10000 or a
number in a completely different range. But they should not be given 10001
(in company one's sequence).
Has anyone any suggestions on how to create a system for generating invoice
numbers. Two users should never be given the same invoice number (within
the same company). There should never be any gaps in invoice numbers (e.g.
Company One next invoice number after 10000 must be 10001 and then 10002
etc).
I need a guaranteed system that will generate an invoice number using the
rules above.
Thanks,
ChrisIf I was to generate my next number using something such as this...
INSERT INTO Invoices (InvoiceNo)
SELECT TOP 1 InvoiceNo + 1 FROM Invoices WHERE CompanySerialNo = 5 ORDER
BY InvoiceNo DESC
This approach seems to work, except for when I generate my first invoice
because the select clause returns nothing. So I tried this...
INSERT INTO Invoices (InvoiceNo)
SELECT TOP 1 InvoiceNo FROM (
SELECT InvoiceNo + 1 As InvoiceNo FROM Invoices WHERE CompanySerialNo
= 5
UNION
SELECT 1 AS InvoiceNo) SubQuery ORDER BY InvoiceNo DESC
This seems to work. Does this sound a good approach for generating invoice
numbers that are unique to a company? And does this guarantee two users
cannot be given the same number?
Thanks,
Chris
"Chris" <cw@.community.nospam> wrote in message
news:%23QF7DOqvFHA.3124@.TK2MSFTNGP12.phx.gbl...
>I am creating an invoicing structure in our database. Our system allows
>multiple companies to be setup within the one database. Each company
>should have seperate invoice number sequences. E.g.
> Company One's last invoice number was 10000
> Company Two generates a new invoice. They should be given either 10000 or
> a number in a completely different range. But they should not be given
> 10001 (in company one's sequence).
>
> Has anyone any suggestions on how to create a system for generating
> invoice numbers. Two users should never be given the same invoice number
> (within the same company). There should never be any gaps in invoice
> numbers (e.g. Company One next invoice number after 10000 must be 10001
> and then 10002 etc).
> I need a guaranteed system that will generate an invoice number using the
> rules above.
>
> Thanks,
> Chris
>|||put it on separate tables
--
thanks,
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"Chris" wrote:
> I am creating an invoicing structure in our database. Our system allows
> multiple companies to be setup within the one database. Each company shou
ld
> have seperate invoice number sequences. E.g.
> Company One's last invoice number was 10000
> Company Two generates a new invoice. They should be given either 10000 or
a
> number in a completely different range. But they should not be given 1000
1
> (in company one's sequence).
>
> Has anyone any suggestions on how to create a system for generating invoic
e
> numbers. Two users should never be given the same invoice number (within
> the same company). There should never be any gaps in invoice numbers (e.g
.
> Company One next invoice number after 10000 must be 10001 and then 10002
> etc).
> I need a guaranteed system that will generate an invoice number using the
> rules above.
>
> Thanks,
> Chris
>
>|||Chris ,
why dont u try describing the column as identity using newid function to
give to unque number everytime
"Chris" wrote:
> If I was to generate my next number using something such as this...
> INSERT INTO Invoices (InvoiceNo)
> SELECT TOP 1 InvoiceNo + 1 FROM Invoices WHERE CompanySerialNo = 5 ORDE
R
> BY InvoiceNo DESC
>
> This approach seems to work, except for when I generate my first invoice
> because the select clause returns nothing. So I tried this...
> INSERT INTO Invoices (InvoiceNo)
> SELECT TOP 1 InvoiceNo FROM (
> SELECT InvoiceNo + 1 As InvoiceNo FROM Invoices WHERE CompanySerial
No
> = 5
> UNION
> SELECT 1 AS InvoiceNo) SubQuery ORDER BY InvoiceNo DESC
>
> This seems to work. Does this sound a good approach for generating invoic
e
> numbers that are unique to a company? And does this guarantee two users
> cannot be given the same number?
> Thanks,
> Chris
>
> "Chris" <cw@.community.nospam> wrote in message
> news:%23QF7DOqvFHA.3124@.TK2MSFTNGP12.phx.gbl...
>
>|||On Wed, 21 Sep 2005 13:29:44 +0100, Chris wrote:
>If I was to generate my next number using something such as this...
>INSERT INTO Invoices (InvoiceNo)
> SELECT TOP 1 InvoiceNo + 1 FROM Invoices WHERE CompanySerialNo = 5 ORDER
>BY InvoiceNo DESC
>
>This approach seems to work, except for when I generate my first invoice
>because the select clause returns nothing. So I tried this...
>INSERT INTO Invoices (InvoiceNo)
> SELECT TOP 1 InvoiceNo FROM (
> SELECT InvoiceNo + 1 As InvoiceNo FROM Invoices WHERE CompanySerialN
o
>= 5
> UNION
> SELECT 1 AS InvoiceNo) SubQuery ORDER BY InvoiceNo DESC
>
>This seems to work. Does this sound a good approach for generating invoice
>numbers that are unique to a company? And does this guarantee two users
>cannot be given the same number?
Hi Chris,
This one is easier, and probably quicker as well:
INSERT INTO Invoices (InvoiceNo)
SELECT COALESCE(MAX(InvoiceNo),0) + 1
FROM Invoices
WHERE CompanySerialNo = 5
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||Thanks Hugo,
That's more readable!
Chris
> Hi Chris,
> This one is easier, and probably quicker as well:
> INSERT INTO Invoices (InvoiceNo)
> SELECT COALESCE(MAX(InvoiceNo),0) + 1
> FROM Invoices
> WHERE CompanySerialNo = 5
> Best, Hugo
> --
> (Remove _NO_ and _SPAM_ to get my e-mail address)
Showing posts with label structure. Show all posts
Showing posts with label structure. Show all posts
Friday, March 30, 2012
Monday, March 26, 2012
Invalid object name!
Hi,
I'm trying to create a new table by merging two files together. They both
have exactly the same table structure. I.e. they are both got 1 field called
ref varchar(255).
The code I'm using is:
INSERT U_T_XmasOnly(REF)
SELECT DISTINCT ref
FROM U_T_AttXmasOnly
UNION
SELECT DISTINCT ref
FROM U_T_BlkXmasOnly
The error message I'm getting is:
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name 'U_T_XmasOnly'.
Can you please tell me what I'm doing wrong?
Thanks in advance
RobRobert
I think you missed INTO within the INSERT statement
It shoul be
INSERT INTO U_T_XmasOnly(REF)
"Robert" <Robert@.discussions.microsoft.com> wrote in message
news:8C2270C4-0CC1-45BB-95D4-C4539A00C1BB@.microsoft.com...
> Hi,
> I'm trying to create a new table by merging two files together. They both
> have exactly the same table structure. I.e. they are both got 1 field
called
> ref varchar(255).
> The code I'm using is:
> INSERT U_T_XmasOnly(REF)
> SELECT DISTINCT ref
> FROM U_T_AttXmasOnly
> UNION
> SELECT DISTINCT ref
> FROM U_T_BlkXmasOnly
> The error message I'm getting is:
>
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name 'U_T_XmasOnly'.
> Can you please tell me what I'm doing wrong?
> Thanks in advance
> Rob|||The INTO is optional, so the INSERT statement is fine, as long as the table
already exists. Your object 'U_T_XmasOnly' musn't exist.
Looking at your statement "I'm trying to create a table" I think what you
want to do is this:
SELECT ref
INTO U_T_XmasOnly
FROM
(
SELECT DISTINCT ref
FROM U_T_AttXmasOnly
UNION
SELECT DISTINCT ref
FROM U_T_BlkXmasOnly
) x
But what you should really do is create your table first, then use the
INSERT syntax above:
eg
CREATE TABLE U_T_XmasOnly ( ref INT) -- other columns etc
INSERT U_T_XmasOnly(REF)
SELECT DISTINCT ref
FROM U_T_AttXmasOnly
UNION
SELECT DISTINCT ref
FROM U_T_BlkXmasOnly
Basically the syntax for adding records to an _existing_ table is the
INSERT, creating a table on they fly and adding records at the same time is
the SELECT INTO, and really you should create the table first, then add the
records, using the CREATE TABLE and INSERT.
Let me know how get on.
Damien
"Uri Dimant" wrote:
> Robert
> I think you missed INTO within the INSERT statement
> It shoul be
> INSERT INTO U_T_XmasOnly(REF)
> "Robert" <Robert@.discussions.microsoft.com> wrote in message
> news:8C2270C4-0CC1-45BB-95D4-C4539A00C1BB@.microsoft.com...
> called
>
>|||Hehehe, right , I have never thought about it.
"Damien" <Damien@.discussions.microsoft.com> wrote in message
news:45A4A9EE-A080-45AC-85E7-E3DC24EB2BD6@.microsoft.com...
> The INTO is optional, so the INSERT statement is fine, as long as the
table
> already exists. Your object 'U_T_XmasOnly' musn't exist.
> Looking at your statement "I'm trying to create a table" I think what you
> want to do is this:
> SELECT ref
> INTO U_T_XmasOnly
> FROM
> (
> SELECT DISTINCT ref
> FROM U_T_AttXmasOnly
> UNION
> SELECT DISTINCT ref
> FROM U_T_BlkXmasOnly
> ) x
> But what you should really do is create your table first, then use the
> INSERT syntax above:
> eg
> CREATE TABLE U_T_XmasOnly ( ref INT) -- other columns etc
> INSERT U_T_XmasOnly(REF)
> SELECT DISTINCT ref
> FROM U_T_AttXmasOnly
> UNION
> SELECT DISTINCT ref
> FROM U_T_BlkXmasOnly
> Basically the syntax for adding records to an _existing_ table is the
> INSERT, creating a table on they fly and adding records at the same time
is
> the SELECT INTO, and really you should create the table first, then add
the
> records, using the CREATE TABLE and INSERT.
> Let me know how get on.
>
> Damien
> "Uri Dimant" wrote:
>
both
I'm trying to create a new table by merging two files together. They both
have exactly the same table structure. I.e. they are both got 1 field called
ref varchar(255).
The code I'm using is:
INSERT U_T_XmasOnly(REF)
SELECT DISTINCT ref
FROM U_T_AttXmasOnly
UNION
SELECT DISTINCT ref
FROM U_T_BlkXmasOnly
The error message I'm getting is:
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name 'U_T_XmasOnly'.
Can you please tell me what I'm doing wrong?
Thanks in advance
RobRobert
I think you missed INTO within the INSERT statement
It shoul be
INSERT INTO U_T_XmasOnly(REF)
"Robert" <Robert@.discussions.microsoft.com> wrote in message
news:8C2270C4-0CC1-45BB-95D4-C4539A00C1BB@.microsoft.com...
> Hi,
> I'm trying to create a new table by merging two files together. They both
> have exactly the same table structure. I.e. they are both got 1 field
called
> ref varchar(255).
> The code I'm using is:
> INSERT U_T_XmasOnly(REF)
> SELECT DISTINCT ref
> FROM U_T_AttXmasOnly
> UNION
> SELECT DISTINCT ref
> FROM U_T_BlkXmasOnly
> The error message I'm getting is:
>
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name 'U_T_XmasOnly'.
> Can you please tell me what I'm doing wrong?
> Thanks in advance
> Rob|||The INTO is optional, so the INSERT statement is fine, as long as the table
already exists. Your object 'U_T_XmasOnly' musn't exist.
Looking at your statement "I'm trying to create a table" I think what you
want to do is this:
SELECT ref
INTO U_T_XmasOnly
FROM
(
SELECT DISTINCT ref
FROM U_T_AttXmasOnly
UNION
SELECT DISTINCT ref
FROM U_T_BlkXmasOnly
) x
But what you should really do is create your table first, then use the
INSERT syntax above:
eg
CREATE TABLE U_T_XmasOnly ( ref INT) -- other columns etc
INSERT U_T_XmasOnly(REF)
SELECT DISTINCT ref
FROM U_T_AttXmasOnly
UNION
SELECT DISTINCT ref
FROM U_T_BlkXmasOnly
Basically the syntax for adding records to an _existing_ table is the
INSERT, creating a table on they fly and adding records at the same time is
the SELECT INTO, and really you should create the table first, then add the
records, using the CREATE TABLE and INSERT.
Let me know how get on.
Damien
"Uri Dimant" wrote:
> Robert
> I think you missed INTO within the INSERT statement
> It shoul be
> INSERT INTO U_T_XmasOnly(REF)
> "Robert" <Robert@.discussions.microsoft.com> wrote in message
> news:8C2270C4-0CC1-45BB-95D4-C4539A00C1BB@.microsoft.com...
> called
>
>|||Hehehe, right , I have never thought about it.
"Damien" <Damien@.discussions.microsoft.com> wrote in message
news:45A4A9EE-A080-45AC-85E7-E3DC24EB2BD6@.microsoft.com...
> The INTO is optional, so the INSERT statement is fine, as long as the
table
> already exists. Your object 'U_T_XmasOnly' musn't exist.
> Looking at your statement "I'm trying to create a table" I think what you
> want to do is this:
> SELECT ref
> INTO U_T_XmasOnly
> FROM
> (
> SELECT DISTINCT ref
> FROM U_T_AttXmasOnly
> UNION
> SELECT DISTINCT ref
> FROM U_T_BlkXmasOnly
> ) x
> But what you should really do is create your table first, then use the
> INSERT syntax above:
> eg
> CREATE TABLE U_T_XmasOnly ( ref INT) -- other columns etc
> INSERT U_T_XmasOnly(REF)
> SELECT DISTINCT ref
> FROM U_T_AttXmasOnly
> UNION
> SELECT DISTINCT ref
> FROM U_T_BlkXmasOnly
> Basically the syntax for adding records to an _existing_ table is the
> INSERT, creating a table on they fly and adding records at the same time
is
> the SELECT INTO, and really you should create the table first, then add
the
> records, using the CREATE TABLE and INSERT.
> Let me know how get on.
>
> Damien
> "Uri Dimant" wrote:
>
both
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!
Subscribe to:
Posts (Atom)