SQLPedia

martes, 13 de abril de 2010

Evento Cloud Computing Bases de Datos y Aplicaciones

El 10 de abril realizamos el Evento Cloud Computing y Aplicaciones, en esta charla se trataron temas sobre SQL Server Azure y Windows Azure, la presentación la puede descargar desde la siguiente dirección http://comunidadwindows.org/files/folders/20100410/default.aspx

View Full Album

Error Could not load package "XXXXX" because of error 0xC00160AA. Description: Connect to SSIS Service on machine "XXXXX" failed: The RPC server is unavailableConnect to SSIS Service on machine “XXXXX" failed: The RPC server is unavailable

If you have two servers one running SQL Server Agent (SERVER A) and the other Integration Services (SERVER B) and you want to be able to run the SSIS packages on SERVER B from the Agent on SERVER A, you need to properly configure the firewall on SERVER B, if you don’t do it, you will run into the following error:

Error Could not load package "XXXXX" because of error 0xC00160AA. Description: Connect to SSIS Service on machine "XXXXX" failed: The RPC server is unavailableConnect to SSIS Service on machine “XXXXX" failed: The RPC server is unavailable

To configure the firewall follow these steps:

Allow the C:\Program Files\Microsoft SQL Server\100\DTS\Binn\MsDtsSrvr.exe to go though the firewall, you can do it with an exeption in Windows 2003 or an Access Rule in Windows 2008.
Allow the traffic for TCP port 135

**********************************************************************************

Si tienes que ejecutar paquetes que están en un servidor remoto tienes que asegurarte que el firewall del servidor remoto está correctamente configurado, para eso debes permitir trafico por el puerto TCP 135 y crear una excepción para el archivo C:\Program Files\Microsoft SQL Server\100\DTS\Binn\MsDtsSrvr.exe

Saludos,

Ing. Eduardo Castro Martínez, PhD – Microsoft SQL Server MVP

http://mswindowscr.org

http://comunidadwindows.org

Costa Rica

Technorati Tags: SQL Server

LiveJournal Tags: SQL Server

del.icio.us Tags: SQL Server

http://ecastrom.blogspot.com

http://ecastrom.wordpress.com

http://ecastrom.spaces.live.com

http://universosql.blogspot.com

http://todosobresql.blogspot.com

http://todosobresqlserver.wordpress.com

http://mswindowscr.org/blogs/sql/default.aspx

http://citicr.org/blogs/noticias/default.aspx

http://sqlserverpedia.blogspot.com/

Error SocketException getaddrinfo no data of the requested type was found when creating a new Report Server Database

When you are trying to create a new database for your Report Server through the Reporting Services Configuration Manager and the database server is not local but a remote server and in the remote server you have changed the default port and the SQL Browser is not running, you will run in the following error SocketException getaddrinfo no data of the requested type was found , and the configuration tool will show the following error in the Generating rights scripts section.

When you click on the Error link, you will saw the following detail:

System.Net.Sockets.SocketException: No such host is known
   at System.Net.Dns.GetAddrInfo(String name)
   at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
   at System.Net.Dns.GetHostEntry(String hostNameOrAddress)
   at ReportServicesConfigUI.RSDatabase.IsLocalDbServer(String dbServer)
   at ReportServicesConfigUI.RSDatabase.GrantRSConnectionRights()
   at ReportServicesConfigUI.RSDatabase.CreateNewDatabase()

This happens because the configuration tools is trying to resolve the server name you have specified, for example if your remote server is called DBServerA and you have created an alias whose name is DB you will run into this error. To solve it, you need to create an alias with the same name of the remote server and you have to specify the remote port, as shown in the following screenshot:

If you are running in a 64 bits machines you will also have to create the alias for the 32 bits clients, I had to create the alias twice for this in order to work.

Regards,

Ing. Eduardo Castro Martínez, PhD – Microsoft SQL Server MVP

http://mswindowscr.org

http://comunidadwindows.org

Costa Rica

Technorati Tags: SQL Server

LiveJournal Tags: SQL Server

del.icio.us Tags: SQL Server

http://ecastrom.blogspot.com

http://ecastrom.wordpress.com

http://ecastrom.spaces.live.com

http://universosql.blogspot.com

http://todosobresql.blogspot.com

http://todosobresqlserver.wordpress.com

http://mswindowscr.org/blogs/sql/default.aspx

http://citicr.org/blogs/noticias/default.aspx

http://sqlserverpedia.blogspot.com/

lunes, 5 de abril de 2010

Need to wait to execute a TSQL in SQL Server?

