recently i was stuck with a problem on remote desktop that the programs are hanged and i cannot click on anything, task manager is not accessible to end the processes. now how to open task manager in a remote desktop. if you can't do it then you haveto login to the remote machine locally or restart the machine manually. this is not a good option
so here is a command to open the task manager on remote desktop
CTRL+SHIFT+ESC - work same as right click taskbar and open task manager
CTRL+ALT+END - work same as CTRL+ALT+DEL
guess this post was useful!!
Wednesday, July 27, 2011
Wednesday, July 6, 2011
Login problem with MSDE
recently i came across a problem with MSDE (Microsft SQL Server Desktop engine) which gets installed mostly with third party software which do not require Standard SQL Server.
MSDE does not have its own user interface as it is primarily designed to run in the background.Users interact with MSDE through the program in which it is embedded. The only tool that is provided with MSDE is the osql utility. The executable file, osql.exe, for me is located in the C:\Program Files\Microsoft SQL Server\80\Tools\Binn\osql.exe
more information about osql.exe utility is available at
http://support.microsoft.com/kb/325003
http://support.microsoft.com/kb/325022
now the problem where i have to dig in is when my program which i downloaded was asking for a database username/password which i never entered during installation. i am able to see MSDE is started from the icon on the right hand side of the windows taskbar.but what is the username and password to connect to MSDE and how to connect to. once the program prompted for username as 'sa' .
to reset the password for user 'sa' since you have no idea about password, there is a way with osql utility.
go to start-run and type osql -U sa (here you are trying to connect to MSDE with username sa) and press enter. the command prompt for password .
do not type anything -----press enter (you came to know password is null for sa at this point)
to reset password type sp_password null 'yournewpassword','sa' ----press enter
type go -----press enter.you get a message Password chnaged
now you can use the sa/yournewpassword to connect from your application or from osql.exe
MSDE does not have its own user interface as it is primarily designed to run in the background.Users interact with MSDE through the program in which it is embedded. The only tool that is provided with MSDE is the osql utility. The executable file, osql.exe, for me is located in the C:\Program Files\Microsoft SQL Server\80\Tools\Binn\osql.exe
more information about osql.exe utility is available at
http://support.microsoft.com/kb/325003
http://support.microsoft.com/kb/325022
now the problem where i have to dig in is when my program which i downloaded was asking for a database username/password which i never entered during installation. i am able to see MSDE is started from the icon on the right hand side of the windows taskbar.but what is the username and password to connect to MSDE and how to connect to. once the program prompted for username as 'sa' .
to reset the password for user 'sa' since you have no idea about password, there is a way with osql utility.
go to start-run and type osql -U sa (here you are trying to connect to MSDE with username sa) and press enter. the command prompt for password .
do not type anything -----press enter (you came to know password is null for sa at this point)
to reset password type sp_password null 'yournewpassword','sa' ----press enter
type go -----press enter.you get a message Password chnaged
now you can use the sa/yournewpassword to connect from your application or from osql.exe
SQL Server Alias to connect to database
I have got a very good article which explains how to create SQL Server Alias to connect from client to server for named instance of SQL database
http://decipherinfosys.wordpress.com/2007/11/26/using-a-server-alias-to-connect-to-sql-server-instances/
-----------------------------------------------------------------------------
When connecting to SQL Server from your PC or from your application/web servers, you can choose to create aliases for connectivity. Before we start getting into the nitty-gritty details of aliases, let us see how you can set one up. You can use SQL Server Connection Manager in SQL Server 2005 to set it up and in case the tools are not installed, then you can also use cliconfg.exe (note – there is no i in confg) which is located under C:\Windows\System32 folder. If you use the connection manager, you will get a screen like this one:
You can then create a new alias as shown in the next image:
If you are using cliconfg.exe (the same is called in SQL Server 2000 when you use the SQL Server Client Network Utility), you will get a dialog box like the one shown below (showing the alias tab):
As you can see from above, the same alias that we had created using the SQL Server Connection Manager is automatically visible using the cliconfg.exe as well – that is because both of them read this entry from the registry. The place where these connection aliases can be found in the registry is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo
So, now that we have seen how to go about creating an alias and where it is stored, what exactly is the use of this feature? There are a couple of benefits of using aliases:
1) An alias can be used to define a user-defined name for connecting to a server -even if the IP address changes later on, there are no changes to the connection string – you just need to update the alias and the application will keep on working as before. You will not need to specify any instance name in the application connection string(s). And using an IP address directly in the alias definition can also save you some time in doing the DNS look-up.
2) You can make connection to SQL Server using different protocols: TCP/IP, Named Pipes etc. and specify specific parameters like the TCP port or the pipe name etc.
3) Aliases are also good for performance reasons. Since an alias has a pre-defined protocol, it can help you speed up the connection. Think about what happens when a connection is made to SQL Server from a client application. It has to try various protocols in the order that they are defined in your SQL Server Connection Manager (SQL 2005) or the SQL Server Client Network Utility (SQL 2000). If you already know which protocol and port your server is listening on, by configuring an alias you can by-pass the discovery phase that SQL Browser service goes through. In addition, if you know and have benchmarked your application using a specific protocol, you can standardize the alias technique across the board.
many thanks to decipherinfosys
---------------------------------------------------------------------------
After doing the above
From SQL Server Configuration Manager - SQL Native Client Configuration - Aliases , i can see my alias. when connecting using alias from SQL Server Management Studio didn't work . in my Configuration Manager there is another SQL Native Client Configuration (32bit). i had to create alias there in order for my client to connect.
Other references:-
http://blogs.msdn.com/b/sql_protocols/archive/2007/01/07/connection-alias.aspx
http://support.microsoft.com/kb/265808
http://decipherinfosys.wordpress.com/2007/11/26/using-a-server-alias-to-connect-to-sql-server-instances/
-----------------------------------------------------------------------------
When connecting to SQL Server from your PC or from your application/web servers, you can choose to create aliases for connectivity. Before we start getting into the nitty-gritty details of aliases, let us see how you can set one up. You can use SQL Server Connection Manager in SQL Server 2005 to set it up and in case the tools are not installed, then you can also use cliconfg.exe (note – there is no i in confg) which is located under C:\Windows\System32 folder. If you use the connection manager, you will get a screen like this one:
You can then create a new alias as shown in the next image:
If you are using cliconfg.exe (the same is called in SQL Server 2000 when you use the SQL Server Client Network Utility), you will get a dialog box like the one shown below (showing the alias tab):
As you can see from above, the same alias that we had created using the SQL Server Connection Manager is automatically visible using the cliconfg.exe as well – that is because both of them read this entry from the registry. The place where these connection aliases can be found in the registry is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo
So, now that we have seen how to go about creating an alias and where it is stored, what exactly is the use of this feature? There are a couple of benefits of using aliases:
1) An alias can be used to define a user-defined name for connecting to a server -even if the IP address changes later on, there are no changes to the connection string – you just need to update the alias and the application will keep on working as before. You will not need to specify any instance name in the application connection string(s). And using an IP address directly in the alias definition can also save you some time in doing the DNS look-up.
2) You can make connection to SQL Server using different protocols: TCP/IP, Named Pipes etc. and specify specific parameters like the TCP port or the pipe name etc.
3) Aliases are also good for performance reasons. Since an alias has a pre-defined protocol, it can help you speed up the connection. Think about what happens when a connection is made to SQL Server from a client application. It has to try various protocols in the order that they are defined in your SQL Server Connection Manager (SQL 2005) or the SQL Server Client Network Utility (SQL 2000). If you already know which protocol and port your server is listening on, by configuring an alias you can by-pass the discovery phase that SQL Browser service goes through. In addition, if you know and have benchmarked your application using a specific protocol, you can standardize the alias technique across the board.
many thanks to decipherinfosys
---------------------------------------------------------------------------
After doing the above
From SQL Server Configuration Manager - SQL Native Client Configuration - Aliases , i can see my alias. when connecting using alias from SQL Server Management Studio didn't work . in my Configuration Manager there is another SQL Native Client Configuration (32bit). i had to create alias there in order for my client to connect.
Other references:-
http://blogs.msdn.com/b/sql_protocols/archive/2007/01/07/connection-alias.aspx
http://support.microsoft.com/kb/265808
Subscribe to:
Posts (Atom)