Dont be frustated, there is a way to get your messages deleted from the mail server and you will not see the strikeout in your Microsoft Outlook too. The answer for deleting email from Microsoft Outlook 2007 is Purging.

Go To EDIT and then PURGE and click on PURGE OPTION
There you will see

When you switch to another folder, the items marked for deletion in the original folder are permanently deleted on the server. Items will not be permanently removed when switching folders offline.

Click on the CheckBox and you can now delete email in Microsoft Outlook 2007 with IMAP protocol.

Permalinks are the permanent URLs to your individual weblog posts, as well as categories and other lists of weblog postings. A permalink is what another weblogger will use to link to your article (or section), or how you might send a link to your story in an e-mail message. The URL to each post should be permanent, and never change hence its called permalink.

There are basically two types of Permalinks in Wordpress i.e Ugly Permalinks and Pretty Permalinks.

The Ugly Permalinks are the default configuration in wordpress and they dont need a .htaccess file. The Ugly Permalink would look something like
www.ravikhanal.com/?p=N
These Ugly Permalinks are the default permalinks and dos not utilize .htaccess file and are not Search engine Optimized too.

The Pretty Permalink are search engine optimized URL. If you want your blog to be optimized in search engine you would most likely want to have the pretty Permalink. The pretty permalink will be something like
www.ravikhanal.com/htaccess-and-wordpress/

If you want to have some pretty permalinks like this then you would need a htaccess file.

How to Put the htaccess file in your wordpress blog:

• First open a notepad with blank content and name it as 1.htaccess
• Put the 1. htaccess file on your server
• Rename the 1.htaccess file to .htaccess file
• Copy this code inside the .htaccess file and save the file

# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

Let me describe the scenario first, I had windows 2003 Server and the Clients have Windows 7. The trust relationship between the workstation and Primary domain fails every time the user tries to log in the system. This error was quite annoying as it used to happen quite a lot of time per day on different computers.

Solution:

I logged in using the local account and then right clicked the My Computer and clicked the Network Id to join the domain. After joining the domain, I restarted the computer and then I changed the computer name and restarted the computer. After that I have not faced that error again.

List of DMV in SQL Server 2005

