mgmt studio-View user permissions?

Using SQL server 2000 Enterprise Manager, one can bring up the properties of
a database user, click the Permissions button, and see all the permissions
that have been set for Stored Procs, tables etc... One can modify these as
needed.
How do I use Management Studio to do this?
I tried selecting the user (under security for that database) and was
expecting to see it under the Securables page under the Explicit permissions
- but I don't see it there - the user has been granted execute permissions to
some of the stored procedures and I can verify that by selecting the stored
proc and selecting the Permissions page under it's properties...
I am running SQL server 2005 Standard on a WinXP SP2.
Hi,
In user properties window and securables, try adding all stored procedures
with Add button.
Then you select all objects of type and select stored procedures.
Then just click on stored procedure and permissions should be written in
bottom of the window.
Danijel Novak
"Bob" <Bob@.discussions.microsoft.com> wrote in message
news:43F72B0A-113D-4A7E-A97D-0D63C77EF41B@.microsoft.com...
> Using SQL server 2000 Enterprise Manager, one can bring up the properties
> of
> a database user, click the Permissions button, and see all the permissions
> that have been set for Stored Procs, tables etc... One can modify these
> as
> needed.
> How do I use Management Studio to do this?
> I tried selecting the user (under security for that database) and was
> expecting to see it under the Securables page under the Explicit
> permissions
> - but I don't see it there - the user has been granted execute permissions
> to
> some of the stored procedures and I can verify that by selecting the
> stored
> proc and selecting the Permissions page under it's properties...
> I am running SQL server 2005 Standard on a WinXP SP2.
|||Thanks for the quick response Danijel. I guess I was looking for something
similar to what Enterprise manager offered "List only objects with
permissions for this user" option when we select the permissions for a user
in the database context.
Is there a way to see these?
Thanks again!
"Danijel Novak" wrote:

> Hi,
> In user properties window and securables, try adding all stored procedures
> with Add button.
> Then you select all objects of type and select stored procedures.
> Then just click on stored procedure and permissions should be written in
> bottom of the window.
> --
> Danijel Novak
>
> "Bob" <Bob@.discussions.microsoft.com> wrote in message
> news:43F72B0A-113D-4A7E-A97D-0D63C77EF41B@.microsoft.com...
>
>
|||Hi,
For that purpose I'm using following T-SQL...
SELECT OBJECT_NAME(major_id), permission_name, state_desc FROM
sys.database_permissions WHERE grantee_principal_id = USER_ID('db_user')
Hope this is what you're looking for...
Danijel Novak
"Bob" <Bob@.discussions.microsoft.com> wrote in message
news:8B465B77-A3D1-4B4C-80ED-A88DCD4B93D6@.microsoft.com...[vbcol=seagreen]
> Thanks for the quick response Danijel. I guess I was looking for something
> similar to what Enterprise manager offered "List only objects with
> permissions for this user" option when we select the permissions for a
> user
> in the database context.
> Is there a way to see these?
> Thanks again!
> "Danijel Novak" wrote:

Mgmt Studio: Script Table as...

Hi,

I'm using SQL Server 2005 Express SP1 & Mgmt Studio express.

I'm trying to use the script output to track my db changes in source code mgmt, but when I output a table to a script the first two bytes of the "text" file are 0xFF and 0xFE which sends my SCM into storingthe file in binary defeating the purpose of storing text files I can "diff" to see the changes.

Does anyone know why the mgmt studio is doing this and is there a way to stop it?

thanks!

Management Studio creates UNICODE files so characters from all alphabets can be represented in the same file. Your SCM system is probably interpretting the UNICODE signature at the top of the file as being "binary."

If you are scripting to a Query Editor Window, you can save the script as an ASCII file by clicking File | Save As... and clicking the little pull-down arrow on the right side of the save button to select the file type. US-ASCII is toward the bottom of the list.

Hope this helps,
Steve

|||

Thanks! This was helpful and it explains the situation.

I'm working around it by the copy & paste method you mention while I deal with the SCM issue.

It's interesting that SQL Server Mgmt Studio uses unicode BOM and Visual Studio uses utf-8 for it's configuration files, so the SCM has to deal with the many "standards" of unicode...

life was not mean't to be easy...

Mgmt Studio: List versus Details view

So now all the Details views have the "Policy Health State" column. Great. But when will we be able to add other columns to the details views? Or at least put back what SQL 2K used to show in details views? Pretty please?

Hi Bob,

We actually have plans to only display the Policy Health State in the Details section for only those objects that have policy state. For CTP6, we are looking to extend the Object Details to show many more properties than you had in the past. Please stay tuned.

Bill Ramos,

Lead PM

|||Many, many thanks Bill.

Mgmt Studio not supporting 7.0?

