Archive
free SQL Training videos on plural sight
Hi all …. get a free 24 hours training for any video on plural sight ..
(better to view first only the highly rated Videos under SQL or whatever you like )
1> like on twitter
2> submit your twitter handle
3> use the link and access code you receive on your twitter account to access all vidoes
OR
Powershell Alias
Power shell is object oriented .. all commands or cmdlets .. return or take objects as parameters ..
to make switch from unix or *NIX easier .. to powershell most of the command have corresponding aliases in PS ..
example :
1> CLS – to clear screen
2> DIR — to give list files and folders at current path/directory
3> to get all alias type at the PS prompt
get-ALIAS or
get-alias cmdlet_name (to get alias for particular cmdlet)
4> to create a temporary alias of yourself
EG: set-ALIAS np notepad
once you have created alias .. if you just type np .. at the PS prompt .. it will open up Notepad
Scripts to monitor SQL Server Memory usage in Buffer Pool, Plan Cache and identify Query Memory grants & waits by session
Linked server works locally but not remotely
i was not able to use linked server remotely (from my desktop) or from SQL agent jobs on an instance INST1
English: M in blue square (similar to seen on ) (Photo credit: Wikipedia)
linked server point to INST2 .. i was able to view objects in linked server tab (in SSMS) and runs select from the server locally (INST1)
even below query worked fine
begin distributed tran
select * from [remoteservername].master.sys.sysprocesses
commit tran
but i was not able to view or make jobs (INST1) run fine … getting below error
Named Pipes Provider: Could not open a connection to SQL Server [5].
OLE DB provider “SQLNCLI10” for linked server “[remoteservername” returned message “Login timeout expired”.
OLE DB provider “SQLNCLI10” for linked server “[remoteservername” returned message “A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.”. (Microsoft SQL Server, Error: 5)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.00.5500&EvtSrc=MSSQLServer&EvtID=5&LinkId=20476
SOLUTION
after checking everything .. from firewall to bouncing SQL browser service on destination server .. we figured out below ..
an alias using named pipes was created to the INST2 ..on INST1 as soon as that alias was dropped .. all jobs ran fine and linked server TAB
worked fine remotely fro
m SSMS .. it seems the alias was the default configuration used by linked server .. for remote requests VIA SSMS and
SQL agent jobs …
**** so just save the alias configurations and deleting it .. and rerun the jobs and remote queries *****
try the above solution .. if nothing works for you
SQL DBA learning curve 