Category Archives: Microsoft

SQL Server

SQL Server & MSDE

While this article is geared mainly toward MSDE users, all of the tools described within can, as far as we know, work against regular editions of SQL Server. Some can even work against Access, Oracle, and other database platforms.

MSDE does not include graphical management tools like Enterprise Manager, Query Analyzer, and Profiler. So, you may have a hard time even verifying that the MSDE install went fine, never mind creating databases, objects and users. There are several ways to manage MSDE installations.

Some of the tools listed below are free, others have a range of pricetags. We will try to update the links to indicate which ones are free.

(Please let us know if we missed your favorite product, or if you have a favorable or non-favorable review of any of the tools listed below.)

read more »

SQL Server

SQL Server format dates and times

DECLARE @now DATETIME SET @now = GETDATE() PRINT dbo.FormatDateTime(@now, ‘LONGDATE’) PRINT dbo.FormatDateTime(@now, ‘LONGDATEANDTIME’) PRINT dbo.FormatDateTime(@now, ‘SHORTDATE’) PRINT dbo.FormatDateTime(@now, ‘SHORTDATEANDTIME’) PRINT dbo.FormatDateTime(@now, ‘UNIXTIMESTAMP’) PRINT dbo.FormatDateTime(@now, ‘YYYYMMDD’) PRINT dbo.FormatDateTime(@now, ‘YYYY-MM-DD’) PRINT dbo.FormatDateTime(@now, ‘YYMMDD’) PRINT dbo.FormatDateTime(@now, ‘YY-MM-DD’) PRINT dbo.FormatDateTime(@now, ‘MMDDYY’) PRINT dbo.FormatDateTime(@now, ‘MM-DD-YY’) PRINT dbo.FormatDateTime(@now, ‘MM/DD/YY’) PRINT dbo.FormatDateTime(@now, ‘MM/DD/YYYY’) PRINT dbo.FormatDateTime(@now, ‘DDMMYY’) PRINT dbo.FormatDateTime(@now, ‘DD-MM-YY’) PRINT dbo.FormatDateTime(@now, ‘DD/MM/YY’) PRINT dbo.FormatDateTime(@now, ‘DD/MM/YYYY’) PRINT dbo.FormatDateTime(@now, ‘HH:MM:SS 24’) PRINT dbo.FormatDateTime(@now, ‘HH:MM 24’) PRINT dbo.FormatDateTime(@now, ‘HH:MM:SS 12’) PRINT dbo.FormatDateTime(@now, ‘HH:MM 12’) PRINT dbo.FormatDateTime(@now, ‘goofy’)

Artigo Completo Aqui

SQL Server

CAST and CONVERT

Explicitly converts an expression of one data type to another. CAST and CONVERT provide similar functionality.

Syntax

Using CAST:

CAST ( expression AS data_type )

Using CONVERT:

CONVERT ( data_type [ ( length ) ] , expression [ , style ] )

SqlCAST.gif

Microsoft

Windows Vista Capable and Premium Ready PCs

Choose a Windows Vista Capable or Premium Ready PC for the Windows Vista edition that’s right for you.

Are you looking to buy a Windows XP-based computer today but want to make sure that it can run Windows Vista? There’s no need to wait. When you buy a new PC that carries the Windows Vista Capable or Premium Ready PC designation, you’ll be able to upgrade to one of the editions of Windows Vista while taking advantage of all the opportunities offered by Windows XP today.
What is a Windows Vista Capable PC?

A new PC that carries the Windows Vista Capable PC logo can run Windows Vista. All editions of Windows Vista will deliver core experiences such as innovations in organizing and finding information, security, and reliability. All Windows Vista Capable PCs will run these core experiences at a minimum. Some features available in the premium editions of Windows Vista—like the new Windows Aero user experience—may require advanced or additional hardware.
read more »

SQL Server

SQL SERVER 2000 – Requisitos

Principais requisitos minimos:

SISTEMA OPERATIVO
SQL Server 2000 Enterprise Edition and Standard Edition can run on the following operating systems:
  • Windows Server 2003 R2
  • Windows Server 2003, Standard Edition1
  • Windows Server 2003, Enterprise Edition2
  • Windows Server 2003, Datacenter Edition3
  • Windows® 2000 Server
  • Windows 2000 Advanced Server
  • Windows 2000 Datacenter Server
