Deployment of system

I am about to start developing a system using VB 2003 and SQL Server 2000. On my development computer, I am going to use MSDE for the database, which I guess I will later be able to export to my client's SQL server 2000.

Now, I am a bit worried. In my local computer, I can develop a system which runs locally very well. So, I am very sure I will be able to develop one for my client. But when I later deploy it to the client, it will have to run on a server and client machines.

My question is, how easy or complex is it to deploy such a system from my standalone platform to a client-server one. I have adequate experience developing stand-alone systems.

I am about to get started so please kindly give me ideas on the best path to take.

Hi there and welcome to client server development :-)

Its quite easy if you are developing on a MSDE and want to deploy that later on a Std / Ent Server. It is reduced to making a backup and restoring the backup on the server, normally that should be all except for the server users, which additionally have to be scripted and deployed.

BTW: If you want to deploy it on productional systems on Std / Ent Editions, why don′t you use SQL Server Dev Edition to develop the applications. It would be more comfortable for you and it would be a more soution-near development.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

|||

Thanx a lot for the info.

What I am about to develop is really a small system that would not warrant me going for any extra development tools more than what I have - cost is an issue.

You said that the database it is a matter of backup/restore. What about the VB application? Lets take the simplest example below.

Supposing I have a VB form bound to a datasource coming from some SQL Connection (localhost) on my development PC. The form will run on my computer because its connection is there.

Now, what happens if I take the above (app and database) to client-server environment. I restore the db on server and install app on client (?). But the connection in app is to localhost on my development PC. So it will not run in client-server until I modify the connection to point to the new server. Am I right or wrong?

|||Hi,

yes you are right, but that a point of configuration. I think right now you are using configurable settings in your application, so just add another setting to pass the servername, port etc. to the data source creator (or whatever you implemented).

The developer edition isn′t expensive at all. Should be available for 49$ (around),so developing on development edition will help you in many cases spending (/wasting) time for configuring something or getting a fst info from the server.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de
|||Be blessed. I'll check out all your suggestions.

Deployment of MSDE