DMV in SQL Server 2005 #1. sys.dm_broker_activated_tasks
DMV in SQL Server 2005 #2. sys.dm_broker_connections
DMV in SQL Server 2005 #3. sys.dm_broker_forwarded_messages
DMV in SQL Server 2005 #4. sys.dm_broker_queue_monitors
DMV in SQL Server 2005 #5. sys.dm_clr_appdomains
DMV in SQL Server 2005 #6. sys.dm_clr_loaded_assemblies
DMV in SQL Server 2005 #7. sys.dm_clr_properties
DMV in SQL Server 2005 #8. sys.dm_clr_tasks
DMV in SQL Server 2005 #9. sys.dm_db_file_space_usage
DMV in SQL Server 2005 #10. sys.dm_db_index_usage_stats
DMV in SQL Server 2005 #11. sys.dm_db_mirroring_connections
DMV in SQL Server 2005 #12. sys.dm_db_missing_index_details
DMV in SQL Server 2005 #13. sys.dm_db_missing_index_group_stats
DMV in SQL Server 2005 #14. sys.dm_db_missing_index_groups
DMV in SQL Server 2005 #15. sys.dm_db_partition_stats
DMV in SQL Server 2005 #16. sys.dm_db_session_space_usage
DMV in SQL Server 2005 #17. sys.dm_db_task_space_usage
DMV in SQL Server 2005 #18. sys.dm_exec_background_job_queue
DMV in SQL Server 2005 #19. sys.dm_exec_background_job_queue_stats
DMV in SQL Server 2005 #20. sys.dm_exec_cached_plans
DMV in SQL Server 2005 #21. sys.dm_exec_connections
DMV in SQL Server 2005 #22. sys.dm_exec_query_memory_grants
DMV in SQL Server 2005 #23. sys.dm_exec_query_optimizer_info
DMV in SQL Server 2005 #24. sys.dm_exec_query_resource_semaphores
DMV in SQL Server 2005 #25. sys.dm_exec_query_stats
DMV in SQL Server 2005 #26. sys.dm_exec_query_transformation_stats
DMV in SQL Server 2005 #27. sys.dm_exec_requests
DMV in SQL Server 2005 #28. sys.dm_exec_sessions
DMV in SQL Server 2005 #29. sys.dm_fts_active_catalogs
DMV in SQL Server 2005 #30. sys.dm_fts_index_population
DMV in SQL Server 2005 #31. sys.dm_fts_memory_buffers
DMV in SQL Server 2005 #32. sys.dm_fts_memory_pools
DMV in SQL Server 2005 #33. sys.dm_fts_population_ranges
DMV in SQL Server 2005 #34. sys.dm_io_backup_tapes
DMV in SQL Server 2005 #35. sys.dm_io_cluster_shared_drives
DMV in SQL Server 2005 #36. sys.dm_io_pending_io_requests
DMV in SQL Server 2005 #37. sys.dm_os_buffer_descriptors
DMV in SQL Server 2005 #38. sys.dm_os_child_instances
DMV in SQL Server 2005 #39. sys.dm_os_cluster_nodes
DMV in SQL Server 2005 #40. sys.dm_os_hosts
DMV in SQL Server 2005 #41. sys.dm_os_latch_stats
DMV in SQL Server 2005 #42. sys.dm_os_loaded_modules
DMV in SQL Server 2005 #43. sys.dm_os_memory_allocations
DMV in SQL Server 2005 #44. sys.dm_os_memory_cache_clock_hands
DMV in SQL Server 2005 #45. sys.dm_os_memory_cache_counters
DMV in SQL Server 2005 #46. sys.dm_os_memory_cache_entries
DMV in SQL Server 2005 #47. sys.dm_os_memory_cache_hash_tables
DMV in SQL Server 2005 #48. sys.dm_os_memory_clerks
DMV in SQL Server 2005 #49. sys.dm_os_memory_objects
DMV in SQL Server 2005 #50. sys.dm_os_memory_pools
DMV in SQL Server 2005 #51. sys.dm_os_performance_counters
DMV in SQL Server 2005 #52. sys.dm_os_ring_buffers
DMV in SQL Server 2005 #53. sys.dm_os_schedulers
DMV in SQL Server 2005 #54. sys.dm_os_stacks
DMV in SQL Server 2005 #55. sys.dm_os_sublatches
DMV in SQL Server 2005 #56. sys.dm_os_sys_info
DMV in SQL Server 2005 #57. sys.dm_os_tasks
DMV in SQL Server 2005 #58. sys.dm_os_threads
DMV in SQL Server 2005 #59. sys.dm_os_virtual_address_dump
DMV in SQL Server 2005 #60. sys.dm_os_wait_stats
DMV in SQL Server 2005 #61. sys.dm_os_waiting_tasks
DMV in SQL Server 2005 #62. sys.dm_os_worker_local_storage
DMV in SQL Server 2005 #63. sys.dm_os_workers
DMV in SQL Server 2005 #64. sys.dm_qn_subscriptions
DMV in SQL Server 2005 #65. sys.dm_repl_articles
DMV in SQL Server 2005 #66. sys.dm_repl_schemas
DMV in SQL Server 2005 #67. sys.dm_repl_tranhash
DMV in SQL Server 2005 #68. sys.dm_repl_traninfo
DMV in SQL Server 2005 #69. sys.dm_tran_active_snapshot_database_transactions
DMV in SQL Server 2005 #70. sys.dm_tran_active_transactions
DMV in SQL Server 2005 #71. sys.dm_tran_current_snapshot
DMV in SQL Server 2005 #72. sys.dm_tran_current_transaction
DMV in SQL Server 2005 #73. sys.dm_tran_database_transactions
DMV in SQL Server 2005 #74. sys.dm_tran_tran_locks
DMV in SQL Server 2005 #75. sys.dm_tran_session_transactions
DMV in SQL Server 2005 #76. sys.dm_tran_top_version_generators
DMV in SQL Server 2005 #77. sys.dm_tran_transactions_snapshot
DMV in SQL Server 2005 #78. sys.dm_tran_version_store