SQL Server 2000 Evaluation Edition and Developer Edition and Workgroup Edition can run on the following operating systems:
  • Operating systems listed above for Enterprise and Standard Editions
  • Windows XP Professional
  • Windows XP Home Edition
  • Windows 2000 Professional
SQL Server 2000 Personal Edition4 and SQL Server 2000 Desktop Engine (MSDE) can run on the following operating systems:
  • Operating systems listed above for Enterprise, Standard, Evaluation, and Developer Editions
  • Windows Server 2003, Web Edition5 (MSDE only)
  • Windows 98
  • Windows Millennium Edition (Windows Me)
MEMORIA
  • Enterprise Edition: 64 megabytes (MB) of RAM; 128 MB recommended
  • Standard Edition: 64 MB
  • Workgroup Edition: 64 MB
  • Evaluation Edition: 64 MB; 128 MB recommended
  • Developer Edition: 64 MB
  • Personal Edition: 128 MB for Windows XP; 64 MB for Windows 2000; 32 MB for other operating systems
  • MSDE: 128 MB for Windows XP; 64 MB for Windows 2000; 32 MB for other operating systems
DISCO
  • Enterprise, Standard, Workgroup, Evaluation, Developer, and Personal Editions require:
  • 95–270 MB of available hard disk space for the server; 250 MB for a typical installation.
  • 50 MB of available hard disk space for a minimum installation of Analysis Services; 130 MB for a typical installation.
  • 80 MB of available hard disk space for English Query.
  • MSDE requires 44 MB of available hard disk space.

Microsoft Scripting

Windows PowerShell

Windows PowerShell, previously Microsoft Shell or MSH (codenamed Monad) is an extensible command line interface (CLI) shell and scripting language product being developed by Microsoft. The product is based on object-oriented programming and the Microsoft .NET framework.

