Remove all permission restrictions

I have a site where my client attempted to change a lot of
authenticated users and I helped (aided and abetted?) him by scripting
over the previouls permissions. We are having a lot of problems now and
want to get back to a completely public editable and open database
before replanning roles and users and restricting rights.
To further complicate the issue, this database is a publisher and
although we have generated a snapshot, we haven't deployed it until
this is fixed - we don't want two sites where users can't see or edit
the data!
I would like to know the simplest way to make the database owned by
dbo, strip all non system users and roles, and to be able to make NT
Authority/Authenticated Users members of the dbowner role.
Thanks
Steve SoltSteve
> I would like to know the simplest way to make the database owned by
> dbo, strip all non system users and roles, and to be able to make NT
> Authority/Authenticated Users members of the dbowner role.
>
Take a look at sp_changedbowner system stored procedure
<s.solt@.czwgarchitects.co.uk> wrote in message
news:1160671910.190428.264470@.h48g2000cwc.googlegroups.com...
>I have a site where my client attempted to change a lot of
> authenticated users and I helped (aided and abetted?) him by scripting
> over the previouls permissions. We are having a lot of problems now and
> want to get back to a completely public editable and open database
> before replanning roles and users and restricting rights.
> To further complicate the issue, this database is a publisher and
> although we have generated a snapshot, we haven't deployed it until
> this is fixed - we don't want two sites where users can't see or edit
> the data!
> I would like to know the simplest way to make the database owned by
> dbo, strip all non system users and roles, and to be able to make NT
> Authority/Authenticated Users members of the dbowner role.
> Thanks
> Steve Solt
>

Remote XML transfer

hello there,
I currently have a vb client application that outputs details to a well
formed xml document.
my question is, how can i send this information (automated) to my sql server
2005 ?
Im able to load the xml document locally, into a xml datatype and retrive it
fine, however the need is to complete this from a cleint machine across a
network.
I have looked for many examples but none seem to fit what im after.
any one help ?
regards
russ.
If you are using VB.NET then you can use ADO.NET to either insert the xml
into a table or pass the xml as a parameter to a stored procedure.
For an example of how this can be done in ADO.NET 2.0 see:
http://msdn.microsoft.com/data/DataA...sqlxml_ado.asp
Regards,
Galex Yen
"grumpy" wrote:

> hello there,
> I currently have a vb client application that outputs details to a well
> formed xml document.
> my question is, how can i send this information (automated) to my sql server
> 2005 ?
> Im able to load the xml document locally, into a xml datatype and retrive it
> fine, however the need is to complete this from a cleint machine across a
> network.
> I have looked for many examples but none seem to fit what im after.
> any one help ?
> regards
> russ.
>
>
>

Remote XML transfer

hello there,
I currently have a vb client application that outputs details to a well
formed xml document.
my question is, how can i send this information (automated) to my sql server
2005 ?
Im able to load the xml document locally, into a xml datatype and retrive it
fine, however the need is to complete this from a cleint machine across a
network.
I have looked for many examples but none seem to fit what im after.
any one help ?
regards
russ.If you are using VB.NET then you can use ADO.NET to either insert the xml
into a table or pass the xml as a parameter to a stored procedure.
For an example of how this can be done in ADO.NET 2.0 see:
http://msdn.microsoft.com/data/Data.../sqlxml_ado.asp
Regards,
Galex Yen
"grumpy" wrote:

> hello there,
> I currently have a vb client application that outputs details to a well
> formed xml document.
> my question is, how can i send this information (automated) to my sql serv
er
> 2005 ?
> Im able to load the xml document locally, into a xml datatype and retrive
it
> fine, however the need is to complete this from a cleint machine across a
> network.
> I have looked for many examples but none seem to fit what im after.
> any one help ?
> regards
> russ.
>
>
>

Remote tools install error

