combining datasets

I have two queries, one that brings back data from a cube and another that
returns records from a db. Is there anyway inside reporting services to
combine the two data sets?Only through subreports.
"Jessica C" <jesscobbe@.hotmail.com> wrote in message
news:ucK4AE02FHA.3272@.TK2MSFTNGP09.phx.gbl...
> I have two queries, one that brings back data from a cube and another that
> returns records from a db. Is there anyway inside reporting services to
> combine the two data sets?
>

COM Plus Catalog Requirement (Warning) When installing MS SQL SERVER 2005 ENTERPRISE ON WINDOWS

COM Plus Catalog Requirement (Warning)

Messages

COM Plus Catalog Requirement

If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.

Are you hitting this warning? Is it preventing you from installing?

Thanks,
Sam Lester (MSFT)|||

I'm getting the same thing when installing SQL Server 2005 Express (with advanced tools) on my Windows XP Pro setup. Recently installed Visual Studio 2005, but not the MSDE because was not recommended.

Is there a solution to this?

|||This article is the first hit on google when searching for a resolution to the com plus catalog requirement message. And it's also the most useless.

I was seeing this error message and this article fixed it for me;

http://msdn2.microsoft.com/en-us/library/ms143690.aspx
|||

i found the Sulosion its 100% Working The Msdb is on and he block the Com+ ports.

http://msdn2.microsoft.com/en-us/library/ms143698.aspx

get it.

Have a nice day and good luck

COM Plus Catalog Requirement (Warning) When installing MS SQL SERVER 2005 ENTERPRISE ON WINDOWS

COM Plus Catalog Requirement (Warning)

Messages

COM Plus Catalog Requirement

If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.

Are you hitting this warning? Is it preventing you from installing?

Thanks,
Sam Lester (MSFT)|||

I'm getting the same thing when installing SQL Server 2005 Express (with advanced tools) on my Windows XP Pro setup. Recently installed Visual Studio 2005, but not the MSDE because was not recommended.

Is there a solution to this?

|||This article is the first hit on google when searching for a resolution to the com plus catalog requirement message. And it's also the most useless.

I was seeing this error message and this article fixed it for me;

http://msdn2.microsoft.com/en-us/library/ms143690.aspx|||

i found the Sulosion its 100% Working The Msdb is on and he block the Com+ ports.

http://msdn2.microsoft.com/en-us/library/ms143698.aspx

get it.

Have a nice day and good luck

COM Plus Catalog Requirement (Warning) When installing MS SQL SERVER 2005 ENTERPRISE ON WIND

COM Plus Catalog Requirement (Warning)

Messages

COM Plus Catalog Requirement

If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.

Are you hitting this warning? Is it preventing you from installing?

Thanks,
Sam Lester (MSFT)|||

I'm getting the same thing when installing SQL Server 2005 Express (with advanced tools) on my Windows XP Pro setup. Recently installed Visual Studio 2005, but not the MSDE because was not recommended.

Is there a solution to this?

|||This article is the first hit on google when searching for a resolution to the com plus catalog requirement message. And it's also the most useless.

I was seeing this error message and this article fixed it for me;

http://msdn2.microsoft.com/en-us/library/ms143690.aspx|||

i found the Sulosion its 100% Working The Msdb is on and he block the Com+ ports.

http://msdn2.microsoft.com/en-us/library/ms143698.aspx

get it.

Have a nice day and good luck

COM Plus Catalog Requirement (Warning) When installing MS SQL SERVER 2005 ENTERPRISE ON WIND

COM Plus Catalog Requirement (Warning)

Messages

COM Plus Catalog Requirement

If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.

Are you hitting this warning? Is it preventing you from installing?

Thanks,
Sam Lester (MSFT)|||

I'm getting the same thing when installing SQL Server 2005 Express (with advanced tools) on my Windows XP Pro setup. Recently installed Visual Studio 2005, but not the MSDE because was not recommended.

Is there a solution to this?

|||This article is the first hit on google when searching for a resolution to the com plus catalog requirement message. And it's also the most useless.

I was seeing this error message and this article fixed it for me;

http://msdn2.microsoft.com/en-us/library/ms143690.aspx|||

i found the Sulosion its 100% Working The Msdb is on and he block the Com+ ports.

http://msdn2.microsoft.com/en-us/library/ms143698.aspx

