I'm testing out the SQL Server 2005 filegroup for Text/Image Filegroup.
Problem:
I created a table and gave the properties "Text/Image Filegroup" the
value of the secondary filegroup, gave the properties "Filegroup or
Partition Scheme Name" the value of primary file group. After I save
it. Then I open it for edit again, the value of the properties
"Text/Image Filegroup" was not showing secondary, instead, it show
primary.
I'd try a few times to change it, from primary to secondary, then save.
After that open for modify again, it still revert back to primary
filegroup. Seems like the changes I made to that particular properties
can't be saved.
Anyone can help?
Thanks in advance.
wodoy.peter
Hi
"wodoy.peter" wrote:
> I'm testing out the SQL Server 2005 filegroup for Text/Image Filegroup.
>
Which version of SQL 2005 are you using?
> Problem:
> I created a table and gave the properties "Text/Image Filegroup" the
> value of the secondary filegroup, gave the properties "Filegroup or
> Partition Scheme Name" the value of primary file group. After I save
> it. Then I open it for edit again, the value of the properties
> "Text/Image Filegroup" was not showing secondary, instead, it show
> primary.
I assume this was through SSMS? As far as I can see there is not a way of
specify a different location for an image column is to script the table.
Where were you changing it? Table properties for text filegroup is readonly
in SSMS (on my version (SP1))
> I'd try a few times to change it, from primary to secondary, then save.
> After that open for modify again, it still revert back to primary
> filegroup. Seems like the changes I made to that particular properties
> can't be saved.
Creating the table with T-SQL seems to be ok!
> Anyone can help?
> Thanks in advance.
>
> wodoy.peter
>
John
|||I'm using SQL Server 2005 SP1 developer edition.
The complete version name and number: Microsoft SQL Server 2005 -
9.00.2047.00
Is there any reason behind MS make the properties editable in user
interface only, but infact, it can't be saved/changed through the
SSMS?
wodoy.peter
On Jan 28, 2:26 am, John Bell <jbellnewspo...@.hotmail.com> wrote:[vbcol=seagreen]
> Hi
> "wodoy.peter" wrote:
> specify a different location for an image column is to script the table.
> Where were you changing it? Table properties for text filegroup is readonly
> in SSMS (on my version (SP1))
>
>
>
>
|||Hi
"wodoy.peter" wrote:
> I'm using SQL Server 2005 SP1 developer edition.
> The complete version name and number: Microsoft SQL Server 2005 -
> 9.00.2047.00
> Is there any reason behind MS make the properties editable in user
> interface only, but infact, it can't be saved/changed through the
> SSMS?
This would be one for the program group! I would guess one reason would be
because once the table has data it would be a very expensive thing to change
which could cause severe problems. But then if there is no data in the table
I don't see why it can't be changed. You may want to log this at
https://connect.microsoft.com/SQLServer/Feedback
John
|||Thanks.
On Jan 28, 4:06 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> "wodoy.peter" wrote:
> because once the table has data it would be a very expensive thing to change
> which could cause severe problems. But then if there is no data in the table
> I don't see why it can't be changed. You may want to log this athttps://connect.microsoft.com/SQLServer/Feedback
> John
Showing posts with label properties. Show all posts
Showing posts with label properties. Show all posts
Friday, March 30, 2012
Modified image filegroup never get saved
I'm testing out the SQL Server 2005 filegroup for Text/Image Filegroup.
Problem:
I created a table and gave the properties "Text/Image Filegroup" the
value of the secondary filegroup, gave the properties "Filegroup or
Partition Scheme Name" the value of primary file group. After I save
it. Then I open it for edit again, the value of the properties
"Text/Image Filegroup" was not showing secondary, instead, it show
primary.
I'd try a few times to change it, from primary to secondary, then save.
After that open for modify again, it still revert back to primary
filegroup. Seems like the changes I made to that particular properties
can't be saved.
Anyone can help?
Thanks in advance.
wodoy.peterHi
"wodoy.peter" wrote:
> I'm testing out the SQL Server 2005 filegroup for Text/Image Filegroup.
>
Which version of SQL 2005 are you using?
> Problem:
> I created a table and gave the properties "Text/Image Filegroup" the
> value of the secondary filegroup, gave the properties "Filegroup or
> Partition Scheme Name" the value of primary file group. After I save
> it. Then I open it for edit again, the value of the properties
> "Text/Image Filegroup" was not showing secondary, instead, it show
> primary.
I assume this was through SSMS? As far as I can see there is not a way of
specify a different location for an image column is to script the table.
Where were you changing it? Table properties for text filegroup is readonly
in SSMS (on my version (SP1))
> I'd try a few times to change it, from primary to secondary, then save.
> After that open for modify again, it still revert back to primary
> filegroup. Seems like the changes I made to that particular properties
> can't be saved.
Creating the table with T-SQL seems to be ok!
> Anyone can help?
> Thanks in advance.
>
> wodoy.peter
>
John|||I'm using SQL Server 2005 SP1 developer edition.
The complete version name and number: Microsoft SQL Server 2005 -
9.00.2047.00
Is there any reason behind MS make the properties editable in user
interface only, but infact, it can't be saved/changed through the
SSMS?
wodoy.peter
On Jan 28, 2:26 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> "wodoy.peter" wrote:
> > I'm testing out the SQL Server 2005 filegroup for Text/Image Filegroup.Which version of SQL 2005 are you using?
> > Problem:
> > I created a table and gave the properties "Text/Image Filegroup" the
> > value of the secondary filegroup, gave the properties "Filegroup or
> > Partition Scheme Name" the value of primary file group. After I save
> > it. Then I open it for edit again, the value of the properties
> > "Text/Image Filegroup" was not showing secondary, instead, it show
> > primary.I assume this was through SSMS? As far as I can see there is not a way of
> specify a different location for an image column is to script the table.
> Where were you changing it? Table properties for text filegroup is readonly
> in SSMS (on my version (SP1))
>
> > I'd try a few times to change it, from primary to secondary, then save.
> > After that open for modify again, it still revert back to primary
> > filegroup. Seems like the changes I made to that particular properties
> > can't be saved.Creating the table with T-SQL seems to be ok!
>
> > Anyone can help?
> > Thanks in advance.
> > wodoy.peterJohn|||Hi
"wodoy.peter" wrote:
> I'm using SQL Server 2005 SP1 developer edition.
> The complete version name and number: Microsoft SQL Server 2005 -
> 9.00.2047.00
> Is there any reason behind MS make the properties editable in user
> interface only, but infact, it can't be saved/changed through the
> SSMS?
This would be one for the program group! I would guess one reason would be
because once the table has data it would be a very expensive thing to change
which could cause severe problems. But then if there is no data in the table
I don't see why it can't be changed. You may want to log this at
https://connect.microsoft.com/SQLServer/Feedback
John|||Thanks.
On Jan 28, 4:06 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> "wodoy.peter" wrote:
> > I'm using SQL Server 2005 SP1 developer edition.
> > The complete version name and number: Microsoft SQL Server 2005 -
> > 9.00.2047.00
> > Is there any reason behind MS make the properties editable in user
> > interface only, but infact, it can't be saved/changed through the
> > SSMS?This would be one for the program group! I would guess one reason would be
> because once the table has data it would be a very expensive thing to change
> which could cause severe problems. But then if there is no data in the table
> I don't see why it can't be changed. You may want to log this athttps://connect.microsoft.com/SQLServer/Feedback
> John
Problem:
I created a table and gave the properties "Text/Image Filegroup" the
value of the secondary filegroup, gave the properties "Filegroup or
Partition Scheme Name" the value of primary file group. After I save
it. Then I open it for edit again, the value of the properties
"Text/Image Filegroup" was not showing secondary, instead, it show
primary.
I'd try a few times to change it, from primary to secondary, then save.
After that open for modify again, it still revert back to primary
filegroup. Seems like the changes I made to that particular properties
can't be saved.
Anyone can help?
Thanks in advance.
wodoy.peterHi
"wodoy.peter" wrote:
> I'm testing out the SQL Server 2005 filegroup for Text/Image Filegroup.
>
Which version of SQL 2005 are you using?
> Problem:
> I created a table and gave the properties "Text/Image Filegroup" the
> value of the secondary filegroup, gave the properties "Filegroup or
> Partition Scheme Name" the value of primary file group. After I save
> it. Then I open it for edit again, the value of the properties
> "Text/Image Filegroup" was not showing secondary, instead, it show
> primary.
I assume this was through SSMS? As far as I can see there is not a way of
specify a different location for an image column is to script the table.
Where were you changing it? Table properties for text filegroup is readonly
in SSMS (on my version (SP1))
> I'd try a few times to change it, from primary to secondary, then save.
> After that open for modify again, it still revert back to primary
> filegroup. Seems like the changes I made to that particular properties
> can't be saved.
Creating the table with T-SQL seems to be ok!
> Anyone can help?
> Thanks in advance.
>
> wodoy.peter
>
John|||I'm using SQL Server 2005 SP1 developer edition.
The complete version name and number: Microsoft SQL Server 2005 -
9.00.2047.00
Is there any reason behind MS make the properties editable in user
interface only, but infact, it can't be saved/changed through the
SSMS?
wodoy.peter
On Jan 28, 2:26 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> "wodoy.peter" wrote:
> > I'm testing out the SQL Server 2005 filegroup for Text/Image Filegroup.Which version of SQL 2005 are you using?
> > Problem:
> > I created a table and gave the properties "Text/Image Filegroup" the
> > value of the secondary filegroup, gave the properties "Filegroup or
> > Partition Scheme Name" the value of primary file group. After I save
> > it. Then I open it for edit again, the value of the properties
> > "Text/Image Filegroup" was not showing secondary, instead, it show
> > primary.I assume this was through SSMS? As far as I can see there is not a way of
> specify a different location for an image column is to script the table.
> Where were you changing it? Table properties for text filegroup is readonly
> in SSMS (on my version (SP1))
>
> > I'd try a few times to change it, from primary to secondary, then save.
> > After that open for modify again, it still revert back to primary
> > filegroup. Seems like the changes I made to that particular properties
> > can't be saved.Creating the table with T-SQL seems to be ok!
>
> > Anyone can help?
> > Thanks in advance.
> > wodoy.peterJohn|||Hi
"wodoy.peter" wrote:
> I'm using SQL Server 2005 SP1 developer edition.
> The complete version name and number: Microsoft SQL Server 2005 -
> 9.00.2047.00
> Is there any reason behind MS make the properties editable in user
> interface only, but infact, it can't be saved/changed through the
> SSMS?
This would be one for the program group! I would guess one reason would be
because once the table has data it would be a very expensive thing to change
which could cause severe problems. But then if there is no data in the table
I don't see why it can't be changed. You may want to log this at
https://connect.microsoft.com/SQLServer/Feedback
John|||Thanks.
On Jan 28, 4:06 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> "wodoy.peter" wrote:
> > I'm using SQL Server 2005 SP1 developer edition.
> > The complete version name and number: Microsoft SQL Server 2005 -
> > 9.00.2047.00
> > Is there any reason behind MS make the properties editable in user
> > interface only, but infact, it can't be saved/changed through the
> > SSMS?This would be one for the program group! I would guess one reason would be
> because once the table has data it would be a very expensive thing to change
> which could cause severe problems. But then if there is no data in the table
> I don't see why it can't be changed. You may want to log this athttps://connect.microsoft.com/SQLServer/Feedback
> John
Modified image filegroup never get saved
I'm testing out the SQL Server 2005 filegroup for Text/Image Filegroup.
Problem:
I created a table and gave the properties "Text/Image Filegroup" the
value of the secondary filegroup, gave the properties "Filegroup or
Partition Scheme Name" the value of primary file group. After I save
it. Then I open it for edit again, the value of the properties
"Text/Image Filegroup" was not showing secondary, instead, it show
primary.
I'd try a few times to change it, from primary to secondary, then save.
After that open for modify again, it still revert back to primary
filegroup. Seems like the changes I made to that particular properties
can't be saved.
Anyone can help?
Thanks in advance.
wodoy.peterHi
"wodoy.peter" wrote:
> I'm testing out the SQL Server 2005 filegroup for Text/Image Filegroup.
>
Which version of SQL 2005 are you using?
> Problem:
> I created a table and gave the properties "Text/Image Filegroup" the
> value of the secondary filegroup, gave the properties "Filegroup or
> Partition Scheme Name" the value of primary file group. After I save
> it. Then I open it for edit again, the value of the properties
> "Text/Image Filegroup" was not showing secondary, instead, it show
> primary.
I assume this was through SSMS? As far as I can see there is not a way of
specify a different location for an image column is to script the table.
Where were you changing it? Table properties for text filegroup is readonly
in SSMS (on my version (SP1))
> I'd try a few times to change it, from primary to secondary, then save.
> After that open for modify again, it still revert back to primary
> filegroup. Seems like the changes I made to that particular properties
> can't be saved.
Creating the table with T-SQL seems to be ok!
> Anyone can help?
> Thanks in advance.
>
> wodoy.peter
>
John|||I'm using SQL Server 2005 SP1 developer edition.
The complete version name and number: Microsoft SQL Server 2005 -
9.00.2047.00
Is there any reason behind MS make the properties editable in user
interface only, but infact, it can't be saved/changed through the
SSMS?
wodoy.peter
On Jan 28, 2:26 am, John Bell <jbellnewspo...@.hotmail.com> wrote:[vbcol=seagreen]
> Hi
> "wodoy.peter" wrote:
>
> specify a different location for an image column is to script the table.
> Where were you changing it? Table properties for text filegroup is readonl
y
> in SSMS (on my version (SP1))
>
>
>
>
>
>|||Hi
"wodoy.peter" wrote:
> I'm using SQL Server 2005 SP1 developer edition.
> The complete version name and number: Microsoft SQL Server 2005 -
> 9.00.2047.00
> Is there any reason behind MS make the properties editable in user
> interface only, but infact, it can't be saved/changed through the
> SSMS?
This would be one for the program group! I would guess one reason would be
because once the table has data it would be a very expensive thing to change
which could cause severe problems. But then if there is no data in the table
I don't see why it can't be changed. You may want to log this at
https://connect.microsoft.com/SQLServer/Feedback
John|||Thanks.
On Jan 28, 4:06 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> "wodoy.peter" wrote:
>
> because once the table has data it would be a very expensive thing to chan
ge
> which could cause severe problems. But then if there is no data in the tab
le
> I don't see why it can't be changed. You may want to log this athttps://co
nnect.microsoft.com/SQLServer/Feedback
> John
Problem:
I created a table and gave the properties "Text/Image Filegroup" the
value of the secondary filegroup, gave the properties "Filegroup or
Partition Scheme Name" the value of primary file group. After I save
it. Then I open it for edit again, the value of the properties
"Text/Image Filegroup" was not showing secondary, instead, it show
primary.
I'd try a few times to change it, from primary to secondary, then save.
After that open for modify again, it still revert back to primary
filegroup. Seems like the changes I made to that particular properties
can't be saved.
Anyone can help?
Thanks in advance.
wodoy.peterHi
"wodoy.peter" wrote:
> I'm testing out the SQL Server 2005 filegroup for Text/Image Filegroup.
>
Which version of SQL 2005 are you using?
> Problem:
> I created a table and gave the properties "Text/Image Filegroup" the
> value of the secondary filegroup, gave the properties "Filegroup or
> Partition Scheme Name" the value of primary file group. After I save
> it. Then I open it for edit again, the value of the properties
> "Text/Image Filegroup" was not showing secondary, instead, it show
> primary.
I assume this was through SSMS? As far as I can see there is not a way of
specify a different location for an image column is to script the table.
Where were you changing it? Table properties for text filegroup is readonly
in SSMS (on my version (SP1))
> I'd try a few times to change it, from primary to secondary, then save.
> After that open for modify again, it still revert back to primary
> filegroup. Seems like the changes I made to that particular properties
> can't be saved.
Creating the table with T-SQL seems to be ok!
> Anyone can help?
> Thanks in advance.
>
> wodoy.peter
>
John|||I'm using SQL Server 2005 SP1 developer edition.
The complete version name and number: Microsoft SQL Server 2005 -
9.00.2047.00
Is there any reason behind MS make the properties editable in user
interface only, but infact, it can't be saved/changed through the
SSMS?
wodoy.peter
On Jan 28, 2:26 am, John Bell <jbellnewspo...@.hotmail.com> wrote:[vbcol=seagreen]
> Hi
> "wodoy.peter" wrote:
>
> specify a different location for an image column is to script the table.
> Where were you changing it? Table properties for text filegroup is readonl
y
> in SSMS (on my version (SP1))
>
>
>
>
>
>|||Hi
"wodoy.peter" wrote:
> I'm using SQL Server 2005 SP1 developer edition.
> The complete version name and number: Microsoft SQL Server 2005 -
> 9.00.2047.00
> Is there any reason behind MS make the properties editable in user
> interface only, but infact, it can't be saved/changed through the
> SSMS?
This would be one for the program group! I would guess one reason would be
because once the table has data it would be a very expensive thing to change
which could cause severe problems. But then if there is no data in the table
I don't see why it can't be changed. You may want to log this at
https://connect.microsoft.com/SQLServer/Feedback
John|||Thanks.
On Jan 28, 4:06 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
> "wodoy.peter" wrote:
>
> because once the table has data it would be a very expensive thing to chan
ge
> which could cause severe problems. But then if there is no data in the tab
le
> I don't see why it can't be changed. You may want to log this athttps://co
nnect.microsoft.com/SQLServer/Feedback
> John
Friday, March 23, 2012
MMC DataBase Properties Error
Hello.
In SQL Server 2000, when I right click on a database and then select
Properties,
I receive the following error message: "Microsoft Management Console has
encountered a problem and needs to close".
I tried a couple of databases with the same results and also rebooted but
that didn't resolve the issue.
Any suggestions will be greatly appreciated :-)
Rita
On May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> Hello.
> In SQL Server 2000, when I right click on a database and then select
> Properties,
> I receive the following error message: "Microsoft Management Console has
> encountered a problem and needs to close".
> I tried a couple of databases with the same results and also rebooted but
> that didn't resolve the issue.
> Any suggestions will be greatly appreciated :-)
> Rita
You may need to uninstall and reinstall client tools if the databases
are fine. This has happened to me and I was working with client tools
on my desktop viewing a registered server instance. I never found out
the issue, but reinstalling the client tools did the trick.
Hope this helps.
Kristina
|||Thanks so much Kristina - I'm going to try that now!
"Kristina" wrote:
> On May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> You may need to uninstall and reinstall client tools if the databases
> are fine. This has happened to me and I was working with client tools
> on my desktop viewing a registered server instance. I never found out
> the issue, but reinstalling the client tools did the trick.
> Hope this helps.
> Kristina
>
In SQL Server 2000, when I right click on a database and then select
Properties,
I receive the following error message: "Microsoft Management Console has
encountered a problem and needs to close".
I tried a couple of databases with the same results and also rebooted but
that didn't resolve the issue.
Any suggestions will be greatly appreciated :-)
Rita
On May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> Hello.
> In SQL Server 2000, when I right click on a database and then select
> Properties,
> I receive the following error message: "Microsoft Management Console has
> encountered a problem and needs to close".
> I tried a couple of databases with the same results and also rebooted but
> that didn't resolve the issue.
> Any suggestions will be greatly appreciated :-)
> Rita
You may need to uninstall and reinstall client tools if the databases
are fine. This has happened to me and I was working with client tools
on my desktop viewing a registered server instance. I never found out
the issue, but reinstalling the client tools did the trick.
Hope this helps.
Kristina
|||Thanks so much Kristina - I'm going to try that now!
"Kristina" wrote:
> On May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> You may need to uninstall and reinstall client tools if the databases
> are fine. This has happened to me and I was working with client tools
> on my desktop viewing a registered server instance. I never found out
> the issue, but reinstalling the client tools did the trick.
> Hope this helps.
> Kristina
>
MMC DataBase Properties Error
Hello.
In SQL Server 2000, when I right click on a database and then select
Properties,
I receive the following error message: "Microsoft Management Console has
encountered a problem and needs to close".
I tried a couple of databases with the same results and also rebooted but
that didn't resolve the issue.
Any suggestions will be greatly appreciated :-)
RitaOn May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> Hello.
> In SQL Server 2000, when I right click on a database and then select
> Properties,
> I receive the following error message: "Microsoft Management Console has
> encountered a problem and needs to close".
> I tried a couple of databases with the same results and also rebooted but
> that didn't resolve the issue.
> Any suggestions will be greatly appreciated :-)
> Rita
You may need to uninstall and reinstall client tools if the databases
are fine. This has happened to me and I was working with client tools
on my desktop viewing a registered server instance. I never found out
the issue, but reinstalling the client tools did the trick.
Hope this helps.
Kristina|||Thanks so much Kristina - I'm going to try that now!
"Kristina" wrote:
> On May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> > Hello.
> >
> > In SQL Server 2000, when I right click on a database and then select
> > Properties,
> > I receive the following error message: "Microsoft Management Console has
> > encountered a problem and needs to close".
> >
> > I tried a couple of databases with the same results and also rebooted but
> > that didn't resolve the issue.
> >
> > Any suggestions will be greatly appreciated :-)
> >
> > Rita
> You may need to uninstall and reinstall client tools if the databases
> are fine. This has happened to me and I was working with client tools
> on my desktop viewing a registered server instance. I never found out
> the issue, but reinstalling the client tools did the trick.
> Hope this helps.
> Kristina
>
In SQL Server 2000, when I right click on a database and then select
Properties,
I receive the following error message: "Microsoft Management Console has
encountered a problem and needs to close".
I tried a couple of databases with the same results and also rebooted but
that didn't resolve the issue.
Any suggestions will be greatly appreciated :-)
RitaOn May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> Hello.
> In SQL Server 2000, when I right click on a database and then select
> Properties,
> I receive the following error message: "Microsoft Management Console has
> encountered a problem and needs to close".
> I tried a couple of databases with the same results and also rebooted but
> that didn't resolve the issue.
> Any suggestions will be greatly appreciated :-)
> Rita
You may need to uninstall and reinstall client tools if the databases
are fine. This has happened to me and I was working with client tools
on my desktop viewing a registered server instance. I never found out
the issue, but reinstalling the client tools did the trick.
Hope this helps.
Kristina|||Thanks so much Kristina - I'm going to try that now!
"Kristina" wrote:
> On May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> > Hello.
> >
> > In SQL Server 2000, when I right click on a database and then select
> > Properties,
> > I receive the following error message: "Microsoft Management Console has
> > encountered a problem and needs to close".
> >
> > I tried a couple of databases with the same results and also rebooted but
> > that didn't resolve the issue.
> >
> > Any suggestions will be greatly appreciated :-)
> >
> > Rita
> You may need to uninstall and reinstall client tools if the databases
> are fine. This has happened to me and I was working with client tools
> on my desktop viewing a registered server instance. I never found out
> the issue, but reinstalling the client tools did the trick.
> Hope this helps.
> Kristina
>
MMC DataBase Properties Error
Hello.
In SQL Server 2000, when I right click on a database and then select
Properties,
I receive the following error message: "Microsoft Management Console has
encountered a problem and needs to close".
I tried a couple of databases with the same results and also rebooted but
that didn't resolve the issue.
Any suggestions will be greatly appreciated :-)
RitaOn May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> Hello.
> In SQL Server 2000, when I right click on a database and then select
> Properties,
> I receive the following error message: "Microsoft Management Console has
> encountered a problem and needs to close".
> I tried a couple of databases with the same results and also rebooted but
> that didn't resolve the issue.
> Any suggestions will be greatly appreciated :-)
> Rita
You may need to uninstall and reinstall client tools if the databases
are fine. This has happened to me and I was working with client tools
on my desktop viewing a registered server instance. I never found out
the issue, but reinstalling the client tools did the trick.
Hope this helps.
Kristina|||Thanks so much Kristina - I'm going to try that now!
"Kristina" wrote:
> On May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> You may need to uninstall and reinstall client tools if the databases
> are fine. This has happened to me and I was working with client tools
> on my desktop viewing a registered server instance. I never found out
> the issue, but reinstalling the client tools did the trick.
> Hope this helps.
> Kristina
>sql
In SQL Server 2000, when I right click on a database and then select
Properties,
I receive the following error message: "Microsoft Management Console has
encountered a problem and needs to close".
I tried a couple of databases with the same results and also rebooted but
that didn't resolve the issue.
Any suggestions will be greatly appreciated :-)
RitaOn May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> Hello.
> In SQL Server 2000, when I right click on a database and then select
> Properties,
> I receive the following error message: "Microsoft Management Console has
> encountered a problem and needs to close".
> I tried a couple of databases with the same results and also rebooted but
> that didn't resolve the issue.
> Any suggestions will be greatly appreciated :-)
> Rita
You may need to uninstall and reinstall client tools if the databases
are fine. This has happened to me and I was working with client tools
on my desktop viewing a registered server instance. I never found out
the issue, but reinstalling the client tools did the trick.
Hope this helps.
Kristina|||Thanks so much Kristina - I'm going to try that now!
"Kristina" wrote:
> On May 18, 5:19 pm, RitaG <R...@.discussions.microsoft.com> wrote:
> You may need to uninstall and reinstall client tools if the databases
> are fine. This has happened to me and I was working with client tools
> on my desktop viewing a registered server instance. I never found out
> the issue, but reinstalling the client tools did the trick.
> Hope this helps.
> Kristina
>sql
Wednesday, March 21, 2012
Mixed mode security
Hello all,
I'm trying to modify the security setting for a local install to m ake
it mixed mode, but in the SQL Server properties window I select SQL
Server and Windows then press OK, but the window doesn't close and it
won't let me save the settings. Why is this? Can anyone help?
Thanks,
JonIt would help if you specify the version and editions
"Jon" <JonMYates@.gmail.com> wrote in message
news:1191402457.786282.106960@.57g2000hsv.googlegroups.com...
> Hello all,
> I'm trying to modify the security setting for a local install to m ake
> it mixed mode, but in the SQL Server properties window I select SQL
> Server and Windows then press OK, but the window doesn't close and it
> won't let me save the settings. Why is this? Can anyone help?
> Thanks,
> Jon
>sql
I'm trying to modify the security setting for a local install to m ake
it mixed mode, but in the SQL Server properties window I select SQL
Server and Windows then press OK, but the window doesn't close and it
won't let me save the settings. Why is this? Can anyone help?
Thanks,
JonIt would help if you specify the version and editions
"Jon" <JonMYates@.gmail.com> wrote in message
news:1191402457.786282.106960@.57g2000hsv.googlegroups.com...
> Hello all,
> I'm trying to modify the security setting for a local install to m ake
> it mixed mode, but in the SQL Server properties window I select SQL
> Server and Windows then press OK, but the window doesn't close and it
> won't let me save the settings. Why is this? Can anyone help?
> Thanks,
> Jon
>sql
Wednesday, March 7, 2012
Missing Properties?
Has anyone tried to open a cube into Business Intelligence Studio and the properties for the database vanished (project menu, properties)?
How do you get them back?
still haven't figured this one out|||
What property are you looking for?
In project mode there is only the database name property, but if you are working in online mode even this does not appear to be available. But the description, account settings and translations properties are all available under the "edit database" option in both modes.
Monday, February 20, 2012
Missing Elements in Report Manager
Has anyone run across this before? I'm missing the Contents and Properties tab along with the button bar containing the "New Folder", "New Data Source", "Upload File" and "Show Details" buttons in the Report Manager. Also, which I think may be related, when I attempt to deploy a report I get the error: "A connection could not be made to the report server http://MyServer/Reports.
I can connect to the SQL Server without problem, and I can browse to the URL containing report manager
Interestingly, I had access to all of this a couple of weeks ago and then all of this suddenly happened. All the other developers have no problems and I am a member of the group which has access.
Any ideas?
Thanks in advance!
JohnMIt sounds like the permission are not set correctly. Perhaps you user account has been specified with more restrictive permissions?|||
Hi John,
Have you managed to resolve the issue? I have the exact same problem! :(
Kind Regards,
Casey.
|||Has anyone figured this out? I have run into this exact issue and can not figure it out. All rights appear correct.
If there is a fix, can you please email me at mradomski@.lpsintegration.com
Missing Elements in Report Manager
Has anyone run across this before? I'm missing the Contents and Properties tab along with the button bar containing the "New Folder", "New Data Source", "Upload File" and "Show Details" buttons in the Report Manager. Also, which I think may be related, when I attempt to deploy a report I get the error: "A connection could not be made to the report server http://MyServer/Reports.
I can connect to the SQL Server without problem, and I can browse to the URL containing report manager
Interestingly, I had access to all of this a couple of weeks ago and then all of this suddenly happened. All the other developers have no problems and I am a member of the group which has access.
Any ideas?
Thanks in advance!
JohnMIt sounds like the permission are not set correctly. Perhaps you user account has been specified with more restrictive permissions?|||
Hi John,
Have you managed to resolve the issue? I have the exact same problem! :(
Kind Regards,
Casey.
|||Has anyone figured this out? I have run into this exact issue and can not figure it out. All rights appear correct.
If there is a fix, can you please email me at mradomski@.lpsintegration.com
Missing Elements in Report Manager
Has anyone run across this before? I'm missing the Contents and Properties tab along with the button bar containing the "New Folder", "New Data Source", "Upload File" and "Show Details" buttons in the Report Manager. Also, which I think may be related, when I attempt to deploy a report I get the error: "A connection could not be made to the report server http://MyServer/Reports.
I can connect to the SQL Server without problem, and I can browse to the URL containing report manager
Interestingly, I had access to all of this a couple of weeks ago and then all of this suddenly happened. All the other developers have no problems and I am a member of the group which has access.
Any ideas?
Thanks in advance!
JohnMIt sounds like the permission are not set correctly. Perhaps you user account has been specified with more restrictive permissions?|||
Hi John,
Have you managed to resolve the issue? I have the exact same problem! :(
Kind Regards,
Casey.
|||Has anyone figured this out? I have run into this exact issue and can not figure it out. All rights appear correct.
If there is a fix, can you please email me at mradomski@.lpsintegration.com
Subscribe to:
Posts (Atom)