Windows PowerShell 1.0 is available for download from the Microsoft web site (https://docs.microsoft.com/en-us/powershell/).

Microsoft originally intended to launch PowerShell along with Windows Vista, but later defined a separate release schedule for PowerShell. Windows PowerShell is the foundation of the administrative experience for Microsoft Exchange Server 2007 where everything is done via command line interfaces and the administrative GUI is layered on top of those commands.

PowerShell requires version 2.0 of the .NET Framework, and is supported on Windows XP, Windows Server 2003, Windows Vista, and Windows Server “Longhorn”, and is available in x86, x64 and Itanium editions.

—-

Microsoft Windows PowerShell command line shell and scripting language helps IT Professionals achieve greater productivity. Using a new admin-focused scripting language, more than 130 standard command line tools, and consistent syntax and utilities, Windows PowerShell allows IT Professionals to more easily control system administration and accelerate automation.

Windows PowerShell is easy to adopt, learn, and use, because it works with your existing IT infrastructure and existing script investments, and because it runs on Windows XP, Windows Vista, Windows Server 2003 and Windows Server . Exchange Server 2007, System Center Operations Manager 2007, System Center Data Protection Manager V2, and System Center Virtual Machine Manager leverage Windows PowerShell to improve efficiency and productivity.


Some References:

http://www.computerperformance.co.uk/powershell/index.htm

https://www.comparitech.com/net-admin/powershell-cheat-sheet/

 

 

 

 

Microsoft

Windows Workflow Foundation

Windows Workflow Foundation (WF) is a Microsoft technology for defining, executing, and managing workflows. This technology is part of .NET Framework 3.0 and will be available natively in the Windows Vista operating system, and has been backported to the Windows XP and Windows 2003 Server operating systems. The .NET Framework 3.0 “workflow runtime” provides common facilities for running and managing the workflows and can be hosted in any CLR app domain.

A new XML-based language XAML is commonly used for declaring the structure of a workflow. However, the workflow may also be expressed in code using any .NET-targeted language (like C#).

Workflows comprise ‘activities
‘. Developers can write their own domain-specific activities and then use them in workflows. The .NET Framework 3.0/Windows Workflow Foundation also provides a set of general-purpose ‘activities’ that cover several control flow constructs.

Windows Workflow Foundation also includes Visual Studio 2005 extensions. These extensions contain a visual workflow designer which allows users to design workflows, a visual debugger which enables the users to debug the workflow designed and project system which enables the user to compile their workflows inside Visual Studio 2005.

http://wf.netfx3.com/Â

SharePoint Server 2007 ScreenCasts

Sharepoint Services

Building ASP.NET Web Parts for Windows SharePoint Services 3.0
Create an ASP.NET Web Part project from scratch and get it up and running within a Windows SharePoint Services 3.0 site.

Creating a Custom Page Layout with SharePoint Server 2007
Create a custom page layout using the Web Content Management features of SharePoint Server 2007.

Creating and Testing Features with Windows SharePoint Services 3.0
Use Visual Studio to create a custom feature and an associated assembly DLL.

Creating and Using Content Types in Windows SharePoint Services 3.0
Create user-defined content types using inheritance, and then configure a document library to use these content types.

Creating and Using Event Handlers in Windows SharePoint Services 3.0
Create a list item receiver class to handle both synchronous events as well as asynchronous events.

Creating and Using Site Columns in Windows SharePoint Services 3.0
Create and reuse site columns across the sites within a site collection.

Creating Custom Document Information Panels
Discover the integration that exists between Document Information Panels and content types in Windows SharePoint Services 3.0.

Creating Custom Workflows with the SharePoint Designer 2007
Build a custom workflow using the SharePoint Designer wizard.

Creating Windows SharePoint Services Sites with Support for Wikis and Blogs
Leverage the new built-in features for creating sites with blogs and wikis.

Customizing a Windows SharePoint Services 3.0 site with the SharePoint Designer 2007
Understand the difference between page templates and page instances, and then learn how to customize your pages.

Getting Up and Running with Excel Services
Configure Excel Services so that you can publish an Excel spreadsheet to a Windows SharePoint Services 3.0 site.

read more »

IIS

How to Create Multiple Websites with one IP address

There are three, count ‘em three ways to create multiple websites on IIS 4 and 5. First way is to use an unique IP for each site. This is ideal but if you haven’t looked around lately, IP addresses can be sorta scarce (that is of course unless your Harley Davidson or Apple both of whom own a Class A address).

The second way allows you to create multiple IP’s on one address by designating a non-standard TCP port number for the designated web to use. This is the way the Administrative website winds up on the same installation as the default website and both can be accessed. However, you have to designate the unique port number in the URL when accessing it. So instead of www.myvirtualsite.com, it becomes www.myvirtualsite.com:6160 or some other number. You can include the port number in a url so it’s really not problem for web pages to reference port designated web sites. The problem is that you can’s specify a port in a DNS server so if users want to lookup your website, they won’t be able to get to it.

Thus we come the next best thing, host headers.

The good news is this is relatively easy to do in IIS and it works very well. There is virtually no performance penalty and it works with most every browser in use today (browsers must be HTTP 1.1 compliant). You can use DNS to point to the website so internet users can find your host header designate site with no problems. You do have to pay attention to the details however or it won’t work. The biggest downside is that you compromised using SSL. (Microsoft KB Article: Q187504 – IIS: HTTP 1.1 Host Headers Not Supported When Using SSL)

read more »

SQL Server

Como saber que versão do SQL Server estou a correr?

2012


SELECT 'SQL Server '
+ CAST(SERVERPROPERTY('productversion') AS VARCHAR)
+ '-'
+ CAST(SERVERPROPERTY('productlevel') AS VARCHAR)
+ ' ('
+ CAST(SERVERPROPERTY('edition') AS VARCHAR)
+ ')'

SQL Server 7.0, 2000, and 2005, running the following will extract ONLY the version information.

SELECT LTRIM(RIGHT(LEFT(@@VERSION,38),9))


And the following query will work on SQL Server 2000 and up:

SELECT ‘SQL Server ‘
+ CAST(SERVERPROPERTY(‘productversion’) AS VARCHAR) + ‘ – ‘
+ CAST(SERVERPROPERTY(‘productlevel’) AS VARCHAR) + ‘ (‘
+ CAST(SERVERPROPERTY(‘edition’) AS VARCHAR) + ‘)’

read more »