I am trying to install SQL server 2000 client tools on to a Win 2000 server.
I get an install error
' installation of MS data access components failed (-).
My server is service pack 3. I understand that that Win 2 K service pack 3
installs MDAC 2.5 SP3.
My MDAC version is 2.53.6200.1
Has anyone seen this error before and is there a fix for getting the client
tools install to work?
Thanks.
JTThanks for your replies. My struggle continues.
I was able to run sqlsetup in debug mode and installed all other client tool
components other than mdac.
I ran mdac component checker to confirm that I am running mdac version 2.5
SP3 - no conflicts seen with the component checker.
I tried to install mdac 6 from the SQL server disk, but the install appeared
to do nothing.
I downloaded mdac 2.6 SP1 and tried to install it but it failed.
I tried to uninstall the sql tools install but it fails with msg ' internal
error - unable to load or call an external .dll
I have tried to reinstall the tools through the setup maintenance mode. It
appears to install a few files and then finishes, but I can't get in to
Enterprise Mgr or any of the other tools.
I deleted the ExceptionComponents reg key, and attempted to reinstall, but I
am getting nowhere with that.
I am trying to install this on a W2K server w/ terminal services running. I
stopped the terminal services service and tried again to install, but I am
not making any progress with that either.
So how does one uninstall these client tools and start over?
Thanks.
"Dinesh.T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:ugUwZspZDHA.2032@.TK2MSFTNGP10.phx.gbl...
> Jane,
> I have listed some options in..
> Q: "Installation of the Microsoft Data Access Components package failed.
> (-1)"-- Error occurs during setup ?
> http://www.tkdinesh.com/faq/ans/MDACerr.html
>
> --
> Dinesh.
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Jane Tunnicliff" <jtunn@.uwpn.org> wrote in message
> news:O41l$opZDHA.2548@.TK2MSFTNGP09.phx.gbl...
> > I am trying to install SQL server 2000 client tools on to a Win 2000
> server.
> > I get an install error
> > ' installation of MS data access components failed (-).
> >
> > My server is service pack 3. I understand that that Win 2 K service
pack
> 3
> > installs MDAC 2.5 SP3.
> > My MDAC version is 2.53.6200.1
> >
> > Has anyone seen this error before and is there a fix for getting the
> client
> > tools install to work?
> >
> > Thanks.
> >
> > JT
> >
> >
>

Remote Database Deployment

We have an application using a SQL 2005 database which we need to deploy to a client. The only we can find of deploying the structure and the data is to perform a backup on the source server and a restore on the destination server.

Is this really the best/only way to deploy a database? I'd appreciate any pointers.

Thanks in advance

LazyGenius wrote:

We have an application using a SQL 2005 database which we need to deploy to a client. The only we can find of deploying the structure and the data is to perform a backup on the source server and a restore on the destination server.

Is this really the best/only way to deploy a database? I'd appreciate any pointers.

Thanks in advance

If you're using SQL 2005 you don't even need to backup/restore. You can just Xcopy your mdf (and optionally ldf) files and do an attach.

|||

It all seems a bit "DOS" to me but thanks for the quick reply. We have a small utility program to attach the database so I guess we'll just use that.

Thanks again

|||

Hey you asked for a better way of doing it. Think of the time that it would take to backup and restore a large database. Compare that with detaching it, making a copy, and attaching that copy on the other end.

Remote connection question

Hi

I have a server with windows 2003 and SQL Server 2005 installed.

When I use the client on the server to connect to the database (using windows authentication) it does this no problem. And when remotely connecting (using SQL authentication) it 'seems' to do it no problem as well.

However in "SQL Sevrer Management Studio" on the server when I connect it displays the server name with a nice green circle with a little arrow inside. On the remote computer it 'seems' to connect but I don't get the green circle with the arrow next to the server (just get a white circle) - Hope this all makes sense.

I get the feeling I can 'see' the server but can't connect properly. Is this common behaviour (white circle) or have I made a 'school boy error' somewhere along the way!?

Any help/suggestions would be much appreciated. Thanks in advance!

Regards

Toby

Would you go to Surface Area Configuration to enable Remote Connection?|||

Surface Area Configuration is setup correctly (on the server):

Database Engine/Remote Connections => Local and Remote Connections - using both TCP/IP and named pipes.

|||

Just to clarify where I am and what I have tried

Basically on the remote computer I log in with "sa" and it says it connects, but it doesn't look/behave like its connected. And on the server I log in with windows authentication and it connects no problem with full functionality.

The server is setup to accept remote connections. It uses both windows and sql authentication. I have tried playing around with the TCP/IP port numbers. I've stopped the windows firewall in administrative tools/services on both the server and remote machine. Also added sql drivers under the ODBC Data Source Administrator for both the client & server.

I am pretty much out of ideas and the problem is really starting to bug me. I can't be the only person getting this bug/problem!?

Thanks in advance
Toby