Is there a way to turn off System Administrators in Server Roles for the
Builtin\Administrators using the deployment toolkit?
No
"Jon" <Jon@.discussions.microsoft.com> wrote in message
news:1364DDFA-764B-4C65-AC14-BBBFEB979DD2@.microsoft.com...
> Is there a way to turn off System Administrators in Server Roles for the
> Builtin\Administrators using the deployment toolkit?
|||Hi Jon,
I install MSDE with my C# app via the deployment toolkit.
As soon as my C# app starts, I run the command against the DB
EXEC sp_denylogin [BUILTIN\\Administrators]
This removes the admins from the built in group
HTH
Paul
"Jon" <Jon@.discussions.microsoft.com> wrote in message
news:1364DDFA-764B-4C65-AC14-BBBFEB979DD2@.microsoft.com...
> Is there a way to turn off System Administrators in Server Roles for the
> Builtin\Administrators using the deployment toolkit?
|||hi Paul,
Paul Aspinall wrote:
> Hi Jon,
> I install MSDE with my C# app via the deployment toolkit.
> As soon as my C# app starts, I run the command against the DB
> EXEC sp_denylogin [BUILTIN\\Administrators]
> This removes the admins from the built in group
>
and the SQL Server Agent can run without problems?
(http://support.microsoft.com/default.aspx?kbid=237604)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql

Deployment File System installation

Hallo,

i created a solution that is working fine in development. I would now like to deploy it on an other server.

We have choosen for a file system -based deployment because this seems to require the least specialized SQL Server-knowledge from the user who will be utilizing this system. I changed the properties of the solution to

CreateDeploymentUtility: true

DeploymentOutputPath : bin\Deployment

Subsequently I build the solution and in the bin\Deployment-folder dtsx-files have been created.

Can anyone tell me what I need to do next to deploy them on an other machine?

Do I need to deploy a complete version of SQL SERVER 2005 Devenv included or is there a lighter installation possible that only contains what I need to run the packages?

Can I shedule the packages to run at a specified moment without DTultil coming up?

When you once found an answer to these many questions i would be most gratefull if you woulkd let me know.

Kind regards,

Paul

I seem to have found a solution to my own questions?

Can anyone tell me what I need to do next to deploy them on an other machine?

Do I need to deploy a complete version of SQL SERVER 2005 Devenv included or is there a lighter installation possible that only contains what I need to run the packages?

I did the test and only succeeded in running the packages after a complete install of SQLServer 2005.

Can I shedule the packages to run at a specified moment without DTultil coming up?

Using the MS-sheduler I sheduled the execution of a batch-file. this batchfile contains the Command line instructions created using DTUtil, preceded by 'DTexec '. for instance. 'DTEXEC /FILE "C:\Program Files\JACBE_IF_CAB\FMC_People.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI'

There might be a more elegant solution but this seems to work .

Kind regards,

Paul

|||

You don't need devenv at all. Devenv comes with the client tools install.

The only thing you need to run packages is to install Integration Services. This is different to the client install.

-Jamie

|||

Hallo Jamie,

Thanks for your swift reply.

I admit i'm not a SQL server specilist but while installing SQL Server 2005 from CD (Microsoft SQL Server 2005 Enterprise Edition December 2005) or DVD the option 'Integration services' is disabled. So I can not single it out for installation. . Is there still an other installation dvd I need or can I download the SSIS server component from somewhere? I did not seem to find it in the download center

With kind regards,

Paul

|||

That's bizarre. I have installed off that CD a number of times and the option is never greyed out. Very strange indeed - I don't know what would cuse this.

I would contact your reseller and ask them why you can't install the software that you have paid for!

-Jamie

sql

Deployment Copy/Paste Problems

Hi all,
We maintain our CAB (meta-data only) in a source control system. The
process for deployment is simply to restore the CAB on the production
server and then copy/paste it to the production database name where it
will have it's final resting place.
By doing this we allow for scalability and robust management since the
same CAB can be deployed to many places. (In some places we process
different sets of cubes than in other places but the same meta-data
can be re-used.)
The problem we are finding is that one of our production servers is a
64 bit box that is (necessarily) remotely managed from a 32 bit
instance of Analysis Manager. When copy/pasting the database remotely
it takes a very, very long time to complete. Keep in mind that only
meta-data is being copied. When copy/paste is happening, it looks
like DSO code is executing to rebuild an entire database from scratch.
Does anybody have a faster method of copy/pasting an Analysis Services
database into place for deployment purposes?
Thanks,
DavidDavid Beavon wrote:

> Hi all,
>
> We maintain our CAB (meta-data only) in a source control system. The
> process for deployment is simply to restore the CAB on the production
> server and then copy/paste it to the production database name where it
> will have it's final resting place.
> By doing this we allow for scalability and robust management since the
> same CAB can be deployed to many places. (In some places we process
> different sets of cubes than in other places but the same meta-data
> can be re-used.)
>
> The problem we are finding is that one of our production servers is a
> 64 bit box that is (necessarily) remotely managed from a 32 bit
> instance of Analysis Manager. When copy/pasting the database remotely
> it takes a very, very long time to complete. Keep in mind that only
> meta-data is being copied. When copy/paste is happening, it looks
> like DSO code is executing to rebuild an entire database from scratch.
>
> Does anybody have a faster method of copy/pasting an Analysis Services
> database into place for deployment purposes?
> Thanks,
> David
http://www.solgenia.com/usa/Solutio.../SheetRubik.htm

Deploying System DSN to Multiple PCs

Is there any way to deploy System DSNs to multiple PCs?
I'm in a windows xp client environment with sql server 2000 running on a
windows server 200 box.
Thanks for any help.
System DSNs are stored in the registry under
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI. Try exporting the registry node
for the data source and run it on another computer to see if it works.
Roman
Roman Rehak, MCSD, MCDBA, MCSA
SQL Server Specialist
Competitive Computing
http://sqljunkies.com/WebLog/Roman
"Josh" <Josh@.discussions.microsoft.com> wrote in message
news:FA14A0DA-A2C4-4779-ADDC-49F79016EF6E@.microsoft.com...
> Is there any way to deploy System DSNs to multiple PCs?
> I'm in a windows xp client environment with sql server 2000 running on a
> windows server 200 box.
> Thanks for any help.
|||Thanks for replying but that didn't work. I was thinking maybe there might
be a way to create a vbscript to create the system dsns.
"Roman Rehak" wrote:

> System DSNs are stored in the registry under
> HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI. Try exporting the registry node
> for the data source and run it on another computer to see if it works.
> Roman
>
> Roman Rehak, MCSD, MCDBA, MCSA
> SQL Server Specialist
> Competitive Computing
> http://sqljunkies.com/WebLog/Roman
>
> "Josh" <Josh@.discussions.microsoft.com> wrote in message
> news:FA14A0DA-A2C4-4779-ADDC-49F79016EF6E@.microsoft.com...
>
>
|||These articles might help you get going with this:
How To Create and Remove a DSN in Visual Basic
http://support.microsoft.com/?id=171146
How To Programmatically Create a DSN for SQL Server with VB
http://support.microsoft.com/?id=184608
-Sue
On Sun, 27 Feb 2005 21:47:01 -0800, "Josh"
<Josh@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thanks for replying but that didn't work. I was thinking maybe there might
>be a way to create a vbscript to create the system dsns.
>
>"Roman Rehak" wrote:

deploying SSIS

Hi

We are storing our packages in File System.

Process:

BIDS->Right Click on soln file ->properties->Deployment Utility->DeploymentOutputPath--Bin\Deployment

So it creates a folder with the project name and all the packages in C:\Program Files\Microsoft SQL Server\90\DTS\Packages\Project

While executing the package on Server what should be thesource of the Package? I mean should it refer to the solution file->..dtsx

or

Bin\Deployment->packages

or

C:\Program Files\Microsoft SQL Server\90\DTS\Packages\Project

Moving from .NET Framework Data Access and Storage...|||

Paarul wrote:

Hi

We are storing our packages in File System.

Process:

BIDS->Right Click on soln file ->properties->Deployment Utility->DeploymentOutputPath--Bin\Deployment

So it creates a folder with the project name and all the packages in C:\Program Files\Microsoft SQL Server\90\DTS\Packages\Project

While executing the package on Server what should be thesource of the Package? I mean should it refer to the solution file->..dtsx

or

Bin\Deployment->packages

or

C:\Program Files\Microsoft SQL Server\90\DTS\Packages\Project

You need to point to the folder holding the .dtsx file in the server no matter hoe you deploy it.

deploying SQL server applications to another machine

Hi -
Let me start off by saying that I am a complete SQL server newbie.
I work with a system that uses SQL Server 2005 as it's backbone DB
running on W2K3 server. This system is going to be installed onto
customer servers, also running W2K3 server. Question is; is there a
way to deploy all aspects of JUST THE DB (tables, stored procedures,
security, users, etc...) to the customers servers without having to do
a full up install of SQL Server 2005 on every server that will host a
database?
ThanksYou need some process to read and interact with the database files. The only such process I know of
is ... SQL Server. Now, that can be Express edition, but it need to be some version of SQL Server...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<ecfiedler@.impactsci.com> wrote in message
news:1179865512.394536.163730@.q69g2000hsb.googlegroups.com...
> Hi -
> Let me start off by saying that I am a complete SQL server newbie.
> I work with a system that uses SQL Server 2005 as it's backbone DB
> running on W2K3 server. This system is going to be installed onto
> customer servers, also running W2K3 server. Question is; is there a
> way to deploy all aspects of JUST THE DB (tables, stored procedures,
> security, users, etc...) to the customers servers without having to do
> a full up install of SQL Server 2005 on every server that will host a
> database?
> Thanks
>

deploying SQL server applications to another machine

Hi -
Let me start off by saying that I am a complete SQL server newbie.
I work with a system that uses SQL Server 2005 as it's backbone DB
running on W2K3 server. This system is going to be installed onto
customer servers, also running W2K3 server. Question is; is there a
way to deploy all aspects of JUST THE DB (tables, stored procedures,
security, users, etc...) to the customers servers without having to do
a full up install of SQL Server 2005 on every server that will host a
database?
Thanks
You need some process to read and interact with the database files. The only such process I know of
is ... SQL Server. Now, that can be Express edition, but it need to be some version of SQL Server...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<ecfiedler@.impactsci.com> wrote in message
news:1179865512.394536.163730@.q69g2000hsb.googlegr oups.com...
> Hi -
> Let me start off by saying that I am a complete SQL server newbie.
> I work with a system that uses SQL Server 2005 as it's backbone DB
> running on W2K3 server. This system is going to be installed onto
> customer servers, also running W2K3 server. Question is; is there a
> way to deploy all aspects of JUST THE DB (tables, stored procedures,
> security, users, etc...) to the customers servers without having to do
> a full up install of SQL Server 2005 on every server that will host a
> database?
> Thanks
>

deploying SQL server applications to another machine

Hi -
Let me start off by saying that I am a complete SQL server newbie.
I work with a system that uses SQL Server 2005 as it's backbone DB
running on W2K3 server. This system is going to be installed onto
customer servers, also running W2K3 server. Question is; is there a
way to deploy all aspects of JUST THE DB (tables, stored procedures,
security, users, etc...) to the customers servers without having to do
a full up install of SQL Server 2005 on every server that will host a
database?
ThanksYou need some process to read and interact with the database files. The only
such process I know of
is ... SQL Server. Now, that can be Express edition, but it need to be some
version of SQL Server...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<ecfiedler@.impactsci.com> wrote in message
news:1179865512.394536.163730@.q69g2000hsb.googlegroups.com...
> Hi -
> Let me start off by saying that I am a complete SQL server newbie.
> I work with a system that uses SQL Server 2005 as it's backbone DB
> running on W2K3 server. This system is going to be installed onto
> customer servers, also running W2K3 server. Question is; is there a
> way to deploy all aspects of JUST THE DB (tables, stored procedures,
> security, users, etc...) to the customers servers without having to do
> a full up install of SQL Server 2005 on every server that will host a
> database?
> Thanks
>

Deploying Reports to a New Server

I developed some reports on one system that I would like to move to another
system. I copied the rdl file to the new system and uploaded it via Report
Manager.
The data source the report uses is based upon SQL views which I created on
the new server.
I'm having a problem with the data source. I've tried creating a new custom
data source by going to the properties of the report and clicking on Data
Sources. I've also tried creating a new data source by clicking New Data
Source from the home page of the Reports.
I've received login errors using the sa account and I've seen that, despite
picking a new data source, it still seems to use the old data source.
What do I need to do to point the report to a the current server's data?
--
Charles Allen, MVPIf both the servers are accessible on your network, just go to report project
properties and change the server to your new server and deploy it, instead of
you doing it does the job perfectly, including datasource..
Amarnath
"Charles Allen" wrote:
> I developed some reports on one system that I would like to move to another
> system. I copied the rdl file to the new system and uploaded it via Report
> Manager.
> The data source the report uses is based upon SQL views which I created on
> the new server.
> I'm having a problem with the data source. I've tried creating a new custom
> data source by going to the properties of the report and clicking on Data
> Sources. I've also tried creating a new data source by clicking New Data
> Source from the home page of the Reports.
> I've received login errors using the sa account and I've seen that, despite
> picking a new data source, it still seems to use the old data source.
> What do I need to do to point the report to a the current server's data?
> --
> Charles Allen, MVP
>|||Thank you for replying quickly.
In this case, the machines are not on the same network. One is a test
environment I use and the other is a client's production system.
--
Charles Allen, MVP
"Amarnath" wrote:
> If both the servers are accessible on your network, just go to report project
> properties and change the server to your new server and deploy it, instead of
> you doing it does the job perfectly, including datasource..
> Amarnath
> "Charles Allen" wrote:
> > I developed some reports on one system that I would like to move to another
> > system. I copied the rdl file to the new system and uploaded it via Report
> > Manager.
> >
> > The data source the report uses is based upon SQL views which I created on
> > the new server.
> >
> > I'm having a problem with the data source. I've tried creating a new custom
> > data source by going to the properties of the report and clicking on Data
> > Sources. I've also tried creating a new data source by clicking New Data
> > Source from the home page of the Reports.
> >
> > I've received login errors using the sa account and I've seen that, despite
> > picking a new data source, it still seems to use the old data source.
> >
> > What do I need to do to point the report to a the current server's data?
> > --
> > Charles Allen, MVP
> >|||ok, MS has provided a sample script on "how to deploy the reports using
command prompt", you can have a look at that sample for your solution.
Amarnath
"Charles Allen" wrote:
> Thank you for replying quickly.
> In this case, the machines are not on the same network. One is a test
> environment I use and the other is a client's production system.
> --
> Charles Allen, MVP
>
> "Amarnath" wrote:
> > If both the servers are accessible on your network, just go to report project
> > properties and change the server to your new server and deploy it, instead of
> > you doing it does the job perfectly, including datasource..
> >
> > Amarnath
> >
> > "Charles Allen" wrote:
> >
> > > I developed some reports on one system that I would like to move to another
> > > system. I copied the rdl file to the new system and uploaded it via Report
> > > Manager.
> > >
> > > The data source the report uses is based upon SQL views which I created on
> > > the new server.
> > >
> > > I'm having a problem with the data source. I've tried creating a new custom
> > > data source by going to the properties of the report and clicking on Data
> > > Sources. I've also tried creating a new data source by clicking New Data
> > > Source from the home page of the Reports.
> > >
> > > I've received login errors using the sa account and I've seen that, despite
> > > picking a new data source, it still seems to use the old data source.
> > >
> > > What do I need to do to point the report to a the current server's data?
> > > --
> > > Charles Allen, MVP
> > >

Deploying reports from VS2003 to RS2005

I was led to believe that you could deploy reports created in VS2003 to
RS2005. I have upgraded our test system to RS2005, but when I try to deploy
a report that has been created in VS2003 (RS2000), I get the following error:
The version of the report server database is either in a format that is not
valid, or it cannot be read. The found version is 'C.0.8.40'. The expected
version is 'C.0.6.54'. To continue, update the version of the report server
database and verify access rights.
Was I wrong in assuming that it was backwards compatible? I realize I can't
create a report in VS2005 and deploy it to an RS2000 instance, but I thought
going the other way was acceptable?Hi dachrist,
Welcome to use MSDN Managed Newsgroup Support.
You can deploy the reports created in VS 2003 to a Reporting Services 2005
server.
The root cause of the error message you recieved is the report server
database is not the same version as the report server engine. This error
can occur if you move components or modify your configuration (for example,
moving a report server into a Web farm, and the existing report servers in
the Web farm are a different version).
please try to use the rsconfig utility to re-config the report server
database.
rsconfig -c -s servername -d reportserver -a SQL -u sa -p password
Thank you for your patient.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Deploying development packages to production

We have a system here where we develop SSIS packages on a development server. I am trying to figure out the cleanest way to promote these changes to a production server where stored procedures/tables that are used in the package are not deployed yet.

When I switch the connection in the package to the production server there are alot of objects in the package that are "invalidated" because they are trying to verify existence of tables/columns. One example is outputing the results of a query to a text file. The text file destination gets a red X on it because it cant grab the columns from the source query (because that stored procedure doesnt exist yet)

Is there a best practices or something on how to deploy packages to a production system? I have tried turning off "ValidateExternalMetaData" with no success.

Thanks!

I think you need to read up on configurations. Configurations allow you to change all sorts of properties/variables external to the ssis package itself.

-Try searching 'configurations' on this forum

-Read books on-line

-Or check many articles on Jamie Thompson's website

http://blogs.conchango.com/jamiethomson/

Hope this helps.

|||

CraigL77 wrote:

We have a system here where we develop SSIS packages on a development server. I am trying to figure out the cleanest way to promote these changes to a production server where stored procedures/tables that are used in the package are not deployed yet.

When I switch the connection in the package to the production server there are alot of objects in the package that are "invalidated" because they are trying to verify existence of tables/columns. One example is outputing the results of a query to a text file. The text file destination gets a red X on it because it cant grab the columns from the source query (because that stored procedure doesnt exist yet)

Is there a best practices or something on how to deploy packages to a production system? I have tried turning off "ValidateExternalMetaData" with no success.

Thanks!

If you use configurations (as Anthony suggested), you can set different connection strings for different environments. However, for the packages to run (and validate) in the production environment, the stored procs will have to be present.

If you change the connection strings in the package, you can ignore the validation errors and copy the packages to the server. They should run successfully as soon as the procs are created.

Deny view on system tables and views

Hello,
Through a GUI, my users can see all the system table or views.
I want to hide these tables and views so the users cannot see them in the
list.
Is it a good idea to:
use master;
deny select on 'systemTable1' to Public
deny select on 'systemTable2' to Public
deny select on 'systemTable3' to Public
...etc...
deny select on 'systemTablen' to Public
or it can have bad consequences?
ThxTo the best of my knowledge, this isn't supported. Move to 2005, where there is explicit support for
this, and by default you can only see objects you have access to (except for databases, but that can
be changed).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Chris Leroquais" <c.le_roq@.caramail.com> wrote in message
news:44884b87$0$851$ba4acef3@.news.orange.fr...
> Hello,
> Through a GUI, my users can see all the system table or views.
> I want to hide these tables and views so the users cannot see them in the list.
> Is it a good idea to:
> use master;
> deny select on 'systemTable1' to Public
> deny select on 'systemTable2' to Public
> deny select on 'systemTable3' to Public
> ...etc...
> deny select on 'systemTablen' to Public
> or it can have bad consequences?
> Thx
>

Deny view on system tables and views

Hello,
Through a GUI, my users can see all the system table or views.
I want to hide these tables and views so the users cannot see them in the
list.
Is it a good idea to:
use master;
deny select on 'systemTable1' to Public
deny select on 'systemTable2' to Public
deny select on 'systemTable3' to Public
...etc...
deny select on 'systemTablen' to Public
or it can have bad consequences?
ThxTo the best of my knowledge, this isn't supported. Move to 2005, where there
is explicit support for
this, and by default you can only see objects you have access to (except for
databases, but that can
be changed).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Chris Leroquais" <c.le_roq@.caramail.com> wrote in message
news:44884b87$0$851$ba4acef3@.news.orange.fr...
> Hello,
> Through a GUI, my users can see all the system table or views.
> I want to hide these tables and views so the users cannot see them in the
list.
> Is it a good idea to:
> use master;
> deny select on 'systemTable1' to Public
> deny select on 'systemTable2' to Public
> deny select on 'systemTable3' to Public
> ...etc...
> deny select on 'systemTablen' to Public
> or it can have bad consequences?
> Thx
>

deny permissions issues

Hi,
i'd like to deny permissions on system objects to the public role in a
database.
I have tried using the following commands without any success:
DENY SELECT ON SCHEMA::sys TO public
or
DENY SELECT ON sys.sysobjects TO public
Can someone tell me what is wrong in my commands?
Thx,
ChrisHello Chris
I am not sure what is the reason to revoke SELECT on objects in sys schema
because resultsets will be filtered already by permissions. Anyway here is
statement you can use:
REVOKE SELECT ON sys.sysobjects FROM public
Martin Rakhmanov
<christophe.leroquais@.gmail.com> wrote in message
news:1149148183.181843.75560@.h76g2000cwa.googlegroups.com...
> Hi,
> i'd like to deny permissions on system objects to the public role in a
> database.
> I have tried using the following commands without any success:
> DENY SELECT ON SCHEMA::sys TO public
> or
> DENY SELECT ON sys.sysobjects TO public
>
> Can someone tell me what is wrong in my commands?
> Thx,
> Chris
>