get it.

Have a nice day and good luck

COM Plus Catalog Requirement (Warning) Com+ Failure SQL 2005 Express Bootstrap

- COM Plus Catalog Requirement (Warning)

Messages

COM Plus Catalog Requirement

If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.

Workaround says remove the .manifest files. Where are they?

SETUP CONTINUES TO FAIL

Hi,

I also encountered same problem.

The workaround is go to Add/Remove program, click on Add/Remove Windows component and click on the next button till end. This will reconfigure the windows component.

I did this on my server, and it worked.

Cheers,

Avi

|||

I too have the same problem and still doesn't work after going through Add/Remove Windows component steps. Very frustrating!

|||

Any solution ?

I am facing with the same problem

|||same to me, have the same error msg|||I'm having the same problem and cannot get around it ...|||

Check that the distributed transaction coordinator (MSDTC) service is started.

I had the same problem so I went to check the com+ applications on my computer (Control panel\administrative tools\Componant services\Computers\My Computer\Com+ Applications).

I could not open the "computers" folder and got an error indicating that MSDTC was not running. (I had disabled this service some time ago).

Upon starting MSDTC I was able to open the computers folder and check the COm+ applications.

Anyway, to cut a long story short, set MSDTC service to automatic, restart the SQL Server 2005 install and you should not get the error again.

|||I am having this problem, and MSDTC isn't even showing in the Services Control Panel. It's as if it's not installed. Any ideas on what I can try next? I know I could try reinstalling Windows XP, but I'd rather not.|||Add/Remove Windows Components -> Application Server -> Enable Network COM+ access

COM Plus Catalog Requirement (Warning) Com+ Failure SQL 2005 Express Bootstrap

- COM Plus Catalog Requirement (Warning)

Messages

COM Plus Catalog Requirement

If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.

Workaround says remove the .manifest files. Where are they?

SETUP CONTINUES TO FAIL

Hi,

I also encountered same problem.

The workaround is go to Add/Remove program, click on Add/Remove Windows component and click on the next button till end. This will reconfigure the windows component.

I did this on my server, and it worked.

Cheers,

Avi

|||

I too have the same problem and still doesn't work after going through Add/Remove Windows component steps. Very frustrating!

|||

Any solution ?

I am facing with the same problem

|||same to me, have the same error msg|||I'm having the same problem and cannot get around it ...|||

Check that the distributed transaction coordinator (MSDTC) service is started.

I had the same problem so I went to check the com+ applications on my computer (Control panel\administrative tools\Componant services\Computers\My Computer\Com+ Applications).

I could not open the "computers" folder and got an error indicating that MSDTC was not running. (I had disabled this service some time ago).

Upon starting MSDTC I was able to open the computers folder and check the COm+ applications.

Anyway, to cut a long story short, set MSDTC service to automatic, restart the SQL Server 2005 install and you should not get the error again.

|||I am having this problem, and MSDTC isn't even showing in the Services Control Panel. It's as if it's not installed. Any ideas on what I can try next? I know I could try reinstalling Windows XP, but I'd rather not.|||Add/Remove Windows Components -> Application Server -> Enable Network COM+ access

COM Plus Catalog Requirement (Warning) Com+ Failure SQL 2005 Express Bootstrap

- COM Plus Catalog Requirement (Warning)

Messages

COM Plus Catalog Requirement

If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.

Workaround says remove the .manifest files. Where are they?

SETUP CONTINUES TO FAIL

Hi,

I also encountered same problem.

The workaround is go to Add/Remove program, click on Add/Remove Windows component and click on the next button till end. This will reconfigure the windows component.

I did this on my server, and it worked.

Cheers,

Avi

|||

I too have the same problem and still doesn't work after going through Add/Remove Windows component steps. Very frustrating!

|||

Any solution ?

I am facing with the same problem

|||same to me, have the same error msg|||I'm having the same problem and cannot get around it ...|||

Check that the distributed transaction coordinator (MSDTC) service is started.

I had the same problem so I went to check the com+ applications on my computer (Control panel\administrative tools\Componant services\Computers\My Computer\Com+ Applications).

I could not open the "computers" folder and got an error indicating that MSDTC was not running. (I had disabled this service some time ago).

Upon starting MSDTC I was able to open the computers folder and check the COm+ applications.

