ea8yscquj6
Uncategorized
Archived Posts from this Category
June 25, 2009
KPI creados en cubos de SQL Server muestran etiqueta ERROR en Performance Point
Posted by ecastrom under UncategorizedLeave a Comment
Si se crea un KPI con MDX en un cubo de SQL Server, cuando dicha información se despliega en Performance Point Server 2007, en lugar del valor del KPI se muestra una etiqueta que dice ERROR para las columnas de value y goal tal y como se muestra en la siguiente figura:
PAra solucionarlo primero es recomendable instalar el SP2 de Performance Point, más detalles en http://office.microsoft.com/download/afile.aspx?AssetID=AM103381121033, además se debe verificar que el Application Pool del SharePoint y el application pool del Monitoring Server están configurados adecuadamente. Para más detalles consultar http://technet.microsoft.com/en-us/library/bb905547.aspx
Saludos,
Eduardo Castro – Microsoft SQL Server
Costa Rica
Technorati Tags: SQL Server
LiveJournal Tags: SQL Server
del.icio.us Tags: SQL Server
June 24, 2009
SQL Server en Windows Server 2003 Enterprise 32bits con 32GB de RAM
Posted by ecastrom under UncategorizedLeave a Comment
Si desea configurar un servidor de SQL Server en 32 bits y desea que el sistema operativo reconozca 32GB de RAM, puede tomar en cuenta las siguientes consideraciones.
Si usted desea mantener el sistema operativo en 32 bits, entonces su opción es tener Windows 2003 Enterprise configurado con PAE. Consulte lo siguiente:
PAE Mode http://www.microsoft.com/whdc/system/platform/server/PAE/pae_os.mspx
PAE is the second method supported to access memory above 4 GB; this method has been widely implemented. PAE maps up to 64 GB of physical memory into a 32-bit (4 GB) virtual address space using either 4-KB or 2-MB pages. The Page directories and the page tables are extended to 8 byte formats, allowing the extension of the base addresses of page tables and page frames to 24 bits (from 20 bits). This is where the extra four bits are introduced to complete the 36-bit physical address.
Windows supports PAE with 4-KB pages. PAE also supports a mode where 2-MB pages are supported. Many of the UNIX operating systems rely on the 2 MB-page mode. The address translation is done without the use of page tables (the PDE supplies the page frame address directly).
Para configurar PAE en Windows 2003 puede consultar este artículo http://msdn.microsoft.com/en-us/library/ms791485.aspx
Este es un ejemplo de cómo configurar PAE en Windows 2003
Primer Boot.ini:
[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT=” Windows Server 2003, Enterprise” /fastdetect
Cambie el Boot.ini de la siguiente forma:
[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT=” Windows Server 2003, Enterprise” /fastdetect /PAE
Si lo desea realizar por medio del commando Bootcfg utilice lo siguiente:
bootcfg /raw "/pae" /A /ID 1
Saludos,
Eduardo Castro – Microsoft SQL Server
Costa Rica
Technorati Tags: SQL Server
LiveJournal Tags: SQL Server
del.icio.us Tags: SQL Server
June 22, 2009
La herramienta ForeFront Client Security y Windows Live One Care, pasaron las pruebas de antivirus, pueden ver todo el reporte en http://www.icsalabs.com/icsa/topic.php?tid=d3a8$95695e0b-40700fe6$8dd1-8fc093ea
Saludos,
Eduardo Castro – Microsoft SQL Server
Costa Rica
Technorati Tags: SQL Server
LiveJournal Tags: SQL Server
del.icio.us Tags: SQL Server
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
June 12, 2009
Utilizar SQL Server 2008 como repositorio para Team Foundation Server 2008
Posted by ecastrom under UncategorizedLeave a Comment
Para utilizar SQL 2008 con TFS 2008 debes primero aplicar el SP1 de TFS al instalador, primero tienes que bajar el SP1 desde la siguiente dirección
Download details- Visual Studio 2008 Team Foundation Server SP1
Después tienes que aplicar el SP1 al instalador de TFS 2008
- Copie el directorio del DVD del instalador al disco duro local
- Extraiga el a un directorio local con el comando TFS90sp1-KB949786.exe /extract:<Destino del Sp1>
- Ejecute el siguiente comando para aplicar el Sp1 al instalador msiexec /a <Directorio del AT>\vs_setup.msi /p <Directorio del SP1>\ TFS90sp1-KB949786.msp TARGETDIR=<Directorio del AT>
- Ahora ya tiene integrado el Sp1 con TFS 2008
Más información en
http://blogs.msdn.com/aabdou/archive/2008/05/13/team-foundation-server-sp1-beta-now-available.aspx
Saludos,
Eduardo Castro – Microsoft SQL Server
Costa Rica
Technorati Tags: SQL Server
LiveJournal Tags: SQL Server
del.icio.us Tags: SQL Server
June 5, 2009
Cómo determinar qué parche de SQL Server tengo instalado
Posted by ecastrom under UncategorizedLeave a Comment
Para saber la versión de SQL que está instalado en un servidor se puede utilizar el siguiente TSQL
select @@version
ó
select SERVERPROPERTY(‘productversion’), SERVERPROPERTY(‘productlevel’)
Esto da resultado por ejemplo:
10.0.2531.0 SP1
Pero si se instala el Cumulative Update 1 for SQL Server 2008 SP1, se tiene el siguiente resultado
10.0.2710.0 SP1
Entonces, cómo se sabe que el Cumulative Update está aplicado, si siempre dice SP1, para determinarlo puedes consultar la siguiente tabla, que es actualiza por Bill Graziano
http://www.sqlteam.com/article/sql-server-versions
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Saludos,
Eduardo Castro – Microsoft SQL Server
Costa Rica
Technorati Tags: SQL Server
LiveJournal Tags: SQL Server
del.icio.us Tags: SQL Server
June 4, 2009
Les adjunto un excelente artículo sobre PeerToPeer Replication en SQL Server 2005, fue escrito por
http://www.sql-server-performance.com/articles/dba/peer-to-peer_replication_p3.aspx
Using Peer-To-Peer Transactional Replication
Let’s consider a typical online e-commerce application. In order to avoid downtime and reduce the load on any single server, the database for this application is in more than one location. As it is an online e-commerce system, data needs to be changed (through inserts, updates, and deletes) at each location and all the data modifications need to be replicated to the other servers. For example, let’s assume there are databases at location A, B, and C.
To accomplish this in SQL Server 2000, we would use merge replication. Location A is the publisher, and B and C are the subscribers.
Figure 1: Merge replication.
The obvious drawback of this method is that it is a single point of failure configuration. If database B is down, the A to C replication link will continue to work. Users who are connected to both servers A and C will not see any adverse effect. However, if database A fails, B and C will be isolated from the system. Modifications will not be visible on other end.
SQL Server 2000 replication uses the publisher and subscriber hierarchy method. Successful operation of this configuration requires that the publisher be present at all times.
With the peer-to-peer replication topology in SQL Server 2005, each node acts as a publisher and as a subscriber. Replication recognizes when changes have occurred on a given node but only allows those changes to cycle through the nodes one at a time.
Figure 2: Peer-to-peer replication.
If one database is down (A, for example), the other databases (B and C) can still replicate. Whenever that database (A) comes back up, it can synchronize with the others (B and C) and get the changes that took place after it went down. This is possible because the databases (A, B, and C) all act as both publisher and subscriber.
How to Configure Peer-to-Peer Replication
Now that we have seen how peer-to-peer transactional replication works, let’s look at the configuration options.
First, we need to create a publication. In SQL Server 2005, we’ll use the New Publication Wizard.
Figure 3: New Publication Wizard.
As you can see (above), there are four publication types. To configure peer-to-peer transactional replication, we need to select Transactional publication.
After the publication is created, we need to change its properties. In the Publication Properties window (see below), set Allow peer-to-peer subscriptions to True. Please note that once we set this property to “true” we cannot revert to “false” until replication for the publication is dropped.
Figure 4: Publication Properties.
Now we’ll go back, right click on the publication, and run the peer-to-peer transactional replication wizard (see below).
With this wizard, we can add more SQL Servers or SQL Server instances to the peer network. You will not be able to add main publication databases or the previously selected database on which we ran the wizard.
Figure 5: Configure Peer-To-Peer Topology Wizard: selecting peers.
After configuring the peer network, we need to specify how we have initialized the databases for the other servers in the peer-to-peer network.
Figure 6: Configure Peer-To-Peer Topology Wizard: initializing the new peers.
The obvious way to initialize the new peer databases is to restore the backups (making sure they are not changed before setting up peer-to-peer replication). Otherwise, we can specify the backup file used. The SQL Server engine will synchronize the databases by comparing the publication database to the backup.
After we provide authentication for the Log Reader and the SQL Agent, the wizard will begin building the peer-to-peer topology. For our example, the process results in the creation of three publications and six subscriptions (see below). For each publication, the wizard will create a distribution database as well.
Figure 7: Configure Peer-To-Peer Topology Wizard: building the topology.
When we have completed the wizard, this is what we’ll see in SQL Server 2005 explorer:
Figure 8: The results of running the wizard.
Introducing Another Node
In today’s competitive environment, businesses expand widely and frequently. What if we need to add another node? In SQL Server 2005, using peer-to-peer replication, all we need to do is configure the new node as a publisher and a subscriber and attach it to the peer-to-peer network.
Conclusion
Peer-to-peer transactional replication has added a new dimension to SQL Server database replication, giving DBAs more flexibility. As a new feature, it isn’t yet widely used. But it will be. So check it out and see how your organization will benefit.
June 3, 2009
Todo el material sobre la charla Conozca Windows 7 puede descargarse de las siguiente direcciones:
http://comunidadwindows.org/files/folders/20090602/default.aspx
http://comunidadwindows.org/files/folders/20090602/entry403.aspx
http://comunidadwindows.org/files/folders/20090602/entry401.aspx
http://comunidadwindows.org/files/folders/20090602/entry402.aspx
Saludos,
Eduardo Castro – Microsoft SQL Server
Costa Rica
Technorati Tags: SQL Server
LiveJournal Tags: SQL Server
del.icio.us Tags: SQL Server
May 29, 2009
Ventajas de utilizar SQL 2008 como repositorio para MOSS 2007
Posted by ecastrom under UncategorizedLeave a Comment
En esta dirección http://comunidadwindows.org/files/folders/20090528/default.aspx pueden descargar el material de la presentación que se realizó el 28 de Mayo en la Universidad Latina de Costa Rica.
Saludos,
Eduardo Castro – Microsoft SQL Server
Costa Rica
Technorati Tags: SQL Server
LiveJournal Tags: SQL Server
del.icio.us Tags: SQL Server
May 14, 2009
El evento realizado por la comunidad en Multiplaza del Este fue todo un éxito, les adjuntamos algunas fotos del evento.
Eduardo Castro Blog 