select serverproperty (‘MachineName’) as Servername
SELECT SERVERPROPERTY(‘ServerName’) AS ServerName
Select SERVERPROPERTY(‘ComputerNamePhysicalNetBIOS’) as PhysicalName
SELECT @@SERVERNAME AS ServerNameGlobalVar
Author Archives: admin
Buzzom.com
16 de Setembro de 2009 – 0:33
Localize e siga pessoas das suas áreas de interesse com Buzzom
Building Scalable Databases: Denormalization, the NoSQL Movement and Digg
15 de Setembro de 2009 – 11:52
Database normalization is a technique for designing relational database schemas that ensures that the data is optimal for ad-hoc querying and that modifications such as deletion or insertion of data does not lead to data inconsistency.
Database denormalization is the process of optimizing your database for reads by creating redundant data. A consequence of denormalization is that insertions or deletions could cause data inconsistency if not uniformly applied to all redundant copies of the data within the database.
Why Denormalize Your Database?
Today, lots of Web applications have “social” features. A consequence of this is that whenever I look at content or a user in that service, there is always additional content from other users that also needs to be pulled in to page. When you visit the typical profile on a social network like Facebook or MySpace, data for all the people that are friends with that user needs to be pulled in.
Or when you visit a shared bookmark on del.icio.us you need data for all the users who have tagged and bookmarked that URL as well. Performing a query across the entire user base for “all the users who are friends with Robert Scoble” or “all the users who have bookmarked this blog link” is expensive even with caching. It is orders of magnitude faster to return the data if it is precalculated and all written to the same place.
This is optimizes your reads at the cost of incurring more writes to the system. It also means that you’ll end up with redundant data because there will be multiple copies of some amount of user data as we try to ensure the locality of data.
Enviando artigo para blog através do Word 2007
11 de Setembro de 2009 – 12:46
Interessante esta funcionalidade do Microsoft Word que permite, assim como criar um novo documento, criar um novo artigo para o Blog.
Suporta por defeito alguns tipos de blog (WordPress, Typepad, Bloguista…), curiosamente por defeito não aparece um dos maiores serviços de blog, o BlogSpot, mas parece ser possível adicioná-lo á lista.
Ao usar pela primeira vez pede o tipo de blog, o URL, login e password de acesso ao BackOffice, depois +e começar a escrever e publicar. Simples e prático.
Permite mais algumas funcuinalidades, tipo: Publicar como rascunho, inserir Categoria, mas não me está a mostrar as existentes…
Resta fazer mais uns testes com upload de imagens por exemplo..
Testing….. J
ASP.Net Recipe
10 de Setembro de 2009 – 14:31
Next time you invite your buddies to a cookout, how about making something special? May I suggest a roast recipe?
Ingredients
* 1 cup sliced CSS
* 1 teaspoon JavaScript
* 1/2 cup XHTML powder
Instructions
1. Grind tables.
2. Place ASP.NET in a roaster, stab with knife to allow view state to escape.
3. Fill layout with semantic markup.
4. Blend CSS with well-beaten JavaScript and pour over the top.
5. Continue making layers until all the ingredients are used.
6. Serve with modern browsers.
Enjoy!
by http://aspnetresources.com/blog/aspnet_roast_recipe.aspx
SQL Server 2008 Editions: Enterprise and Standard
8 de Setembro de 2009 – 16:28
Enterprise
SQL Server 2008 Enterprise is a comprehensive data platform that meets the high demands of enterprise online transaction processing and data warehousing applications.
Standard
SQL Server 2008 Standard is a complete data management and business intelligence platform providing best-in-class ease of use and manageability for running departmental applications.
 |
KEY: |
|
|
|
= Full
= Partial/Limited
= Not Available|
SQL Server 2008 Enterprise Edition |
SQL Server 2008 Standard Edition |
|
|---|---|---|
|
Number of CPUs |
OS Maximum |
4 |
|
Scalability & Performance |
 |
 |
|
High Availability (Always On) |
|
|
|
Enterprise Security |
|
|
|
Data Warehousing |
|
 |
|
Business Intelligence |
|
 |
|
Enterprise Manageability |
|
|
Review the detailed feature comparison.
Source link: http://www.microsoft.com/sqlserver/2008/en/us/compare-std-ent.aspx
Social Networking on Intranets
2 de Setembro de 2009 – 12:27
Summary:
Community features are spreading from “Web 2.0” to “Enterprise 2.0.” Research across 14 companies found that many are making productive use of social intranet features.
Through several rounds of research on intranet portals, we’ve repeatedly reached the same conclusions:
- When Intranet information architectures are structured according to the org chart, employees have a hard time finding their way around. It’s better to structure information according to how people use it, rather than what department owns it.
- Role-based personalization lets portals bring information to users in centralized views, rather than forcing users to navigate an immense information space to find individual (and dispersed) locations.
Social features on intranets take these two trends a step further, creating a “person-structured” intranet IA focused around the individual users as well as other people on the intranet.
by Jakob Nielsen’s Alertbox, August 3, 2009: http://www.useit.com/alertbox/social-intranet-features.html read moreProgrammer Stereotype
2 de Setembro de 2009 – 12:12
Cowboy Coder
Cowboy Coders are programmers who write code according to their own rules. They may be very good at writing code, but it doesn’t generally follow the standards, processes, policies, or anything else derived from the group. Cowboy Coders work well alone, or in the old-style CaveProgrammer environment, but they rarely, if ever, work well in a team. Often times, they are a burr in the saddle that keeps the team from getting positive work done.
The above elicits mixed emotions. I have often been a CowboyCoder; in some circumstances I didn’t have a choice (I was the *only* coder on the project); in others, it was inherent in the context : no team rules, standards, or processes, and a division of labor which put senior developers in charge of different projects, with little opportunity to elaborate such standards as a team. I didn’t like having the pattern thrust upon me, and I’m pretty sure I’ll do much better in a team.
CowboyCoders are identified more by their attitude than by their circumstances. CowboyCoders prefer — nay, insist! — to avoid standards, processes, and policies, and hate working with others.
Some CowboyCoders work in packs as GuerillaCoders, self-supporting their behaviors. See RamboCoder.
The Cowboy Way:
read more
Microsoft Software Licensing and Protection Services
1 de Setembro de 2009 – 15:55
Microsoft Software Licensing and Protection Services (SLP Services) is a development platform that offers developers a license activation and management framework to build protected applications written in managed and native code.
Adding a product, designing a feature set, and issuing a perpetual license in the Microsoft SLP Online Service are among the first steps in protecting intellectual property and enforcing licensing policies. Microsoft Software Licensing and Protection (SLP) Services offer software vendors a variety of licensing models with which to protect their applications.
http://msdn.microsoft.com/en-us/slps
Home