Anyway, to cut a long story short, set MSDTC service to automatic, restart the SQL Server 2005 install and you should not get the error again.

|||I am having this problem, and MSDTC isn't even showing in the Services Control Panel. It's as if it's not installed. Any ideas on what I can try next? I know I could try reinstalling Windows XP, but I'd rather not.

COM Plus Catalog Requirement (Warning) Com+ Failure SQL 2005 Express Bootstrap

- COM Plus Catalog Requirement (Warning)

Messages

COM Plus Catalog Requirement

If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.

Workaround says remove the .manifest files. Where are they?

SETUP CONTINUES TO FAIL

Hi,

I also encountered same problem.

The workaround is go to Add/Remove program, click on Add/Remove Windows component and click on the next button till end. This will reconfigure the windows component.

I did this on my server, and it worked.

Cheers,

Avi

|||

I too have the same problem and still doesn't work after going through Add/Remove Windows component steps. Very frustrating!

|||

Any solution ?

I am facing with the same problem

|||same to me, have the same error msg|||I'm having the same problem and cannot get around it ...|||

Check that the distributed transaction coordinator (MSDTC) service is started.

I had the same problem so I went to check the com+ applications on my computer (Control panel\administrative tools\Componant services\Computers\My Computer\Com+ Applications).

I could not open the "computers" folder and got an error indicating that MSDTC was not running. (I had disabled this service some time ago).

Upon starting MSDTC I was able to open the computers folder and check the COm+ applications.

Anyway, to cut a long story short, set MSDTC service to automatic, restart the SQL Server 2005 install and you should not get the error again.

|||I am having this problem, and MSDTC isn't even showing in the Services Control Panel. It's as if it's not installed. Any ideas on what I can try next? I know I could try reinstalling Windows XP, but I'd rather not.

COM Plus Catalog Requirement (Warning) Com+ Failure SQL 2005 Express Bootstrap

- COM Plus Catalog Requirement (Warning)

Messages

COM Plus Catalog Requirement

If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.

Workaround says remove the .manifest files. Where are they?

SETUP CONTINUES TO FAIL

Hi,

I also encountered same problem.

The workaround is go to Add/Remove program, click on Add/Remove Windows component and click on the next button till end. This will reconfigure the windows component.

I did this on my server, and it worked.

Cheers,

Avi

|||

I too have the same problem and still doesn't work after going through Add/Remove Windows component steps. Very frustrating!

|||

Any solution ?

I am facing with the same problem

|||same to me, have the same error msg|||I'm having the same problem and cannot get around it ...|||

Check that the distributed transaction coordinator (MSDTC) service is started.

I had the same problem so I went to check the com+ applications on my computer (Control panel\administrative tools\Componant services\Computers\My Computer\Com+ Applications).

I could not open the "computers" folder and got an error indicating that MSDTC was not running. (I had disabled this service some time ago).

Upon starting MSDTC I was able to open the computers folder and check the COm+ applications.

Anyway, to cut a long story short, set MSDTC service to automatic, restart the SQL Server 2005 install and you should not get the error again.

|||I am having this problem, and MSDTC isn't even showing in the Services Control Panel. It's as if it's not installed. Any ideas on what I can try next? I know I could try reinstalling Windows XP, but I'd rather not.

COM Plus Catalog Requirement (Warning) Com+ Failure SQL 2005 Express Bootstrap

- COM Plus Catalog Requirement (Warning)

Messages

COM Plus Catalog Requirement

If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.

Workaround says remove the .manifest files. Where are they?

SETUP CONTINUES TO FAIL

Hi,

I also encountered same problem.

The workaround is go to Add/Remove program, click on Add/Remove Windows component and click on the next button till end. This will reconfigure the windows component.

I did this on my server, and it worked.

Cheers,

Avi

|||

I too have the same problem and still doesn't work after going through Add/Remove Windows component steps. Very frustrating!

|||

Any solution ?

I am facing with the same problem

|||same to me, have the same error msg|||I'm having the same problem and cannot get around it ...|||

Check that the distributed transaction coordinator (MSDTC) service is started.

I had the same problem so I went to check the com+ applications on my computer (Control panel\administrative tools\Componant services\Computers\My Computer\Com+ Applications).

I could not open the "computers" folder and got an error indicating that MSDTC was not running. (I had disabled this service some time ago).