I tried using Mgmt Studio RTM to connect to SQL Server 7.0 instance and
received this:
"This version of Microsoft SQL Server Management Studio can only be used to
connect to SQL Server 2005 and SQL Server 2000 servers (ConnectionDlg)"
I thought Mgmt Studio was going to support 7.0?
Hi
No. 7.0 is really very close to end of life so no support for it.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Johnny Ortega" <john.ortega@.quest.com> wrote in message
news:uuklBLx5FHA.2956@.TK2MSFTNGP12.phx.gbl...
>I tried using Mgmt Studio RTM to connect to SQL Server 7.0 instance and
> received this:
> "This version of Microsoft SQL Server Management Studio can only be used
> to
> connect to SQL Server 2005 and SQL Server 2000 servers (ConnectionDlg)"
> I thought Mgmt Studio was going to support 7.0?
>
|||Maybe part of the confusion is because the book 'Microsoft SQL Server 2005 -
Changing the Paradigm' mentions that SQL Server 7 will be supported (page
97).
Ben Nevarez
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:usTkijx5FHA.2628@.TK2MSFTNGP11.phx.gbl...
> Hi
> No. 7.0 is really very close to end of life so no support for it.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Johnny Ortega" <john.ortega@.quest.com> wrote in message
> news:uuklBLx5FHA.2956@.TK2MSFTNGP12.phx.gbl...
>
|||Hi
Lots of features get dropped from the Product over it's development life.
This support was dropped very early. SMO support for SQL Server 7.0 was
dropped very late and there is still documentation mentioning it.
During the development program, even e-mails were stale by the time most
people read them, let alone printed books.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:e2lMdML6FHA.1000@.tk2msftngp13.phx.gbl...
> Maybe part of the confusion is because the book 'Microsoft SQL Server
> 2005 - Changing the Paradigm' mentions that SQL Server 7 will be supported
> (page 97).
> Ben Nevarez
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:usTkijx5FHA.2628@.TK2MSFTNGP11.phx.gbl...
>

Mgmt Studio and Sql 2000

I have a local server I just upgraded to 2005. Everything went well. But,
I
also have a remote sql 2000 server I still need to connect to. Can't seem
to get the tcp/ip connection to old server to work. Go back to old 2000 too
l
and it works fine, but I'd prefer to stay in one environment and migrate to
the new tool. Any ideas?What errors do you get?
-Sue
On Tue, 25 Jul 2006 06:47:02 -0700, Janet
<Janet@.discussions.microsoft.com> wrote:

>I have a local server I just upgraded to 2005. Everything went well. But,
I
>also have a remote sql 2000 server I still need to connect to. Can't seem
>to get the tcp/ip connection to old server to work. Go back to old 2000 to
ol
>and it works fine, but I'd prefer to stay in one environment and migrate to
>the new tool. Any ideas?|||As background - in SSMS, I checked the sql native client connectivity and
tcpip is enabled, alias is listed with correct ip and port. Error is:
===================================
Cannot connect to CASCE.
===================================
This version of Microsoft SQL Server Management Studio can only be used to
connect to SQL Server 2000 and SQL Server 2005 servers. (ConnectionDlg)
Program Location:
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.SqlServerType.Microsoft.SqlS
erver.Management.UI.ConnectionDlg.IConnectionValidator.CheckConnection(IDbCo
nnection conn)
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.CheckConnection()
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectorThread()
"Sue Hoegemeier" wrote:

> What errors do you get?
> -Sue
> On Tue, 25 Jul 2006 06:47:02 -0700, Janet
> <Janet@.discussions.microsoft.com> wrote:
>
>|||That's the error you get when you try to connect to SQL
Server 7 or earlier with SSMS. Double check the version on
the other remote server when you connect with Query Analyzer
using select @.@.version.
-Sue
On Wed, 26 Jul 2006 10:28:02 -0700, Janet
<Janet@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>As background - in SSMS, I checked the sql native client connectivity and
>tcpip is enabled, alias is listed with correct ip and port. Error is:
>===================================
>Cannot connect to CASCE.
>===================================
>This version of Microsoft SQL Server Management Studio can only be used to
>connect to SQL Server 2000 and SQL Server 2005 servers. (ConnectionDlg)
>--
>Program Location:
> at
>Microsoft.SqlServer.Management.UI.ConnectionDlg.SqlServerType.Microsoft.Sql
Server.Management.UI.ConnectionDlg.IConnectionValidator.CheckConnection(IDbC
onnection conn)
> at
>Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.CheckConnection()
> at
>Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectorThread()
>
>"Sue Hoegemeier" wrote:
>|||Sue, holy toledo! You're right! My contact TOLD me they were running sql
2000, but they're running sql 7. I know that the new SSMS won't work with
that - read that in the documentation. Ah, well. Have to keep the old tool
s
around, I guess. Thanks so much for forcing me to double-check.
"Sue Hoegemeier" wrote:

