Avoid IIS redirecting to localhost (DotNetNuke)

If you are working with DNN on your localhost Machine, and want to see your site in another machine. You must add a new alias, in fact DNN just have localhost by default.

So, don’t forget to add the new alias, when you are planning to move your DNN site, somewhere else.

See the picture bellow:

 

Reset sa principal, after install SQL 05 Express

Personal Note, after install VS 2008 and the  SQL Server 05 Express that it’s embedded to it. My sa account was unavailable, so was impossible connect to my SQL Instance using SQL Server sa principal.

Solution ?

1. Log on as Win Authenticated user

2. Open the ‘master’ DB and type:

sp_password @old = null, @new = ‘lisber’,  @loginame =’sa’

go

ALTER LOGIN sa WITH PASSWORD = ‘lisber’ UNLOCK

ALTER LOGIN sa ENABLE
That should be enough

PD:

1) Some users have been writing that ‘For unlocking SA, you just have to connect as a machine administrator to the server, as you observed. The machine administrators are by default granted access to SQL Server’

2)I know that using the ’sa’ is not recommendable, we must create users with the minimum permissions in order to perform their actions, so avoiding using the ’sa’ principal. We must never forget that.

 

MCTS Certified :)

I’m very happy because yesterday i get the MCTS certification (Microsoft Certified Technology Specialist).

I made the 70-431 Test in order to get the ‘Microsoft Certified Technology Specialist – SQL Server 2005′ , to get the MCTS you need to achive a minimum of 70% in your final score!.

What’s next ? BI Certification !! that’s the next target

 

Windows Live Writer Test

It seams a very good app

 

Windows Seven – First Impressions

Well Microsoft does it again!. After Vista big mistake, Seven seems to be the next step from xp.

After using Seven for several hours i found it, easy to use. Visually appealing, but is not a miracle and it won’t change the OS world.

Microsoft put so much effort on the Vista performance issue, the boot loading time is faster than vista, the programs seems to be loading rapidly. I’m Seven comes with plenty of drivers, it was not necessary to find any driver there was all built in. Awesome!

Things i noticed:

• The preview on movies (yeah Mac OS have this feature for long time ….)
• The Stack (Well it’s called this way on OS 10.5)
• Paint is  improved
• The power Button finally is a ‘Shut down Button’ from default (One of the major mistakes on Win Vista User Interaction)

So they take Vista clean the mess and comes with a new fresh OS.

winseven

 

Avoid Cursors

Yes avoid them, hide from them each time someones tells you to use them. Why ?

Performance!!!!

These tinny row by row misters, can make your SS claim for more RAM or put your processor in a nonsense processing.

Instead of them i prefer temp Tables, yeah there is some drawbacks, like locks supports that are part of cursors (Dynamic and Keyset).

So when i need to use a row by row analysis to a rowSet i use temp tables and the Select INTO statement, so there is no need to create Table statement aside of the query, just put it all together and run. For example:

SELECT AlunoID

INTO #MyTempTable

FROM Aluno

WHERE Gender = ‘F’

Remember that when the connection holding this query is closed the MyTempTable will disappear, also remember that all temp Tables are created within the tempDB.

To avoid some dirty reads, it’s better to use some lock mechanism. (to be totally sure, use the serializable lock). It never fails…..

 

Creating Queries That Use Full-Text Search

If your database contains many columns that use string data types such as VARCHAR or NVARCHAR, you might find that searching these columns for data by using the Transact-SQL = and LIKE operators does not perform well. A more efficient way to search text data is to use the SQL Server FTS capabilities.

The follow informationg was obtained from several blog’s, all about SS FTI:

Full-Text Indexing Architecture

You might be a bit surprised to learn that SQL Server doesn’t handle its own full-text indexing tasks. Any version of Windows that SQL Server will run on includes an operating system component named the Microsoft Search Service. This service provides indexing and searching capabilities to a variety of applications, including SQL Server, Exchange, and SharePoint.

SQL Server uses an interface component, the SQL Server Handler, to communicate with the Microsoft Search Service. The Handler extracts data from SQL Server tables that have been enabled for full-text searching and passes it to the search service for indexing.

————-

Architecture

Let us identify different components of Full text search before going ahead with understanding the architecture.

· The Microsoft Full-Text Engine for SQL Server (MSFTESQL)

· The Microsoft Full-Text Engine Filter Daemon (MSFTEFD) that comprises the following:

1. Filter

2. Protocol handler

3. Word breaker

MSFTESQL is a windows service that is a tightly integrated component of SQL Server 2005 which is used as a search engine. This is built on the (MSSearch) technology. MSFTESQL service is mainly involved in providing three functionalities.

· Implementing full-text catalogs and indexes for database

· Querying the database with words, phrases and words in close proximity [meaning of a word]

· Managing the full-text catalogs that are stored in SQL servers

MSSearch is a process in windows system that is responsible for doing the cataloguing and indexing. This file name is mssearch.exe. This process will be used by MSFTESQL service to implement the indexing and full-text catalogs.

————-

Implementing Full Text search

Let us discuss the steps for implementing full-text search in SQL Server 2005.

· Adding a full text search catalog to the database – To add a full text search catalog we need to open the database node in Management studio and click on the storage node. We can see the Full text catalog in this node. We have an option for adding the full-text catalog by which we can add a new catalog.

· Adding the Full text indexing table – We need to specify to the database that we want to implement the full-text search functionality for a table. To do this we can select the respective table and select the right click option of Full-Text Index and Define Full-Text index. This opens up the Full text indexing wizard.

1. Using the Full text indexing wizard we select a unique index.

2. Once we select a unique index and move to the next step, we select the columns that are eligible for full text queries. This enables the full-text search for the selected columns.

3. We need to select the option of how can we track the changes. If automatically selected then a full population of indexing occurs. To avoid a population at the end of this wizard, select the Do Not Track Changes option, and clear the Start Full Population When Index Is Created checkbox.

4. Once we are done with step 3 we need to map the catalog out of all the catalogs at the database level. Or we could even create a new catalog for the full text search.

5. This is the last step of the wizard. Here we can create a table schedule and catalog schedules and schedule them with time. A table schedule can have a name, time of schedule and occurrences.

Once we create them and click on the finish button the full-text index is created.

— I Followed these steps, but i founded some troubles by the fact that i wasn’t enabling the DB for full text search catalog, and i was forced to run a specific Stored Procedure.

here are some screen shots from those steps:

DB Text Catalog

Warning Message

Run The System SP

Enable the Table and Columns to be indexed

 

SQL Server 2008 (Katmai) First Impression

After installing the new Microsoft’s RDBMS, i’ve been working with it and founding its new features, one of them Intellisense on SSMS, thanks god !!!.

In previous versions of SSMS, there was a third part tool(From RedGate) that had been bringing the intellisense power to ssms, but it had a big downside PERFORMANCE!!.

Until now, i’m not feeling that issue on SSMS, if that time comes we can disabled this feature on the main menu in SSMS UI.

————————————————————————————————————————————————————————————

The other change i saw, is related with the surface configuration area, there is no longer this concept on Katmai, so how we can manage our server ?

well this turns to be a downside a think, now users are forced to install SSMS in order to manage the local/remote connections and other features, instead of installing just the server tools. So after installing the SSMS we click with the right button over the server instance, then

Facets -> Server Configuration -> Remote Acces Enabled (ENABLED)

More about Katmai soon, i’m curious about SSAS, SSIS, SSRS ….