Showing posts with label management. Show all posts
Showing posts with label management. Show all posts

Monday, March 12, 2012

logins and users

Hello,

How can I login in one databse from Sql Management Studio? Do I need one login for each user?

How does it work?

thanks,

Using the management studio you should be able to log on with a trusted connection. You will need to get the Database owner or admin to assign the permissions to each user that will need to connect... or you could create a network group in the AD and assign permissions to the user group in the databases that the users need to connect to.

|||yes, but how can I assign permission to this users. I mean trusted connection|||

Hi,

no you don′t need to. Trusted Connections / Windows Authentication is based on Windows security. Therefore you can also create a principal using a Windows group of your Windows domain or local server.


HTH, Jens K. Suessmeyer.


http://www.sqlserver2005.de

Wednesday, March 7, 2012

Login to SQL Server management studio

Hi,

I am facing a strange behavior during loging in to SQL server mangement studio.

Whenever I install SQL server express, various protocols like Named Pipe and TCP/IP and SQL browser are disabled by default. But still I am able to log in to SQL Server throguh Management studio.

But when I try to log in to SQL server throguh one of my applications, it allows me to log in to it only for one time. From next time onwards, I am not able to log in to SQL server neither through my application nor through Management studio.

I connect to SQL server using "machine name"\"Instance name". Machine name is the name of machine on my office LAN.

PS: Once this problem occurs, I can log in to SQL server if I use "localhost" instead of "machine name".

Any suggestions would be tremendously helpful.

Regards

-Orion

SQL Express supports connecting through Shared Memory, which is a local connectivity protocol that is used by the SQL Native Client. This is how you're connecting with Management Studio. I can't tell you what the problem is with your application as you have not provided an error message or error log.

Mike

|||

Hi Mike,

Thanks for the reply.

>>
I can't tell you what the problem is with your application as you have not provided an error message or error log
>>

Following are the details of the exception thrown by SQL server.

{"State:08001,Native:6,Origin:[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] State:01000,Native:11004,Origin:[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]"}

The problem is when it allows my application to connect to SQL Server only once. After this, I need to enable TCP/IP protocol for any subsequent connection through my application or SQL Server management studio.

Regards,
Orion

|||

Hi Orion,

Could you define what you mean by "subsequent connections through my application"? Are you talking about a single application creating multiple threads connecting to SQL Server? Are these different copies of the same application being run by other users on other computers? What is the connection string you're using from your application?

I don't recognize that error, is there any more descirptive text?

Mike

Monday, February 20, 2012

Login not working anymore

I am running an Express 2005 server, using the Management software included. I was attempting to view server settings when it locked me out. I could not access the properties of the server, and after that, anything. I tried logging out, but it would not let me log back in. It said that the server may not allow remote connections, but this was the same login that I had been using previously with Windows authentication without a problem.

So, now I'm locked out of my database with no way to access anything. Does anyone know how I can get around this or make the login work again?
Hi,

is the service started properly ? Perhaps you switch the RemoteConnections Setting for some reason ? http://www.sqlserver2005.de/SharedFiles/RemoteConnection.jpg

Or you have a different port than the default one associated with the Service and the SQL Browser which does the dynamic directing doesnt work anymore ? In this case start the SQL Browser or use the direct syntax to contact your SQL Server : machineName\InstanceName,Portnumber . There could be various issues why you can′t connect anymore, try to find out if something changed on the system first by looking in the event logs.

One possible reason *could* be that you assigned the service a specific account and changed the password for that account, but this could be clearly seen in the event log.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de