http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=578917&SiteID=1
Its a real problem with no solution available. So far I can't find a work around and concur with the final analysis.
<A quick summary>
In SQL 2000 Enterprise Manager, one was able to edit and commit data
on-the-fly directly from the results pane. Action->Open
Table->Query with the SQL Pane shown gives you an interface similar
to Query Analyzer. One could write a complex select statement with
where clauses and joins, and the results pane would show the resulting
data.
The question is this:
How do you edit data in the results grid in SQL 2005 Management Studio
as you would in SQL 2000 Enterprise Manager when you Open Table via
Query (Action->Open Table->Query), and what option/configuration
setting or panel would you need to enable/show to make this a permanent
feature? In other words, what is the equivalent of Action->Open
Table->Query in Management Studio?
I also found this link that makes me wonder if its a setting: (search for "open table")
http://msdn.microsoft.com/SQL/community/webcasts/ManagementStudioQandA.aspx
<conclusion>
So far it seems it can't be done. Like they removed the feature in favor of application developers creating apps to take care of this for you, which is greatly hampering our environment.
Any official word?You can edit results in the results pane of the View designer.
From Object Explorer, right-click on the Views folder of a
database. Choose New View... . Type your query into the SQL
pane of the designer. Click on the red exclamation point to
execute your query. If the query results are updatable, you
can update them from this results pane.
If you close the criteria and diagram panes, it will be
nicer to look at.
That said, I do not recommend doing this. The view designer
has a bad habit of changing the SQL you type in, and it's
safer to make updates through SQL statements, because if you
slip up, you can at least see what you did by reading the SQL
you just executed, and you can use BEGIN TRAN and COMMIT/ROLLBACK
when you want.
Steve Kass
Drew University
www.stevekass.com
Greenmtnsun@.discussions.microsoft.com wrote:
> This post has been edited either by the author or a moderator in the
> Microsoft Forums: http://forums.microsoft.com I'm wondering if we can
> get official word on the post below:
>
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=578917&SiteID=1
>
>
> Its a real problem with no solution available. So far I can't find a
> work around and concur with the final analysis.
>
>
>
>
> In SQL > 2000 Enterprise Manager, one was able to edit and commit data > > directly from the results pane. Action->Open Table->Query with the SQL > Pane shown gives you an interface similar to Query Analyzer. One could > write a complex select statement with where clauses and joins, and the > results pane would show the resulting data. > > The question is this: How do you edit data in the results grid in SQL > 2005 Management Studio as you would in SQL 2000 Enterprise Manager when > you Open Table via Query (Action->Open Table->Query), and what > option/configuration setting or panel would you need to enable/show to > make this a permanent feature? In other words, what is the equivalent of > Action->Open Table->Query in Management Studio? > > > I also found this link that makes me wonder if its a setting: (search > for "open table") > http://msdn.microsoft.com/SQL/community/webcasts/ManagementStudioQandA.a > spx > > > > So far it seems it can't be done. Like they removed the feature in favor > of application developers creating apps to take care of this for you, > which is greatly hampering our environment. > > Any official word? > >|||I'm going to have to beg your patience because I am finding this issue very difficult to research. As you can see in this post below, good natured people like yourself have some natural inclination to feel they resolved the question just like you just did. I can't say this any other way, it does NOT work. My frustation with this issue is that if you see the thread below, it got dropped because back and forth people came in the thread thinking they resolved it, and they didn't, and eventually it fell by the wayside. Try multiple tables. It worked in SQL 2000 and does NOT in 2005. We need help. With all due respect. Is there anyone official here who can confirm this? Who can provide work arounds? Who can see if they can get this resolved in the next SP?|||http I'm bummed by Microsoft pulling this long standing precedent from its software. It seems like a bug in their thinking but I think I found my answer. Does anyone know of a peice of software that we can get around this? We need suggestions. Thanks,
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=578917&SiteID=1
Keith
No comments:
Post a Comment