If you are running tests on a SQL Server database using scripts, usually you may have to create a batch of TSQL and they must be executed in a certain order and in a certain time, to achive this you can use the WAITFOR DELAY statament, it allows your script to wait N seconds before being executed. In the following script we wait 30 seconds before executing the getdate command.

WAITFOR DELAY '00:00:30' ---- 30 Seconds Delay SELECT GETDATE() CurrentTime

Regards,

Ing. Eduardo Castro Martínez, PhD – Microsoft SQL Server MVP

http://mswindowscr.org

http://comunidadwindows.org

Costa Rica

Technorati Tags: SQL Server

LiveJournal Tags: SQL Server

del.icio.us Tags: SQL Server

http://ecastrom.blogspot.com

http://ecastrom.wordpress.com

http://ecastrom.spaces.live.com

http://universosql.blogspot.com

http://todosobresql.blogspot.com

http://todosobresqlserver.wordpress.com

http://mswindowscr.org/blogs/sql/default.aspx

http://citicr.org/blogs/noticias/default.aspx

http://sqlserverpedia.blogspot.com/

SQL Distributed Transaction fired by a COM+ not working

If you have some COM+ object that connects to SQL Server and opens a transaction, sometimes it stops working at all, you may be facing a COM+ Corrupted Database, to “repair” this database you must follow the following steps:

Find the file %WinDir%\System32\Clbcatq.dll and rename it to ~Clbcatq.dll
Reboot the computer in Recovery Mode.
Open the Registry and delete the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3.
Find in the %WinDir% directory and look for a subdirectory named Registration. Delete Registration folder.
Reboot the machine normally.
Open Control Panel | Add/Remove Programs | Add/Remove Windows Components.
Click Next to reinstall COM+.
Now your transactions should work

Regards,

Ing. Eduardo Castro Martínez, PhD – Microsoft SQL Server MVP

http://mswindowscr.org

http://comunidadwindows.org

Costa Rica

Technorati Tags: SQL Server

LiveJournal Tags: SQL Server

del.icio.us Tags: SQL Server

http://ecastrom.blogspot.com

http://ecastrom.wordpress.com

http://ecastrom.spaces.live.com

http://universosql.blogspot.com

http://todosobresql.blogspot.com

http://todosobresqlserver.wordpress.com

http://mswindowscr.org/blogs/sql/default.aspx

http://citicr.org/blogs/noticias/default.aspx

http://sqlserverpedia.blogspot.com/

Note: Cross posted from Eduardo Castro.

Permalink

martes, 30 de marzo de 2010

SQL Server ejecutando en HyperV despliega el siguiente error Virtual machine could not be started because the hypervisor is not running. Boot Configuration Data.

Si por alguna razón usted edita el Boot Configuration Data debe ejecutar el siguiente comando después de la edición:

bcdedit /set hypervisorlaunchtype auto

Si no lo hace cuando intente levantar la máquina virtual de SQL SERVER se desplegará el siguiente error “virtual machine could not be started because the hypervisor is not running”.

Saludos,

Ing. Eduardo Castro Martínez, PhD – Microsoft SQL Server MVP

http://mswindowscr.org

http://comunidadwindows.org

Costa Rica

Technorati Tags: SQL Server

LiveJournal Tags: SQL Server

del.icio.us Tags: SQL Server

http://ecastrom.blogspot.com

http://ecastrom.wordpress.com

http://ecastrom.spaces.live.com

http://universosql.blogspot.com

http://todosobresql.blogspot.com

http://todosobresqlserver.wordpress.com

http://mswindowscr.org/blogs/sql/default.aspx

http://citicr.org/blogs/noticias/default.aspx

http://sqlserverpedia.blogspot.com/

SQL Server running in HyperV displays error: Virtual machine could not be started because the hypervisor is not running. Boot Configuration Data.

If for any reason you edit the Boot Configuration Data be sure to run the following command after the edit:

bcdedit /set hypervisorlaunchtype auto

If you don’t do it you will run into an error saying that your SQL Server virtual machine could not be started because the hypervisor is not running and then you will be presented with three possible errors, usually the main cause is where changes have been made to the Boot Configuration Data or BCD. This can also happen if you had sysprep'ed images with Hyper-V.

Regards,

Ing. Eduardo Castro Martínez, PhD – Microsoft SQL Server MVP

http://mswindowscr.org

http://comunidadwindows.org

Costa Rica

Technorati Tags: SQL Server

LiveJournal Tags: SQL Server

del.icio.us Tags: SQL Server

http://ecastrom.blogspot.com

http://ecastrom.wordpress.com

http://ecastrom.spaces.live.com

http://universosql.blogspot.com