Hi Technet community.

Today I have the privilege to start write in this blog (and a little reward the knowledge I've gained in Technet and MSDN). A few weeks ago it was the launch of SQL 2012 (http://www.microsoft.com/es-es/sqlserver/default.aspx) and I would like to make a brief reference to the current documentation that will allow us to explore some of its new BI features from SharePoint 2010 perspective.

A few weeks ago in Caracas-Venezuela, business partners and customers met at the Renaissance Hotel, to see first hand the value proposition offered by MIcrosoft to help companies and NGOs in the information management: analysis, reporting fast and simple ("Power View"), over huge data ("Parallel Datawarehouse"), in any location (On Premise, cloud or mix) with high availability ("Always On"). SQL 2012 is here with new features in order to strengthen their commitment with the transactional, spatial, multidimensional and critical information.

From the point of view of collaboration and Insights, this commitment translates into the ability to:
- Support SharePoint 2010 with Service Pack 1 (SP1) databases.
- Editing and publishing in SharePoint sites, reports in any format Office, using "Power View", a new feature of SQL Server Reporting Services for SharePoint.
- Strengthen the high availability databases, SharePoint 2010 (with SP1), by "Always On"

At this moment, SQL 2012 is not mentioned in software requirements documentation for SharePoint 2010, However, We have the following Guide for use SQL 2012 BI features in a SharePoint 2010 farm: http://technet.microsoft.com/en-us/library/hh231680(v=SQL.110).aspx This guide describes the possibility of deploying a farm SharePoint on SQL 2012, previously updated with Service Pack 1.

I hope this reference help you to promote the updating of your SharePoint 2010 farm and start to familiarize with the new features of BI in SQL 2012.

Hey there community,

Today we will learn how to create and use WMA or MP3 files as ringtones in our powerfull Windows Phone 7.

Since Microsoft released its Mobile operating system we wished to use our old ringtones from other companies or inclusive from our Windows Mobile phone, today is official we can use WMA and/or MP3 files as ringtones in our phone, but first we need to acomplish some pre-requisites:

Pre-requisites

• You can use only WMA or MP3 files
• Files should be less than 40 seconds
• Cannot be biger than 1 MB
• Cannot be protected with digital rights management (DRM)

Procedure:

• Using any software that allows you to trim the audio file create a file with the specs above
• Once the file was trimmed > Right click on it and go to properties
• On the Details tab go to the Genre field and choose or type Ringtone
• Click OK to save your changes
• Using Zune software load the file to your Collection
• Sync with your Windows phone 7
• You are done, go to Settings > Ringtones+Sounds
• Now you will find a new category named Custom with all your edited files

Enjoy, for more information about please review http://www.microsoft.com/windowsphone/en-us/howto/wp7/start/create-ringtones.aspx

Una vez más trayendo para ustedes algo que pueda ser de utilidad.

Desde que Microsoft liberó la nueva y más reciente versión de su sistema operativo para dispositivos móviles, todos deseamos que el hardware nos permitiera hacer lo que se hace con la competencia (iPhone) relacionado a la personalización de nuestro teléfono y contactos sobre todo. Cuando intentábamos usar un archivo wma como timbre simplemente no era posible.

Pero esto se acabo, ahora podemos usar archivos no protegidos como MP3 o WMA como timbres personalizados y poder usarlos en la configuración de nuestro teléfono, solo debemos cumplir ciertas condiciones y seguir los siguientes pasos:

Requisitos

• Solo se pueden usar formatos MP3 o WMA.
• Los archivos no deben contener mas de 40 segundos de audio.
• Los archivos no deben medir mas de 1 MB.
• Y no pueden estar protegidos con digital rights management (DRM).

Procedimiento

1. Utilizando cualquier software de edición de audio disponible en Internet deberás recortar el archivo para que cumpla con los requisitos anteriores
2. Una vez recortado > Clic derecho sobre el archivo y entras a las propiedades
3. En la pestaña de Detalles del archivo busca el atributo de Género y cambialo por Ringtone*
4. Ahora si por medio del software de Zune de tu Windows Phone vas a cargar el archivo a tu colección personal
5. Y finalmente sincronizar con tu Windows Phone
6. De esta manera ya puedes entrar a la configuración de tu teléfono y en las opciones de Timbres+Sonidos se habrá creado una categoria nueva al principio de sonidos personalizados en donde se encontrarán tus nuevos timbres.

Y listo a disfrutar, si tienes dudas o deseas información más detallada y oficial sobre este tema consulta: http://www.microsoft.com/windowsphone/en-us/howto/wp7/start/create-ringtones.aspx

Saludos comunidad,
 
Esta vez no vamos a atormentarlos con más temas técnicos, esta vez los estamos invitando a que asistan al Sexto Simposio Latinoamericano de SharePoint que se estará llevando a cabo en las oficinas de Microsoft en la Ciudad de México.
 
En esta clase de eventos ustedes podrán estar en contacto con los especialistas de la tecnología para poder preguntar lo que ustedes quieran, y este año habrá charlas con gente de Seguridad, Directorio Activo y Base de datos entre otras, solo tienen que registrarse y listo, un lugar estará reservado para ustedes.

Sólo tienes que hacer clic en: Sexto Simposio Latinoamericano de SharePoint para poder registrarte y reservar tu lugar.

Los esperamos en:

Av. Vasco de Quiroga 1700 PH

Col. Santa Fe, C.P. 01210, México D.F.

One of the clients that I worked for has a fully transactional core database. This database is accessed by a web application, which has an intermediate layer of application servers which connect directly to databases.

Here we can distinguish 3 different levels: web, application and database. The right programming practices lead us to keep most of the code within the database in order to obtain a better performance by decreasing the amount of information that goes over the network, in this case through the 3 levels explained before.

However a big number of old wrong programming practices maintain over 70% of source code routines within the application servers.

This did not become a real problem until the transaction level was increasing over time, as well as size and complexity of the database had reached.

One of the company policies is not to make code changes to databases production outside the "service packs" or application version upgrades, so you can assume that each "Service Pack" carries a large number of changes that are released into the Production environment at the same time.

Having clarified the environment, programming practices and deployments policy I can expose the case I had to face to at that time in this blog. Once, a day after a "Service Packs" release, Monday, customers began to contact customer service complaining that no one could enter to any of the applications, after the LOGIN screen appears, nothing happened until a time-out pop up in response.

Immediately I had to go through the database servers and I got the unpleasant surprise that in one server the CPU was 100% of usage; just wondering what change might come with the service pack that was causing this strange behavior!

After a while, some SQL traces were captured, and obtaining information from the DMV's and other tools, we conclude that the compiling level was much higher than historically shown before the version upgrade, but among so many changes that were pushed with the service pack we would have had the application down for too long in order to find the statement(s) responsible for such horror.

Two things were done in order to solve this issues, first, by analyzing the traces we conclude that we had to two indexes on a couple of tables that were desperately needed them, and second, by knowing that most of the executions were BATCH type, we came out with the possibility of changing the PARAMETERIZATION database option from SIMPLE to FORCED.

Command:

ALTER DATABASE <db_name> SET PARAMETERIZATION FORCED

What does this option do to a database?

Parameterizes all the values ​​which come with selects, updates, deletes and inserts that are BATCH type, individually, this way they won’t need to be recompiled each time they are executed. The execution plan is kept at memory level.

Obviously, this option does not apply to all statements that are within stored procedures as these are compiled by the database engine instead.

There are other situations where the parameterization is not applicable, you can see all the cases by entering the following link.

http://technet.microsoft.com/en-us/library/ms175037.aspx

By implementing these changes, the degree of recompiling decreased significantly and the CPU returned to normal levels between 20% and 30% of usage; this way all users could happily accessed the applications.

Conclusion

Before concluding this post I want to suggest recommending to developers to keep most of the code within the database engine as much as possible and if you came across with environments like the exposed here, I recommend changing the parameterization database option to "FOCED" before the disasters occurred.

“The opinions and views expressed in this blog are those of the author and do not necessarily state or reflect those of Microsoft”