restrict user access

how can i set the user access level for sql 2000 server?
i want to restrict the user only can query/add table/ drop table/ modify
data/import & export data
but don't allow them to view other services such as "Management,
Replication, Security...etc"
which standard role i can choose or need to create a custom role for this?
btw, Although user can view the content of other user, but they still can
see the name of DB? how can avoid this?
Thanks in advanced.
Hi
> i want to restrict the user only can query/add table/ drop table/ modify
> data/import & export data
Thats all what you want ? :-))))
Well first of all you need to create a login to SQL Server for this person.
Then grant an access to the database
As I see your requirements you are going to put them into db_owner database
role.
For more details please refer to the BOL.
"beachboy" <stanley@.javacatz.com> wrote in message
news:%23SgC77JIGHA.740@.TK2MSFTNGP12.phx.gbl...
> how can i set the user access level for sql 2000 server?
> i want to restrict the user only can query/add table/ drop table/ modify
> data/import & export data
> but don't allow them to view other services such as "Management,
> Replication, Security...etc"
> which standard role i can choose or need to create a custom role for this?
> btw, Although user can view the content of other user, but they still can
> see the name of DB? how can avoid this?
> Thanks in advanced.
>

restrict user access

how can i set the user access level for sql 2000 server?
i want to restrict the user only can query/add table/ drop table/ modify
data/import & export data
but don't allow them to view other services such as "Management,
Replication, Security...etc"
which standard role i can choose or need to create a custom role for this?
btw, Although user can view the content of other user, but they still can
see the name of DB? how can avoid this?
Thanks in advanced.Hi
> i want to restrict the user only can query/add table/ drop table/ modify
> data/import & export data
Thats all what you want ? :-))))
Well first of all you need to create a login to SQL Server for this person.
Then grant an access to the database
As I see your requirements you are going to put them into db_owner database
role.
For more details please refer to the BOL.
"beachboy" <stanley@.javacatz.com> wrote in message
news:%23SgC77JIGHA.740@.TK2MSFTNGP12.phx.gbl...
> how can i set the user access level for sql 2000 server?
> i want to restrict the user only can query/add table/ drop table/ modify
> data/import & export data
> but don't allow them to view other services such as "Management,
> Replication, Security...etc"
> which standard role i can choose or need to create a custom role for this?
> btw, Although user can view the content of other user, but they still can
> see the name of DB? how can avoid this?
> Thanks in advanced.
>

restrict user access

how can i set the user access level for sql 2000 server?
i want to restrict the user only can query/add table/ drop table/ modify
data/import & export data
but don't allow them to view other services such as "Management,
Replication, Security...etc"
which standard role i can choose or need to create a custom role for this?
btw, Although user can view the content of other user, but they still can
see the name of DB? how can avoid this?
Thanks in advanced.Hi
> i want to restrict the user only can query/add table/ drop table/ modify
> data/import & export data
Thats all what you want ? :-))))
Well first of all you need to create a login to SQL Server for this person.
Then grant an access to the database
As I see your requirements you are going to put them into db_owner database
role.
For more details please refer to the BOL.
"beachboy" <stanley@.javacatz.com> wrote in message
news:%23SgC77JIGHA.740@.TK2MSFTNGP12.phx.gbl...
> how can i set the user access level for sql 2000 server?
> i want to restrict the user only can query/add table/ drop table/ modify
> data/import & export data
> but don't allow them to view other services such as "Management,
> Replication, Security...etc"
> which standard role i can choose or need to create a custom role for this?
> btw, Although user can view the content of other user, but they still can
> see the name of DB? how can avoid this?
> Thanks in advanced.
>sql

Restoring to a different directory structure