Upon starting MSDTC I was able to open the computers folder and check the COm+ applications.

Anyway, to cut a long story short, set MSDTC service to automatic, restart the SQL Server 2005 install and you should not get the error again.

|||I am having this problem, and MSDTC isn't even showing in the Services Control Panel. It's as if it's not installed. Any ideas on what I can try next? I know I could try reinstalling Windows XP, but I'd rather not.

Column length changes back to default automatically

Why is it that when I create a varchar column in a table through the
SQL Server 2005 Management Studio and assign it a length of, say, 10,
when I tab to the next field, the length is changed back to 50? If I
return to the column type field and correct it, it works fine.Because there is a bug in Management Studio. It will be fixed at the latest
in SQL Server 2008; in the meantime, you will either have to live with it,
or use CREATE TABLE in a query window instead of the table designer (which
has about 50 other bugs, FWIW). Here are three issues relating to your
problem:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127135
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=278074
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125878
The last one suggests the bug was being considered for SP2, but I don't
think it made the bar. One of the others suggests that it has been fixed in
an early Katmai CTP. Have you updated your client tools to SP2 or better?
What does Help|About... in Management Studio tell you (the first row under
the Versions column)?
A
"Richard Carpenter" <rumbledor@.hotmail.com> wrote in message
news:61b0eefa-15f3-475c-b173-76bf35e77c50@.p73g2000hsd.googlegroups.com...
> Why is it that when I create a varchar column in a table through the
> SQL Server 2005 Management Studio and assign it a length of, say, 10,
> when I tab to the next field, the length is changed back to 50? If I
> return to the column type field and correct it, it works fine.
>|||I'm sure that's it, Aaron. This is a new install of the client tools,
and I have yet to update them with SP2.
Thanks!
--
Richard Carpenter
On Mar 19, 7:42=A0pm, "Aaron Bertrand [SQL Server MVP]"
<ten...@.dnartreb.noraa> wrote:
> Because there is a bug in Management Studio. =A0It will be fixed at the la=test
> in SQL Server 2008; in the meantime, you will either have to live with it,=
> or use CREATE TABLE in a query window instead of the table designer (which=
> has about 50 other bugs, FWIW). =A0Here are three issues relating to your
> problem:
> https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?Fe...
> https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?Fe...
> https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?Fe...
> The last one suggests the bug was being considered for SP2, but I don't
> think it made the bar. =A0One of the others suggests that it has been fixe=d in
> an early Katmai CTP. =A0Have you updated your client tools to SP2 or bette=r?
> What does Help|About... in Management Studio tell you (the first row under=
> the Versions column)?
> A
> "Richard Carpenter" <rumble...@.hotmail.com> wrote in message
> news:61b0eefa-15f3-475c-b173-76bf35e77c50@.p73g2000hsd.googlegroups.com...
>
> > Why is it that when I create a varchar column in a table through the
> > SQL Server 2005 Management Studio and assign it a length of, say, 10,
> > when I tab to the next field, the length is changed back to 50? If I
> > return to the column type field and correct it, it works fine.- Hide quo=ted text -
> - Show quoted text -|||Richard , I could not reproduce the bug , can you tell me what did you do
step by step?
"Richard Carpenter" <rumbledor@.hotmail.com> wrote in message
news:7dd431ea-206f-40d1-bab4-34850956501f@.m44g2000hsc.googlegroups.com...
I'm sure that's it, Aaron. This is a new install of the client tools,
and I have yet to update them with SP2.
Thanks!
--
Richard Carpenter
On Mar 19, 7:42 pm, "Aaron Bertrand [SQL Server MVP]"
<ten...@.dnartreb.noraa> wrote:
> Because there is a bug in Management Studio. It will be fixed at the
> latest
> in SQL Server 2008; in the meantime, you will either have to live with it,
> or use CREATE TABLE in a query window instead of the table designer (which
> has about 50 other bugs, FWIW). Here are three issues relating to your
> problem:
> https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?Fe...
> https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?Fe...
> https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?Fe...
> The last one suggests the bug was being considered for SP2, but I don't
> think it made the bar. One of the others suggests that it has been fixed
> in
> an early Katmai CTP. Have you updated your client tools to SP2 or better?
> What does Help|About... in Management Studio tell you (the first row under
> the Versions column)?
> A
> "Richard Carpenter" <rumble...@.hotmail.com> wrote in message
> news:61b0eefa-15f3-475c-b173-76bf35e77c50@.p73g2000hsd.googlegroups.com...
>
> > Why is it that when I create a varchar column in a table through the
> > SQL Server 2005 Management Studio and assign it a length of, say, 10,
> > when I tab to the next field, the length is changed back to 50? If I
> > return to the column type field and correct it, it works fine.- Hide
> > quoted text -
> - Show quoted text -|||Uri, I can reproduce this at will quite easily in Microsoft SQL Server
Management Studio 9.00.3042.00.
In any database, right-click "Tables" in Object Explorer, and select "New
Table..."
In Column Name type "foo", then hit Tab and in Data Type type "varchar(10)"
and hit Tab. varchar(10) should change to varchar(50).
A
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:e1Xc5ZmiIHA.5780@.TK2MSFTNGP06.phx.gbl...
> Richard , I could not reproduce the bug , can you tell me what did you do
> step by step?|||Thank you Aaron, I was able reproduce it too. As I see it is happening only
for the first time ( also Click change to varchar(50)) I mean if you go back
and change it again to VARCHAR(10) then SQL Server DOES save it, am I
right?
PS. Microsoft SQL Server Management Studio 9.00.3042.00.
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:eVHhfqoiIHA.4436@.TK2MSFTNGP02.phx.gbl...
> Uri, I can reproduce this at will quite easily in Microsoft SQL Server
> Management Studio 9.00.3042.00.
> In any database, right-click "Tables" in Object Explorer, and select "New
> Table..."
> In Column Name type "foo", then hit Tab and in Data Type type
> "varchar(10)" and hit Tab. varchar(10) should change to varchar(50).
> A
>
>
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:e1Xc5ZmiIHA.5780@.TK2MSFTNGP06.phx.gbl...
>> Richard , I could not reproduce the bug , can you tell me what did you do
>> step by step?
>|||> Thank you Aaron, I was able reproduce it too. As I see it is happening
> only for the first time ( also Click change to varchar(50)) I mean if you
> go back and change it again to VARCHAR(10) then SQL Server DOES save it,
> am I right?
Yes, that seems right. But the user shouldn't have to override (50) twice.|||> Yes, that seems right. But the user shouldn't have to override (50)
> twice.
100% , I hope to see they fixed it in SP3 , I so hope......
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:upTjzwoiIHA.2304@.TK2MSFTNGP05.phx.gbl...
>> Thank you Aaron, I was able reproduce it too. As I see it is happening
>> only for the first time ( also Click change to varchar(50)) I mean if you
>> go back and change it again to VARCHAR(10) then SQL Server DOES save it,
>> am I right?
> Yes, that seems right. But the user shouldn't have to override (50)
> twice.
>