New DMV in SQL Server 2008
DMV in SQL Server 2008 #1. sys.dm_audit_actions
DMV in SQL Server 2008 #2. sys.dm_audit_class_type_map
DMV in SQL Server 2008 #3. sys.dm_cdc_errors
DMV in SQL Server 2008 #4. sys.dm_cdc_log_scan_sessions
DMV in SQL Server 2008 #5. sys.dm_cryptographic_provider_properties
DMV in SQL Server 2008 #6. sys.dm_database_encryption_keys
DMV in SQL Server 2008 #7. sys.dm_db_mirroring_auto_page_repair
DMV in SQL Server 2008 #8. sys.dm_db_mirroring_past_actions
DMV in SQL Server 2008 #9. sys.dm_db_persisted_sku_features
DMV in SQL Server 2008 #10. sys.dm_db_script_level
DMV in SQL Server 2008 #11. sys.dm_exec_procedure_stats
DMV in SQL Server 2008 #12. sys.dm_exec_trigger_stats
DMV in SQL Server 2008 #13. sys.dm_filestream_file_io_handles
DMV in SQL Server 2008 #14. sys.dm_filestream_file_io_requests
DMV in SQL Server 2008 #15. sys.dm_fts_fdhosts
DMV in SQL Server 2008 #16. sys.dm_fts_outstanding_batches
DMV in SQL Server 2008 #17. sys.dm_os_dispatcher_pools
DMV in SQL Server 2008 #18. sys.dm_os_dispatchers
DMV in SQL Server 2008 #19. sys.dm_os_memory_brokers
DMV in SQL Server 2008 #20. sys.dm_os_memory_node_access_stats
DMV in SQL Server 2008 #21. sys.dm_os_memory_nodes
DMV in SQL Server 2008 #22. sys.dm_os_nodes
DMV in SQL Server 2008 #23. sys.dm_os_process_memory
DMV in SQL Server 2008 #24. sys.dm_os_spinlock_stacks
DMV in SQL Server 2008 #25. sys.dm_os_sys_memory
DMV in SQL Server 2008 #26. sys.dm_resource_governor_configuration
DMV in SQL Server 2008 #27. sys.dm_resource_governor_resource_pools
DMV in SQL Server 2008 #28. sys.dm_resource_governor_workload_groups
DMV in SQL Server 2008 #29. sys.dm_server_audit_status
DMV in SQL Server 2008 #30. sys.dm_tran_commit_table
DMV in SQL Server 2008 #31. sys.dm_xe_map_values
DMV in SQL Server 2008 #32. sys.dm_xe_object_columns
DMV in SQL Server 2008 #33. sys.dm_xe_objects
DMV in SQL Server 2008 #34. sys.dm_xe_packages
DMV in SQL Server 2008 #35. sys.dm_xe_session_event_actions
DMV in SQL Server 2008 #36. sys.dm_xe_session_events
DMV in SQL Server 2008 #37. sys.dm_xe_session_object_columns
DMV in SQL Server 2008 #38. sys.dm_xe_session_targets
DMV in SQL Server 2008 #39. sys.dm_xe_sessions

I have my DTS package on my File System, so I am choosing Structured Storage File. If you have your DTS Package on the Database then you can choose the Source as SQL Server.

Then You have to choose the destination. In my case again I am using DTSX file as my destination.

Then you can choose the package and edit the destination package name.

Then you can specify the log file.

Then the Package Migration is completed.

1. Google’s advertizing model will start facing problems:
Google will have some problems with their advertizing model in the year 2009 and advertisers would be less interested in Google’s ads. Google’s ad should not be context based but rather be user based. Google should read the mind of the user and display the ad, exactly what he is looking for. There should be more localization in the Google’s ads. Now a day people are not so much interested in the Google’s ads, so either Google has to change its advertizing model or it will start facing problems.

2. Microsoft will inch ahead due to Google’s loss of reputation:
Year 2009 will be really bad for the Google. Google is acting as a spy and tracking all the data from cookies. Everybody will think twice before using Google. So the charm of Google is reducing day by day and it will slowly fall behind in the race against Microsoft.

3. Standards will evolve in the Clouds:
Till now everybody has defined cloud according to their way. But in the year 2009, some standards will evolve in the clouds and there will be SLAs .

4. Amazon will appear as the next big thing after Microsoft and Google:
Amazon has now everything and it will evolve as the next big thing after Microsoft and Google. Amazon’s Cloud will be the major success in the year 2009.

5. Virtual Societies will evolve on top of the social networking
Social networking sites will be a downward spiral. Virtual Societies will evolve on the top of the social networking on the year 2009. People will start making virtual societies around them with the same kind of interest and website promoting these virtual societies will become the major highlight for the year 2009.

