Dotnetpanel Forums

Here is my setup.

1.Virtual server English
   msSQL  5 Express Instance with English Collation      

2.Virtual server [Local language]
msSQL  5 Express Instance with [Local language] Collation 

Creating new users works fine to each server

I need to move a user from 1 plan to the other.

So I change the plan without error, but when creating a database the database still gets created on previous plans mssql server

what should I do.

1. Create new user in preferred hosting plan,
2. Create a (bogus) database with same name as old database
3. through SQL Server Management Studio, delete the new database
4. detach old database from old instance and attach it to the new instance
5. give new sql user access to the old database.
6. copy website from old webusername to new username
7. change file setting for new user on all files

Maybe I should just move the database between instances? How do I take with me the Database User ? or how do I inform DNP that this other INstance of MSSQL should also be attached to this user and administered by him.

Or is there a simpler way to do this ?

This functionality will be in the next DNP 1.6.

For now in order to move database between services you should just change "ServiceID" column value in "ServiceItems" table for the appropriate row (using SQL Management Studio ).

thank you for the quick reply.

should I restart something..  ?  to get it to work ?

No, it does cache nothing.

Will 1.6 handle moving from one account to another? For example, I have my "managed" accounts sitting under hosting space beloning to serveradmin. These are accounts where the client does not need panel access. What if a few months down the road the client decides he wants more control over his site. Can I create a user for the client and move the hosting space over to the new user?

Yes, DNP 1.6 will allow moving the space between accounts.

Iano:

Will 1.6 handle moving from one account to another? For example, I have my "managed" accounts sitting under hosting space beloning to serveradmin. These are accounts where the client does not need panel access. What if a few months down the road the client decides he wants more control over his site. Can I create a user for the client and move the hosting space over to the new user?

Why don't you create a user account anyway for them (and not giving them the password)? I find that more convenient.

I've done that in the past, but I don't like re-using passwords, and having individual passwords for so many managed accounts that most likely won't ever need the panel becomes a hassle when I need to get in to make a change, which is frequent. Especially if I need to make a change quickly at a client-site, or a location where I do not have access to a password list.

As a follow-up to my own post here... a thought occured to me, if you made the seperate user/hosting space, could you log as serveradmin and then work-for that user to modify/set changes? This would satisfy seperated accounts and control via 1 master account, right?

Yes you can use this scenario to update user's settings or modify it's space. Also you are right regarding intention of this feature as well as it allows you to solve user's problems/issues without any additional movements such as emailing user passwords and etc.

Iano:

I've done that in the past, but I don't like re-using passwords, and having individual passwords for so many managed accounts that most likely won't ever need the panel becomes a hassle when I need to get in to make a change, which is frequent. Especially if I need to make a change quickly at a client-site, or a location where I do not have access to a password list.

I understand. I use this excellent application to manage passwords, works great: Password Safe

I tried this, but did not really get it to work.

Ended up creating a login user on the database instance 
and then a user on the specifik database with the created loginuser

This worked so I got the website running with database with right COLATION.  Later when  DNP 1.6 arrives I hope to fix problems with DNP admin for these users and databases.

Thanks for the help anyway.