Column length changes back to default automatically

Why is it that when I create a varchar column in a table through the
SQL Server 2005 Management Studio and assign it a length of, say, 10,
when I tab to the next field, the length is changed back to 50? If I
return to the column type field and correct it, it works fine.
Because there is a bug in Management Studio. It will be fixed at the latest
in SQL Server 2008; in the meantime, you will either have to live with it,
or use CREATE TABLE in a query window instead of the table designer (which
has about 50 other bugs, FWIW). Here are three issues relating to your
problem:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127135
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=278074
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125878
The last one suggests the bug was being considered for SP2, but I don't
think it made the bar. One of the others suggests that it has been fixed in
an early Katmai CTP. Have you updated your client tools to SP2 or better?
What does Help|About... in Management Studio tell you (the first row under
the Versions column)?
A
"Richard Carpenter" <rumbledor@.hotmail.com> wrote in message
news:61b0eefa-15f3-475c-b173-76bf35e77c50@.p73g2000hsd.googlegroups.com...
> Why is it that when I create a varchar column in a table through the
> SQL Server 2005 Management Studio and assign it a length of, say, 10,
> when I tab to the next field, the length is changed back to 50? If I
> return to the column type field and correct it, it works fine.
>
|||I'm sure that's it, Aaron. This is a new install of the client tools,
and I have yet to update them with SP2.
Thanks!
Richard Carpenter
On Mar 19, 7:42Xpm, "Aaron Bertrand [SQL Server MVP]"
<ten...@.dnartreb.noraa> wrote:
> Because there is a bug in Management Studio. XIt will be fixed at the latest
> in SQL Server 2008; in the meantime, you will either have to live with it,
> or use CREATE TABLE in a query window instead of the table designer (which
> has about 50 other bugs, FWIW). XHere are three issues relating to your
> problem:
> https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?Fe...
> https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?Fe...
> https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?Fe...
> The last one suggests the bug was being considered for SP2, but I don't
> think it made the bar. XOne of the others suggests that it has been fixed in
> an early Katmai CTP. XHave you updated your client tools to SP2 or better?
> What does Help|About... in Management Studio tell you (the first row under
> the Versions column)?
> A
> "Richard Carpenter" <rumble...@.hotmail.com> wrote in message
> news:61b0eefa-15f3-475c-b173-76bf35e77c50@.p73g2000hsd.googlegroups.com...
>
>
> - Show quoted text -
|||Richard , I could not reproduce the bug , can you tell me what did you do
step by step?
"Richard Carpenter" <rumbledor@.hotmail.com> wrote in message
news:7dd431ea-206f-40d1-bab4-34850956501f@.m44g2000hsc.googlegroups.com...
I'm sure that's it, Aaron. This is a new install of the client tools,
and I have yet to update them with SP2.
Thanks!
Richard Carpenter
On Mar 19, 7:42 pm, "Aaron Bertrand [SQL Server MVP]"
<ten...@.dnartreb.noraa> wrote:
> Because there is a bug in Management Studio. It will be fixed at the
> latest
> in SQL Server 2008; in the meantime, you will either have to live with it,
> or use CREATE TABLE in a query window instead of the table designer (which
> has about 50 other bugs, FWIW). Here are three issues relating to your
> problem:
> https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?Fe...
> https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?Fe...
> https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?Fe...
> The last one suggests the bug was being considered for SP2, but I don't
> think it made the bar. One of the others suggests that it has been fixed
> in
> an early Katmai CTP. Have you updated your client tools to SP2 or better?
> What does Help|About... in Management Studio tell you (the first row under
> the Versions column)?
> A
> "Richard Carpenter" <rumble...@.hotmail.com> wrote in message
> news:61b0eefa-15f3-475c-b173-76bf35e77c50@.p73g2000hsd.googlegroups.com...
>
>
> - Show quoted text -
|||Uri, I can reproduce this at will quite easily in Microsoft SQL Server
Management Studio 9.00.3042.00.
In any database, right-click "Tables" in Object Explorer, and select "New
Table..."
In Column Name type "foo", then hit Tab and in Data Type type "varchar(10)"
and hit Tab. varchar(10) should change to varchar(50).
A
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:e1Xc5ZmiIHA.5780@.TK2MSFTNGP06.phx.gbl...
> Richard , I could not reproduce the bug , can you tell me what did you do
> step by step?
|||Thank you Aaron, I was able reproduce it too. As I see it is happening only
for the first time ( also Click change to varchar(50)) I mean if you go back
and change it again to VARCHAR(10) then SQL Server DOES save it, am I
right?
PS. Microsoft SQL Server Management Studio 9.00.3042.00.
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:eVHhfqoiIHA.4436@.TK2MSFTNGP02.phx.gbl...
> Uri, I can reproduce this at will quite easily in Microsoft SQL Server
> Management Studio 9.00.3042.00.
> In any database, right-click "Tables" in Object Explorer, and select "New
> Table..."
> In Column Name type "foo", then hit Tab and in Data Type type
> "varchar(10)" and hit Tab. varchar(10) should change to varchar(50).
> A
>
>
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:e1Xc5ZmiIHA.5780@.TK2MSFTNGP06.phx.gbl...
>
|||> Thank you Aaron, I was able reproduce it too. As I see it is happening
> only for the first time ( also Click change to varchar(50)) I mean if you
> go back and change it again to VARCHAR(10) then SQL Server DOES save it,
> am I right?
Yes, that seems right. But the user shouldn't have to override (50) twice.
|||> Yes, that seems right. But the user shouldn't have to override (50)
> twice.
100% , I hope to see they fixed it in SP3 , I so hope......
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:upTjzwoiIHA.2304@.TK2MSFTNGP05.phx.gbl...
> Yes, that seems right. But the user shouldn't have to override (50)
> twice.
>