6. Research will happen on Image Search and Video Search:
Till now we are having Image Search and Video Search only based on the text search associated with the Image and Video. But there would be research on Image Search and Video Search. Till now if the title of any videos is different then we could never get to the videos but if we have Video Search option available then this would be the milestone for stopping piracy on videos. So in the year 2009, big media companies will be sponsoring Universities to research on “Search based on Image and Video”.

7. Yahoo as a Company might be divided into several pieces.
Yahoo as a Company might be divided into several pieces and Google will buy some part of it and Microsoft will buy some part of it. Microsoft will likely buy the search part of the yahoo. Google will buy the messenger of yahoo and combine with their gtalk.

8. Google will buy Mozilla:
Due to and despite the modest success of the Chrome, Google will buy Mozilla to compete against the Internet Explorer.

9. Google App Engine will support Ruby
Till now Google App Engine only supports Python but in the year 2009, it will also support Ruby.

10. Java will evolve through dynamic languages but the SUN will be in crisis
Since Java is moving more towards the open source, Java will evolve through other dynamic languages but SUN will be in crisis.

• Enterprise Reporting Engine

There are two major infrastructure changes for Reporting Services. Reporting Services enhances the processing engine and rendering extensions to enable new functionality, such as Tablix support, and scalability as well as remove the dependency on IIS. Additionally, new report designer and configuration tool are provided that improve usability and workflow for RS customers.

• Analysis Services Time Series

This improvement adds a new time series forecasting algorithm (ARIMA: Auto Regressive Integrated Moving Average) to the data mining algorithm suite that provides more stable long term predictions.

In Data warehouses, spaces used to be always wasted due to the NULL values. Columns having lots of NULL value is actually allocating lots of space without storing any values. This problem has been taken care in SQL Server 2008 by the introduction of a sparse columns. This columns allows NULL values to be stored without taking any physical space on the disk.

T-SQL Improvements

Object Dependencies: The object dependencies improvement provides reliable discovery of dependencies between objects through newly introduced catalog view and dynamic management functions. Dependency information is always up-to-date for both schema-bound and non-schema-bound objects. Dependencies are tracked for stored procedures, tables, views, functions, triggers, user-defined types, XML schema-collections, and more.

Performance Data Collection
Collect data from various sources in SQL Server and OS to help with performance troubleshooting and server maintenance. With this improvement, organizations improve their analysis of common performance issues:

•  Define what data is collected and organize the collection into collection sets
•  Start/stop/manipulate collection sets programmatically (T-SQL and .NET API)
•  Define where data is stored (relational database)
•  View data through reports in SQL Server Management Studio.
•  Provide platform to plug in more data collectors in the future.

Extended Events

SQL Server Extended Events is a general event-handling system for server systems. The Extended Events infrastructure supports the correlation of data from SQL Server, and under certain conditions, the correlation of data from the operating system and database applications. In the latter case, Extended Events output must be directed to Event Tracing for Windows (ETW) in order to correlate the event data with operating system or application event data.

Database Mirroring Enhancements
SQL Server 2008 builds upon the momentum of SQL Server 2005 by providing a more reliable platform with enhanced database mirroring:

Automatic bad page repair – allows the principal and mirror machines to transparently recover from 823/824 types of data page errors by requesting a fresh copy of the corrupted page from the mirroring partner.

Log stream compression – compression of the outgoing log stream in order to minimize the network bandwidth used by database mirroring.

Miscellaneous performance enhancements:
using asynchronous log write requests on the mirror in order to shorten the log write time and thus speed-up the commit acknowledgement.

better utilization of the mirroring log send buffers in order to pack multiple smaller log blocks into a single network send.

Supportability and diagnosability improvements:
additional performance counters to allow for more granular accounting of the time spent across the different stages of the DBM log processing.

new DMVs and extensions of existing views in order to expose additional information about the mirroring sessions.

ORDPATH Improvement
ORDPATH improvement provides an important new functionality to our customers who use hierarchical data. It provides a superior way of modeling hierarchies in SQL Server by introducing the HierarchyID system data type and corresponding built-in methods which are designed to make it easier to store, query and operate hierarchical data. HierarchyID is also optimized for representing trees, the most common type of hierarchical data.

Large User-Defined Types Improvement
Large user-defined types allows users to expand the size of defined data types by eliminating the 8‑KB limit.

