I have a server with SQL 2000 and a name instance of SQL 2005, I am trying
to use the copy wizard to move databases from SQL2000 to SQL2005, when I do
this and to try to change the drive letters to my D: drive for the logs and
E: drive for the database, it goes through the process and fails. So I have
tried it again this time to the default location that SQL 2005 wants, which
is on the C: drive - of course this is not acceptable, but it works that
way. I figure it is a NTFS / permissions issue. But what permissions do I
need to setup on the other drive D: and E: to get this to work properly,
anyone please help me.
Thanks,
Andres
andres.perales@.mclaneat.com
Hi
Take a look at RESTORE command WITH MOVE option in the BOL
"Andres Perales" <andres@.andresperales.com> wrote in message
news:eu%23YtAyIHHA.1248@.TK2MSFTNGP03.phx.gbl...
>I have a server with SQL 2000 and a name instance of SQL 2005, I am trying
>to use the copy wizard to move databases from SQL2000 to SQL2005, when I do
>this and to try to change the drive letters to my D: drive for the logs and
>E: drive for the database, it goes through the process and fails. So I
>have tried it again this time to the default location that SQL 2005 wants,
>which is on the C: drive - of course this is not acceptable, but it works
>that way. I figure it is a NTFS / permissions issue. But what permissions
>do I need to setup on the other drive D: and E: to get this to work
>properly, anyone please help me.
> Thanks,
> Andres
> andres.perales@.mclaneat.com
>
>
2012年3月27日星期二
Disk permission to move SQL 2005 databases too...
I have a server with SQL 2000 and a name instance of SQL 2005, I am trying
to use the copy wizard to move databases from SQL2000 to SQL2005, when I do
this and to try to change the drive letters to my D: drive for the logs and
E: drive for the database, it goes through the process and fails. So I have
tried it again this time to the default location that SQL 2005 wants, which
is on the C: drive - of course this is not acceptable, but it works that
way. I figure it is a NTFS / permissions issue. But what permissions do I
need to setup on the other drive D: and E: to get this to work properly,
anyone please help me.
Thanks,
Andres
andres.perales@.mclaneat.comHi
Take a look at RESTORE command WITH MOVE option in the BOL
"Andres Perales" <andres@.andresperales.com> wrote in message
news:eu%23YtAyIHHA.1248@.TK2MSFTNGP03.phx.gbl...
>I have a server with SQL 2000 and a name instance of SQL 2005, I am trying
>to use the copy wizard to move databases from SQL2000 to SQL2005, when I do
>this and to try to change the drive letters to my D: drive for the logs and
>E: drive for the database, it goes through the process and fails. So I
>have tried it again this time to the default location that SQL 2005 wants,
>which is on the C: drive - of course this is not acceptable, but it works
>that way. I figure it is a NTFS / permissions issue. But what permissions
>do I need to setup on the other drive D: and E: to get this to work
>properly, anyone please help me.
> Thanks,
> Andres
> andres.perales@.mclaneat.com
>
>|||Assuming the RESTORE command is correct (you have used the MOVE options corr
ectly):
The account used by the SQL Server service need create file and write permis
sions on the directory.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andres Perales" <andres@.andresperales.com> wrote in message
news:eu%23YtAyIHHA.1248@.TK2MSFTNGP03.phx.gbl...
>I have a server with SQL 2000 and a name instance of SQL 2005, I am trying
to use the copy wizard
>to move databases from SQL2000 to SQL2005, when I do this and to try to cha
nge the drive letters to
>my D: drive for the logs and E: drive for the database, it goes through the
process and fails. So
>I have tried it again this time to the default location that SQL 2005 wants
, which is on the C:
>drive - of course this is not acceptable, but it works that way. I figure
it is a NTFS /
>permissions issue. But what permissions do I need to setup on the other dri
ve D: and E: to get this
>to work properly, anyone please help me.
> Thanks,
> Andres
> andres.perales@.mclaneat.com
>
>
to use the copy wizard to move databases from SQL2000 to SQL2005, when I do
this and to try to change the drive letters to my D: drive for the logs and
E: drive for the database, it goes through the process and fails. So I have
tried it again this time to the default location that SQL 2005 wants, which
is on the C: drive - of course this is not acceptable, but it works that
way. I figure it is a NTFS / permissions issue. But what permissions do I
need to setup on the other drive D: and E: to get this to work properly,
anyone please help me.
Thanks,
Andres
andres.perales@.mclaneat.comHi
Take a look at RESTORE command WITH MOVE option in the BOL
"Andres Perales" <andres@.andresperales.com> wrote in message
news:eu%23YtAyIHHA.1248@.TK2MSFTNGP03.phx.gbl...
>I have a server with SQL 2000 and a name instance of SQL 2005, I am trying
>to use the copy wizard to move databases from SQL2000 to SQL2005, when I do
>this and to try to change the drive letters to my D: drive for the logs and
>E: drive for the database, it goes through the process and fails. So I
>have tried it again this time to the default location that SQL 2005 wants,
>which is on the C: drive - of course this is not acceptable, but it works
>that way. I figure it is a NTFS / permissions issue. But what permissions
>do I need to setup on the other drive D: and E: to get this to work
>properly, anyone please help me.
> Thanks,
> Andres
> andres.perales@.mclaneat.com
>
>|||Assuming the RESTORE command is correct (you have used the MOVE options corr
ectly):
The account used by the SQL Server service need create file and write permis
sions on the directory.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andres Perales" <andres@.andresperales.com> wrote in message
news:eu%23YtAyIHHA.1248@.TK2MSFTNGP03.phx.gbl...
>I have a server with SQL 2000 and a name instance of SQL 2005, I am trying
to use the copy wizard
>to move databases from SQL2000 to SQL2005, when I do this and to try to cha
nge the drive letters to
>my D: drive for the logs and E: drive for the database, it goes through the
process and fails. So
>I have tried it again this time to the default location that SQL 2005 wants
, which is on the C:
>drive - of course this is not acceptable, but it works that way. I figure
it is a NTFS /
>permissions issue. But what permissions do I need to setup on the other dri
ve D: and E: to get this
>to work properly, anyone please help me.
> Thanks,
> Andres
> andres.perales@.mclaneat.com
>
>
Disk permission to move SQL 2005 databases too...
I have a server with SQL 2000 and a name instance of SQL 2005, I am trying
to use the copy wizard to move databases from SQL2000 to SQL2005, when I do
this and to try to change the drive letters to my D: drive for the logs and
E: drive for the database, it goes through the process and fails. So I have
tried it again this time to the default location that SQL 2005 wants, which
is on the C: drive - of course this is not acceptable, but it works that
way. I figure it is a NTFS / permissions issue. But what permissions do I
need to setup on the other drive D: and E: to get this to work properly,
anyone please help me.
Thanks,
Andres
andres.perales@.mclaneat.comHi
Take a look at RESTORE command WITH MOVE option in the BOL
"Andres Perales" <andres@.andresperales.com> wrote in message
news:eu%23YtAyIHHA.1248@.TK2MSFTNGP03.phx.gbl...
>I have a server with SQL 2000 and a name instance of SQL 2005, I am trying
>to use the copy wizard to move databases from SQL2000 to SQL2005, when I do
>this and to try to change the drive letters to my D: drive for the logs and
>E: drive for the database, it goes through the process and fails. So I
>have tried it again this time to the default location that SQL 2005 wants,
>which is on the C: drive - of course this is not acceptable, but it works
>that way. I figure it is a NTFS / permissions issue. But what permissions
>do I need to setup on the other drive D: and E: to get this to work
>properly, anyone please help me.
> Thanks,
> Andres
> andres.perales@.mclaneat.com
>
>|||Assuming the RESTORE command is correct (you have used the MOVE options correctly):
The account used by the SQL Server service need create file and write permissions on the directory.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andres Perales" <andres@.andresperales.com> wrote in message
news:eu%23YtAyIHHA.1248@.TK2MSFTNGP03.phx.gbl...
>I have a server with SQL 2000 and a name instance of SQL 2005, I am trying to use the copy wizard
>to move databases from SQL2000 to SQL2005, when I do this and to try to change the drive letters to
>my D: drive for the logs and E: drive for the database, it goes through the process and fails. So
>I have tried it again this time to the default location that SQL 2005 wants, which is on the C:
>drive - of course this is not acceptable, but it works that way. I figure it is a NTFS /
>permissions issue. But what permissions do I need to setup on the other drive D: and E: to get this
>to work properly, anyone please help me.
> Thanks,
> Andres
> andres.perales@.mclaneat.com
>
>sql
to use the copy wizard to move databases from SQL2000 to SQL2005, when I do
this and to try to change the drive letters to my D: drive for the logs and
E: drive for the database, it goes through the process and fails. So I have
tried it again this time to the default location that SQL 2005 wants, which
is on the C: drive - of course this is not acceptable, but it works that
way. I figure it is a NTFS / permissions issue. But what permissions do I
need to setup on the other drive D: and E: to get this to work properly,
anyone please help me.
Thanks,
Andres
andres.perales@.mclaneat.comHi
Take a look at RESTORE command WITH MOVE option in the BOL
"Andres Perales" <andres@.andresperales.com> wrote in message
news:eu%23YtAyIHHA.1248@.TK2MSFTNGP03.phx.gbl...
>I have a server with SQL 2000 and a name instance of SQL 2005, I am trying
>to use the copy wizard to move databases from SQL2000 to SQL2005, when I do
>this and to try to change the drive letters to my D: drive for the logs and
>E: drive for the database, it goes through the process and fails. So I
>have tried it again this time to the default location that SQL 2005 wants,
>which is on the C: drive - of course this is not acceptable, but it works
>that way. I figure it is a NTFS / permissions issue. But what permissions
>do I need to setup on the other drive D: and E: to get this to work
>properly, anyone please help me.
> Thanks,
> Andres
> andres.perales@.mclaneat.com
>
>|||Assuming the RESTORE command is correct (you have used the MOVE options correctly):
The account used by the SQL Server service need create file and write permissions on the directory.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andres Perales" <andres@.andresperales.com> wrote in message
news:eu%23YtAyIHHA.1248@.TK2MSFTNGP03.phx.gbl...
>I have a server with SQL 2000 and a name instance of SQL 2005, I am trying to use the copy wizard
>to move databases from SQL2000 to SQL2005, when I do this and to try to change the drive letters to
>my D: drive for the logs and E: drive for the database, it goes through the process and fails. So
>I have tried it again this time to the default location that SQL 2005 wants, which is on the C:
>drive - of course this is not acceptable, but it works that way. I figure it is a NTFS /
>permissions issue. But what permissions do I need to setup on the other drive D: and E: to get this
>to work properly, anyone please help me.
> Thanks,
> Andres
> andres.perales@.mclaneat.com
>
>sql
2012年3月8日星期四
Disaster Recovery
Win2003 Ent Ed. SQL2005 Std 2-node A/P
Is the Windows Backup utility the only tool I need? Is there anything this
backup tool does not cover? Any issues with?
tia,
Chris
It works nicely. Though nothing beats a dry run where you actually test the
tool.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:8F3F75C8-A908-4827-800C-BE94DFBDE9EF@.microsoft.com...
> Win2003 Ent Ed. SQL2005 Std 2-node A/P
> Is the Windows Backup utility the only tool I need? Is there anything this
> backup tool does not cover? Any issues with?
> tia,
> Chris
|||Until you test a backup by restoring, you don't have recovery plan, you
have a recovery hope.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:8F3F75C8-A908-4827-800C-BE94DFBDE9EF@.microsoft.com...
> Win2003 Ent Ed. SQL2005 Std 2-node A/P
> Is the Windows Backup utility the only tool I need? Is there anything this
> backup tool does not cover? Any issues with?
> tia,
> Chris
|||"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23Bz2vQSNHHA.3288@.TK2MSFTNGP03.phx.gbl...
> Until you test a backup by restoring, you don't have recovery plan, you
> have a recovery hope.
I am sssoooo going to steal that!
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Denver starting Feb 12th
NYC starting Feb 19th
|||Geoff is the man Russ!
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Russ Kaufmann [MVP]" <russ@.clusterhelp.com> wrote in message
news:OGPDNuZNHHA.3552@.TK2MSFTNGP03.phx.gbl...
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23Bz2vQSNHHA.3288@.TK2MSFTNGP03.phx.gbl...
> I am sssoooo going to steal that!
>
> --
> Russ Kaufmann
> MVP - Windows Server - Clustering
> ClusterHelp.com, a Microsoft Certified Gold Partner
> Web http://www.clusterhelp.com
> Blog http://msmvps.com/clusterhelp
> The next ClusterHelp classes are:
> Denver starting Feb 12th
> NYC starting Feb 19th
>
|||This just made my blog its so good...
And I'm "re-using the code" as well
Thanks Geoff
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23Bz2vQSNHHA.3288@.TK2MSFTNGP03.phx.gbl...
> Until you test a backup by restoring, you don't have recovery plan, you
> have a recovery hope.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:8F3F75C8-A908-4827-800C-BE94DFBDE9EF@.microsoft.com...
>
Is the Windows Backup utility the only tool I need? Is there anything this
backup tool does not cover? Any issues with?
tia,
Chris
It works nicely. Though nothing beats a dry run where you actually test the
tool.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:8F3F75C8-A908-4827-800C-BE94DFBDE9EF@.microsoft.com...
> Win2003 Ent Ed. SQL2005 Std 2-node A/P
> Is the Windows Backup utility the only tool I need? Is there anything this
> backup tool does not cover? Any issues with?
> tia,
> Chris
|||Until you test a backup by restoring, you don't have recovery plan, you
have a recovery hope.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:8F3F75C8-A908-4827-800C-BE94DFBDE9EF@.microsoft.com...
> Win2003 Ent Ed. SQL2005 Std 2-node A/P
> Is the Windows Backup utility the only tool I need? Is there anything this
> backup tool does not cover? Any issues with?
> tia,
> Chris
|||"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23Bz2vQSNHHA.3288@.TK2MSFTNGP03.phx.gbl...
> Until you test a backup by restoring, you don't have recovery plan, you
> have a recovery hope.
I am sssoooo going to steal that!
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Denver starting Feb 12th
NYC starting Feb 19th
|||Geoff is the man Russ!
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Russ Kaufmann [MVP]" <russ@.clusterhelp.com> wrote in message
news:OGPDNuZNHHA.3552@.TK2MSFTNGP03.phx.gbl...
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23Bz2vQSNHHA.3288@.TK2MSFTNGP03.phx.gbl...
> I am sssoooo going to steal that!
>
> --
> Russ Kaufmann
> MVP - Windows Server - Clustering
> ClusterHelp.com, a Microsoft Certified Gold Partner
> Web http://www.clusterhelp.com
> Blog http://msmvps.com/clusterhelp
> The next ClusterHelp classes are:
> Denver starting Feb 12th
> NYC starting Feb 19th
>
|||This just made my blog its so good...
And I'm "re-using the code" as well
Thanks Geoff
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23Bz2vQSNHHA.3288@.TK2MSFTNGP03.phx.gbl...
> Until you test a backup by restoring, you don't have recovery plan, you
> have a recovery hope.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:8F3F75C8-A908-4827-800C-BE94DFBDE9EF@.microsoft.com...
>
Disaster - Recovery Order of events
we are trying to simulate a disater recovery of our SQL2000 and SQL2005 development servers. Which is the order in which we should restore the DBs. I am talking specifically of MSDB, master and user DBs; should we restore user DBs before master and MSDB?
Thanks,
CarlosGenerally, you restore master first, then model(if you made any changes to it), and msdb. After that, all the user databases should be restored. THis goes for SQL 2000 and SQL 2005.|||Generally I have a standby box|||lucky little %^*)|||lucky little %^*)
He didn't say WHAT kind of box. It's actually a box of 64 crayola crayons.
Regards,
hmscott|||i thought the first thing to do was to start blaming other people. maybe followed by some frantic yelling all around the office.
maybe Brett has a squeezebox. But wait, if he has a squeezebox who doesn't sleep at night? I am confused. Back to writing code.
Thanks,
CarlosGenerally, you restore master first, then model(if you made any changes to it), and msdb. After that, all the user databases should be restored. THis goes for SQL 2000 and SQL 2005.|||Generally I have a standby box|||lucky little %^*)|||lucky little %^*)
He didn't say WHAT kind of box. It's actually a box of 64 crayola crayons.
Regards,
hmscott|||i thought the first thing to do was to start blaming other people. maybe followed by some frantic yelling all around the office.
maybe Brett has a squeezebox. But wait, if he has a squeezebox who doesn't sleep at night? I am confused. Back to writing code.
Disaster - Recovery Order of events
we are trying to simulate a disater recovery of our SQL2000 and SQL2005
development servers. Which is the order in which we should restore the DBs. I
am talking specifically of MSDB, master and user DBs; should we restore user
DBs before master and MSDB?
Thanks,
CarlosHi
http://msdn2.microsoft.com/en-us/library/ms190190.aspx
"Carlos" <carlosarango@.SQLserver.com> wrote in message
news:580A4901-C15A-4694-8EBF-A9E84B7075E1@.microsoft.com...
> we are trying to simulate a disater recovery of our SQL2000 and SQL2005
> development servers. Which is the order in which we should restore the
> DBs. I
> am talking specifically of MSDB, master and user DBs; should we restore
> user
> DBs before master and MSDB?
> Thanks,
> Carlos|||Thanks Uri
Carlos
"Uri Dimant" wrote:
> Hi
> http://msdn2.microsoft.com/en-us/library/ms190190.aspx
>
> "Carlos" <carlosarango@.SQLserver.com> wrote in message
> news:580A4901-C15A-4694-8EBF-A9E84B7075E1@.microsoft.com...
> > we are trying to simulate a disater recovery of our SQL2000 and SQL2005
> > development servers. Which is the order in which we should restore the
> > DBs. I
> > am talking specifically of MSDB, master and user DBs; should we restore
> > user
> > DBs before master and MSDB?
> >
> > Thanks,
> >
> > Carlos
>
>
development servers. Which is the order in which we should restore the DBs. I
am talking specifically of MSDB, master and user DBs; should we restore user
DBs before master and MSDB?
Thanks,
CarlosHi
http://msdn2.microsoft.com/en-us/library/ms190190.aspx
"Carlos" <carlosarango@.SQLserver.com> wrote in message
news:580A4901-C15A-4694-8EBF-A9E84B7075E1@.microsoft.com...
> we are trying to simulate a disater recovery of our SQL2000 and SQL2005
> development servers. Which is the order in which we should restore the
> DBs. I
> am talking specifically of MSDB, master and user DBs; should we restore
> user
> DBs before master and MSDB?
> Thanks,
> Carlos|||Thanks Uri
Carlos
"Uri Dimant" wrote:
> Hi
> http://msdn2.microsoft.com/en-us/library/ms190190.aspx
>
> "Carlos" <carlosarango@.SQLserver.com> wrote in message
> news:580A4901-C15A-4694-8EBF-A9E84B7075E1@.microsoft.com...
> > we are trying to simulate a disater recovery of our SQL2000 and SQL2005
> > development servers. Which is the order in which we should restore the
> > DBs. I
> > am talking specifically of MSDB, master and user DBs; should we restore
> > user
> > DBs before master and MSDB?
> >
> > Thanks,
> >
> > Carlos
>
>
2012年2月19日星期日
Disable Sysadmin to view metadata in SQL2005
Hi Everyone,
Is there any way we can disable sysadmin/sa to view metadata on a
particular database in SQL2005?
Thanks,
DexThere better not be an option to do that; it would be insane to do it.
Tim S
"Dex" <dplaras@.hotmail.com> wrote in message
news:1153253585.004826.199140@.75g2000cwc.googlegroups.com...
> Hi Everyone,
> Is there any way we can disable sysadmin/sa to view metadata on a
> particular database in SQL2005?
> Thanks,
> Dex
>|||Hi Tim,
There's a SQL statement in 2005 that disables users view access of the
metadata. I think it's View Any Database / View Server State/ View
Definition. My question is that if we can disable SA account to view
the metadata (tables, columns, etc)?
Thanks,
Dex
Tim Stahlhut wrote:[vbcol=seagreen]
> There better not be an option to do that; it would be insane to do it.
> Tim S
> "Dex" <dplaras@.hotmail.com> wrote in message
> news:1153253585.004826.199140@.75g2000cwc.googlegroups.com...|||You cannot deny permissions to a sysadmin, so you cannot prevent him to
access information that, by definition, he is supposed to access.
You can, however, restrict who is a sysadmin and if you need other users to
perform administrative tasks, look at granting only the minimal permissions
required to perform those tasks. If the permissions are not granular enough,
look at granting access via signed code - this way you can avoid granting
the permissions required by the operation and instead you can grant EXECUTE
permission on code that "packs" the access to the operation.
Thanks
Laurentiu Cristofor [MSFT]
Software Design Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dex" <dplaras@.hotmail.com> wrote in message
news:1153258018.919768.201370@.m79g2000cwm.googlegroups.com...
> Hi Tim,
> There's a SQL statement in 2005 that disables users view access of the
> metadata. I think it's View Any Database / View Server State/ View
> Definition. My question is that if we can disable SA account to view
> the metadata (tables, columns, etc)?
> Thanks,
> Dex
> Tim Stahlhut wrote:
>|||Thank you so much! So what do you recommend/best practices in
deploying a system to another clients so that they won't see database
schemas, given the fact that they have sysadmin rights to that box? In
the data layer, we're implementing encryption in a couple of key fields
so that even sysadmin won't be able to see those info?
Thanks again for your help!
Dex
Laurentiu Cristofor [MSFT] wrote:[vbcol=seagreen]
> You cannot deny permissions to a sysadmin, so you cannot prevent him to
> access information that, by definition, he is supposed to access.
> You can, however, restrict who is a sysadmin and if you need other users t
o
> perform administrative tasks, look at granting only the minimal permission
s
> required to perform those tasks. If the permissions are not granular enoug
h,
> look at granting access via signed code - this way you can avoid granting
> the permissions required by the operation and instead you can grant EXECUT
E
> permission on code that "packs" the access to the operation.
> Thanks
> --
> Laurentiu Cristofor [MSFT]
> Software Design Engineer
> SQL Server Engine
> http://blogs.msdn.com/lcris/
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Dex" <dplaras@.hotmail.com> wrote in message
> news:1153258018.919768.201370@.m79g2000cwm.googlegroups.com...|||In this case, you are looking for a DRM solution for your database. SQL
Server does not provide such a solution. This issue has also been discussed
in the following threads:
http://forums.microsoft.com/MSDN/Sh...=52094&SiteID=1
http://forums.microsoft.com/MSDN/Sh...371562&SiteID=1
Thanks
Laurentiu Cristofor [MSFT]
Software Design Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dex" <dplaras@.hotmail.com> wrote in message
news:1153259304.913735.140010@.p79g2000cwp.googlegroups.com...
> Thank you so much! So what do you recommend/best practices in
> deploying a system to another clients so that they won't see database
> schemas, given the fact that they have sysadmin rights to that box? In
> the data layer, we're implementing encryption in a couple of key fields
> so that even sysadmin won't be able to see those info?
> Thanks again for your help!
> Dex
> Laurentiu Cristofor [MSFT] wrote:
>
Is there any way we can disable sysadmin/sa to view metadata on a
particular database in SQL2005?
Thanks,
DexThere better not be an option to do that; it would be insane to do it.
Tim S
"Dex" <dplaras@.hotmail.com> wrote in message
news:1153253585.004826.199140@.75g2000cwc.googlegroups.com...
> Hi Everyone,
> Is there any way we can disable sysadmin/sa to view metadata on a
> particular database in SQL2005?
> Thanks,
> Dex
>|||Hi Tim,
There's a SQL statement in 2005 that disables users view access of the
metadata. I think it's View Any Database / View Server State/ View
Definition. My question is that if we can disable SA account to view
the metadata (tables, columns, etc)?
Thanks,
Dex
Tim Stahlhut wrote:[vbcol=seagreen]
> There better not be an option to do that; it would be insane to do it.
> Tim S
> "Dex" <dplaras@.hotmail.com> wrote in message
> news:1153253585.004826.199140@.75g2000cwc.googlegroups.com...|||You cannot deny permissions to a sysadmin, so you cannot prevent him to
access information that, by definition, he is supposed to access.
You can, however, restrict who is a sysadmin and if you need other users to
perform administrative tasks, look at granting only the minimal permissions
required to perform those tasks. If the permissions are not granular enough,
look at granting access via signed code - this way you can avoid granting
the permissions required by the operation and instead you can grant EXECUTE
permission on code that "packs" the access to the operation.
Thanks
Laurentiu Cristofor [MSFT]
Software Design Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dex" <dplaras@.hotmail.com> wrote in message
news:1153258018.919768.201370@.m79g2000cwm.googlegroups.com...
> Hi Tim,
> There's a SQL statement in 2005 that disables users view access of the
> metadata. I think it's View Any Database / View Server State/ View
> Definition. My question is that if we can disable SA account to view
> the metadata (tables, columns, etc)?
> Thanks,
> Dex
> Tim Stahlhut wrote:
>|||Thank you so much! So what do you recommend/best practices in
deploying a system to another clients so that they won't see database
schemas, given the fact that they have sysadmin rights to that box? In
the data layer, we're implementing encryption in a couple of key fields
so that even sysadmin won't be able to see those info?
Thanks again for your help!
Dex
Laurentiu Cristofor [MSFT] wrote:[vbcol=seagreen]
> You cannot deny permissions to a sysadmin, so you cannot prevent him to
> access information that, by definition, he is supposed to access.
> You can, however, restrict who is a sysadmin and if you need other users t
o
> perform administrative tasks, look at granting only the minimal permission
s
> required to perform those tasks. If the permissions are not granular enoug
h,
> look at granting access via signed code - this way you can avoid granting
> the permissions required by the operation and instead you can grant EXECUT
E
> permission on code that "packs" the access to the operation.
> Thanks
> --
> Laurentiu Cristofor [MSFT]
> Software Design Engineer
> SQL Server Engine
> http://blogs.msdn.com/lcris/
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Dex" <dplaras@.hotmail.com> wrote in message
> news:1153258018.919768.201370@.m79g2000cwm.googlegroups.com...|||In this case, you are looking for a DRM solution for your database. SQL
Server does not provide such a solution. This issue has also been discussed
in the following threads:
http://forums.microsoft.com/MSDN/Sh...=52094&SiteID=1
http://forums.microsoft.com/MSDN/Sh...371562&SiteID=1
Thanks
Laurentiu Cristofor [MSFT]
Software Design Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dex" <dplaras@.hotmail.com> wrote in message
news:1153259304.913735.140010@.p79g2000cwp.googlegroups.com...
> Thank you so much! So what do you recommend/best practices in
> deploying a system to another clients so that they won't see database
> schemas, given the fact that they have sysadmin rights to that box? In
> the data layer, we're implementing encryption in a couple of key fields
> so that even sysadmin won't be able to see those info?
> Thanks again for your help!
> Dex
> Laurentiu Cristofor [MSFT] wrote:
>
订阅：
博文 (Atom)