> That's the error you get when you try to connect to SQL
> Server 7 or earlier with SSMS. Double check the version on
> the other remote server when you connect with Query Analyzer
> using select @.@.version.
> -Sue
> On Wed, 26 Jul 2006 10:28:02 -0700, Janet
> <Janet@.discussions.microsoft.com> wrote:
>
>

Mgmt Studio

Can I manage MSDE databases in Management Studio? If not, how can I? How
about SQL Express?
When I try to attach an msde.mdf it just gets an "unknown error."
Regards,
Gary BlakelyTry to attach an MSDE MDF file to what?
You can certainly manage existing instances of SQL Server 2000 (including
MSDE). But you're not going to be able to just attach a SQL Server
2000-based mdf (from MSDE or otherwise) to a 2005 instance.
A
"GaryDean" <GaryDean@.newsgroups.nospam> wrote in message
news:OZhDtF5HHHA.4760@.TK2MSFTNGP03.phx.gbl...
> Can I manage MSDE databases in Management Studio? If not, how can I? How
> about SQL Express?
> When I try to attach an msde.mdf it just gets an "unknown error."
> --
> Regards,
> Gary Blakely
>|||Hi Gary,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support

Mgmt Studio

Can I manage MSDE databases in Management Studio? If not, how can I? How
about SQL Express?
When I try to attach an msde.mdf it just gets an "unknown error."
--
Regards,
Gary BlakelyTry to attach an MSDE MDF file to what?
You can certainly manage existing instances of SQL Server 2000 (including
MSDE). But you're not going to be able to just attach a SQL Server
2000-based mdf (from MSDE or otherwise) to a 2005 instance.
A
"GaryDean" <GaryDean@.newsgroups.nospam> wrote in message
news:OZhDtF5HHHA.4760@.TK2MSFTNGP03.phx.gbl...
> Can I manage MSDE databases in Management Studio? If not, how can I? How
> about SQL Express?
> When I try to attach an msde.mdf it just gets an "unknown error."
> --
> Regards,
> Gary Blakely
>|||Hi Gary,
SQL Server 2005 Management Studio totally supports attaching SQL Server
2000, MSDE2000 and SQL Express databases by using sp_detach_db/sp_attach_db
stored procedure.
Please try again via the following:
1. Connect to your MSDE instance, and run the following statement:
use master
go
exec sp_detach_db 'YourDatabaseName'
2. Connect to your SQL Server 2005 instance and run the following statement:
use master
go
exec sp_attach_db @.dbname='DatabaseName',
@.filename1 = N'C:\Program Files\Microsoft SQL
Server\MSSQL$MSDE\Data\test.mdf',
@.filename2 = N'C:\Program Files\Microsoft SQL
Server\MSSQL$MSDE\Data\test_log.ldf'
Could you please mail me (changliw@.microsoft.com) the SQL error logs and a
screenshot of the error message for further research?
By default, the error logs of SQL Server 2005 instance are located in
"C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG". You may check it
if there are multiple instances installed on your computer.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Hi Gary,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support

Mgmt Studio

Can I manage MSDE databases in Management Studio? If not, how can I? How
about SQL Express?
When I try to attach an msde.mdf it just gets an "unknown error."
Regards,
Gary Blakely
Try to attach an MSDE MDF file to what?
You can certainly manage existing instances of SQL Server 2000 (including
MSDE). But you're not going to be able to just attach a SQL Server
2000-based mdf (from MSDE or otherwise) to a 2005 instance.
A
"GaryDean" <GaryDean@.newsgroups.nospam> wrote in message
news:OZhDtF5HHHA.4760@.TK2MSFTNGP03.phx.gbl...
> Can I manage MSDE databases in Management Studio? If not, how can I? How
> about SQL Express?
> When I try to attach an msde.mdf it just gets an "unknown error."
> --
> Regards,
> Gary Blakely
>
|||Hi Gary,
SQL Server 2005 Management Studio totally supports attaching SQL Server
2000, MSDE2000 and SQL Express databases by using sp_detach_db/sp_attach_db
stored procedure.
Please try again via the following:
1. Connect to your MSDE instance, and run the following statement:
use master
go
exec sp_detach_db 'YourDatabaseName'
2. Connect to your SQL Server 2005 instance and run the following statement:
use master
go
exec sp_attach_db @.dbname='DatabaseName',
@.filename1 = N'C:\Program Files\Microsoft SQL
Server\MSSQL$MSDE\Data\test.mdf',
@.filename2 = N'C:\Program Files\Microsoft SQL
Server\MSSQL$MSDE\Data\test_log.ldf'
Could you please mail me (changliw@.microsoft.com) the SQL error logs and a
screenshot of the error message for further research?
By default, the error logs of SQL Server 2005 instance are located in
"C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG". You may check it
if there are multiple instances installed on your computer.
Sincerely yours,
Charles Wang
Microsoft Online Community Support
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Hi Gary,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support