DATE/TIME Data Types
SQL Server 2008 introduces new date and time data types. The new data types enable applications to have separate date and time types, larger year ranges for date value, larger fractional seconds precision for time value, time-zone offset aware datetime type that containing date, time and time zone offset portion, user defined option on fractional seconds precision of time related types and datetime2 and datetimeoffset provide standards conformant semantics. Along with the T-SQL support on the new types, both native (ODBC, OLEDB) and managed (SqlClient) providers also provide the full support through the client driver APIs.

Improved XML Support
To leverages the new date and time types, SQL Server’s XML Schema collection now provides full support for the xs:date, xs:time and xs:dateTime data types. Support for union types is also enhanced by returning correct results for “instance of” queries when union types are involved, and adding support for lists of unions and unions of lists constructs in XML Schemas.

SSMS Improvement
SQL Server Management Studio(SSMS) has been improved a lot in SQL Server 2008. Most important improvement in SSMS 2008 are:

• Activity Monitor
• Object Explorer Details
• Object Search
• Multi-server Queries
• Intellisense added to the query Editor
• T-SQL Debugger Added to the Query Editor

Backup Database test
to disk='C:\test\test1.bak'
with compression

Plan Freezing

Data Compression

Hot-Add CPUs and Hot-Add Memory

So let’s discuss what is the cause behind this. SQL Server logins are stored in the master database and they are mapped against individual databases. The Login informations on SQL Server 2005 are visible through sys.server_principals system catalog view and the sys.logins view. The mapping information of the database user is stored in the sysusers system table. This table includes the name of the database user and the SID of the corresponding SQL Server Login. The SID is the security identifier and SID tracks the logins throughout the entire systems.

So when we move or copy our database from one server to another or from one instance to another then the windows login will have the same SID but the SQL logins may have the different SIDs. So when the SID of the new server instance and the older instance doesn’t matches we have a Orphaned User.

So if you are copying or moving a database from one server to another, then you should follow these steps:

1. Backup the source database.
2. Create the logins on the destination server.
3. Restore the database on the destination server.
4. Synchronize logins if not completed in step 2.

So for Synchronizing the logins, first you need to check all the users that are present.
Select 'user', * from sys.sysusers

Then check whether those users have logins or not by
Select 'Login', * from sys.server_principals

If there is orphaned user for user ‘dave’ then you should create the login with the same SID as its SID in the source server. This can be done by

Create login dave with Password = 'password', SID=0x8103F8ADEEADFA44BC4FE23836BCCE93


Another way of synchronizing the login can be done by system stored procedure.

Exec sp_change_users_login Report

This code will list out all the orphaned users and their corresponding SID.

Then after this you can do

Exec sp_change_users_login AUTO_FIX, 'lisa', 'password'

So the Auto_Fix will create a new login with the new SID and then match those with the User’s SID.

After this also you have more orphaned user then you can do

Exec sp_change_users_login 'update one', 'john', 'password'

But there is one major problem with using the stored procedure sp_change_users_login, when you restore the database again then the sp_change_users_login will be gone. So you would have to again do the whole process again. So sp_change_users_login is fine if you are moving database only once. If it is a repeatable transfer of a database from server to server then this sp_change_users_login is not useful.

Login Synchronization can be done through SSIS as well. SSIS also uses random SIDs at the destination and sp_change_users_login type to work to remap the users accounts to the newly generated SIDs.

Another way of Synchronization can be done through sp_help_revlogin. So we need to first download sp_help_revlogin from the Microsoft’s kb246133, then execute sp_help_revlogin on the source and copy the result. Then run the copied result in the destination server. So this will solve the orphaned users problem.

Solution:

So First I need to have the data flow task for this.

Then in the data flow the package would be like this:

Let us first add the flat file connection Manager, Excel Connection Manager, and Oledb Connection Manager.

In the flat file Source add the Flat file connection Manager.

In the Excel Source add the Excel Source connection Manager.

Since the data in Excel is in Unicode format so it should be converted into string format using Data Conversion Transformation.

Before the data is merged, it should be sorted. So lets sort the Flat file Source and converted data of Excel by First Name and Last Name.

Then after Sorting the data, it should be merged.

Then after merging the data, the first name column should be changed to uppercase. So the Character Map Transformation should be used.

After changing the data into uppercase, we have to add a new Salary column which could show the raise in the salary. So the derived column transformation has to be used which will calulate the 20% increase in salary.

Then finally the OLEDB destination is added where all the data is dumped. In this OLEDB Destination the OLEDB Connection manager is added and the desired table is selected and mapped.