We are trying to import our backups made on one SQL Server 2000
machine to another SQL Server 2000 machine. The problem is the
directory structures are different. After the import is done, I get
errors trying to start SQL Server. I have to move the master database
around. This makes me wonder what other things are in the wrong place?
What other problems will we have? etc.
I don't understand what the problem is exactly, shouldn't SQL Server
import the database and put its files wherever the current 'data'
directory is?
The source server was originally running 7.0, which we upgraded in
place to 2000. All the sql server directories, like data, repldata,
ftdata, logs, etc are in our d:\database directory.
On the destination server, it is a fresh install of SQL Server 2000. I
tried to specify "d:\database" as our data directory when installing,
but it insists on creating an MSSQL directory, and then putting all of
its directories within that directory (argghhh!!).
Any ideas?
Thanks,
ThomasThomas,
you should use the MOVE option of the Restore command. Check for syntax in
Books OnLine.
--
Dejan Sarka, SQL Server MVP
Please reply only to the newsgroups.
"Thomas" <thomas-ggl-01@.data.iatn.net> wrote in message
news:4f2cac50.0311100913.21169934@.posting.google.com...
> We are trying to import our backups made on one SQL Server 2000
> machine to another SQL Server 2000 machine. The problem is the
> directory structures are different. After the import is done, I get
> errors trying to start SQL Server. I have to move the master database
> around. This makes me wonder what other things are in the wrong place?
> What other problems will we have? etc.
> I don't understand what the problem is exactly, shouldn't SQL Server
> import the database and put its files wherever the current 'data'
> directory is?
> The source server was originally running 7.0, which we upgraded in
> place to 2000. All the sql server directories, like data, repldata,
> ftdata, logs, etc are in our d:\database directory.
> On the destination server, it is a fresh install of SQL Server 2000. I
> tried to specify "d:\database" as our data directory when installing,
> but it insists on creating an MSSQL directory, and then putting all of
> its directories within that directory (argghhh!!).
> Any ideas?
> Thanks,
> Thomassql

Restoring SQL 2005 Analysis service database backup on SQL 2000

Hello
I think the subject line says it all.
Is there any way to import my cubes, measures from SQL 2005 Analysis
service to SQL 2000 Analysis service database.
Madhur> I think the subject line says it all.
> Is there any way to import my cubes, measures from SQL 2005 Analysis
> service to SQL 2000 Analysis service database.
I do not think so. If you have a data warehouse, you can create a fresh OLAP
2000 cube. If not, you have problems. What you could do is you could
regenerate a SSAS 2005 project with BI Dev Studio, then generate the DW
schema in a relational database from the project, and finally generate the
OLAP 2000 cube from the DW. You have to export the data from the SSAS UDM to
the DW and then process the OLAP 2000 cube.
maybe I am wrong, but at the moment, I cannot imagine an easier process.
--
Dejan Sarka
http://www.solidqualitylearning.com/blogs/

Restoring SQL 2005 Analysis service database backup on SQL 2000

Hello
I think the subject line says it all.
Is there any way to import my cubes, measures from SQL 2005 Analysis
service to SQL 2000 Analysis service database.
Madhur> I think the subject line says it all.
> Is there any way to import my cubes, measures from SQL 2005 Analysis
> service to SQL 2000 Analysis service database.
I do not think so. If you have a data warehouse, you can create a fresh OLAP
2000 cube. If not, you have problems. What you could do is you could
regenerate a SSAS 2005 project with BI Dev Studio, then generate the DW
schema in a relational database from the project, and finally generate the
OLAP 2000 cube from the DW. You have to export the data from the SSAS UDM to
the DW and then process the OLAP 2000 cube.
maybe I am wrong, but at the moment, I cannot imagine an easier process.
Dejan Sarka
http://www.solidqualitylearning.com/blogs/

Restoring Linux ANSI_SQL to SQL 2005

Our firm needs to analyze some financial data for a client. They gave us a SQL database file in ANSI format. Is there a way to import this data into SQL 2005?

Thanks,

Steve

If the data is in a 'standard' format, and If you have a good data map, then you 'should' be able to use SSIS, or the IMPORT Wizard, to import the data into a functioning SQL Server.|||

Arnie,

Thanks for the reply. Do I need to contact the client to get column types and widths, etc?

Steve

|||I would definitely want some way to undertand what data is in the data file, and how it is organized. So that sounds like a good plan. -Unless you can open the datafile and inspect the format.