Sophisticated Database Conversion and Data Migration.

Sophisticated Database Conversion and Data Migration.Full Convert Enterprise is the easiest and most feature-rich database converter on the market. It will effortlesly migrate your database tables with all the data, create indexes, foreign keys - and more. When you do need the power, you will find unmatched customization features, conversion scheduler for recurring migrations, built-in database explorer, extremely powerful command-line interface, character set conversion, global datatype translation rules, support for SQL expressions to transform data on the fly - and much much more.
Microsoft Access
dBase
FoxPro
Microsoft Excel
Interbase
Firebird
Lotus 1-2-3
MySQL
ODBC
Oracle
Paradox
PostgreSQL
SQL Server
SQL Server Compact
Delimited text files (CSV)
XML

Handles databases of unlimited size. Literally.
Full Unicode support
Creates all data, indexes and foreign keys
Data throughput of thousands of records/sec
Easily handles hundreds of gigabytes of data
Advanced command-line support
Built-in scheduler for recurring conversions
BLOB and MEMO fields are fully supported
Runs on all Windows versions
See what's new in version 5
See what's new in version 4
All features

Complete translation of your whole SQL Server database

Easily migrate all your database objects:
Tables, Indexes, Constraints
Views
Procedures
Functions
Triggers
Table data, including memo and binary fields

Using SQL Tran, you are using a tool which manages near 100% fully automated translation of your database logic. Of course, you can modify the translated statements and maintain your customizations in a saved project. For many databases, our tool does a full 100% translation with no modifications needed!
For more details visit : http://www.spectralcore.com/sqltran/

Microsoft SharePoint Administration Toolkit released

The SharePoint product team has released the first version of the Microsoft SharePoint Administration Toolkit which is supported on MOSS and WSS.

Get all the details at the SharePoint team's blog: http://blogs.msdn.com/sharepoint/archive/2008/04/30/announcing-the-first-release-of-the-microsoft-sharepoint-administration-toolkit.aspx

The STSADM.EXE Command Line Utility

WSS ships with a handy command-line utility named STSADM.EXE. This utility allows you to run interactive commands from the Windows command line and to script batch files that accomplish administrative tasks such as creating, backing up, and restoring site collections. When you run this utility from the command line or from a batch file, you must pass the –o parameter followed by one of the supported operations. Here’s an example of a command line instruction to create a new site collection at a specific URL.

STSADM.EXE –o CreateSite –url http://mshehadeh/sites/blog
-ownerlogin mshehadeh\admin
-owneremail mail@mshehadeh.com
-sitetemplate STS#0

Note that this example has introduced line breaks between the parameters to make things more readable. However, you cannot actually use line breaks between the parameters when running the STSADM utility from the command line or from a batch file.
Keep in mind that the installation of WSS adds the STSADM.EXE utility to a WSS system directory deep within the Windows Program Files directory. If you want to be able to call this utility directly from the command line on your development workstation, you should add the following path to your configured System path.
c:\program files\common files\microsoft shared\web server extensions\12\bin\
This System path is known as 12HIVE

When you write a batch file, you should also assume that it might be run on a machine that does not have the proper System path configured. Therefore, you should write batch files that explicitly specify the location of the STSADM.EXE utility.

@SET STSADM="c:\program files\common files\microsoft shared\
web server extensions\12\bin\stsadm"
%STSADM% –o CreateSite –url http://mshehadeh/sites/blog
-ownerlogin mshehadeh\admin
-owneremail mail@mshehadeh.com
-sitetemplate STS#0

Once again, the line breaks in the preceding example are only for readability. You will want to remove them when writing an actual batch file.

Free Sharepoint Hosting

You want a free sharepoint hosting?
TRY IT FREE
No Time Limit
5 MB Disk Space
5 Users

SharePoint Training Tutorials

Step by Step How To Instructions

In these SharePoint screencast tutorials, get step by step instructions on all the features included in SharePoint hosting and how to optimize your site. The tutorials cover topics from Alerts and Creating Web Parts to Creating Meetings Sites and Wikis.
Go ahead and try it at http://www.frontpages-web-hosting.net/sharepoint-hosting/free-sharepoint-tutorials.asp

Optimization of Virtual Machine Size and Performance

While googling for a software that help me on optimizing my virtual machines size,i found a great software named vOptimizer.

vOptimizer is an advanced optimization solution that quickly and easily reduces a virtual machines virtual hard drive to the smallest size possible while optimizing Windows guest operating systems for speed and performance. vOptimizer 4.0 offers many new functions for enterprise level customers while improving the interface and ease of operation for smaller, desktop oriented users. vOptimizer Desktop Edition enables unlimited optimizations of local VMs while Network Edition enables unlimited optimizations of VMs located anywhere across the network as well as scheduled optimizations. vOptimizer FreeWare is essentially Desktop Edition with a number of features disabled and additional popup messages

Download vOptimizer

How to Create a MOSS 2007 VPC Image

As SharePoint-y guys - virtualization is a *must* for us.
I found a great article about creating a sharepoint Virtual PC Image,this is a complete step by step article that shows you How to Create a MOSS 2007 VPC Image
Enjoy it

I am back

I am back to writing . i will be writing about Windows Sharepoint Services 3.0 (WSS 3.0), and Office Sharepoint 2007 (MOSS 2007).,
I will share with you some resources and articles about WSS 3.0 and MOSS 2007

Restoring SQL Server 2005 Suspect Database

I had a SQL Server 2005 database in suspect mode,so i couldn't work on transaction until i repaired,while i am searching on the internet to resolve this problem i found an new Database status called Emergency introduced in SQL Server 2005.
This mode can change the database from Suspect mode to Emergency mode, so that you can retrieve the data in read only mode.
Please follow the following steps to change the database status from suspect to emergency than to it's normal state:

EXEC sp_resetstatus 'DBname'

ALTER DATABASE DBname SET EMERGENCY

DBCC checkdb('DBname')

ALTER DATABASE DBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE

DBCC CheckDB ('DBname', REPAIR_ALLOW_DATA_LOSS)

ALTER DATABASE DBname SET MULTI_USER

I hope that will help you to get your database working

FTP Put file using t-sql

I have to use a stored procedure which will send/Receive text file
from/to a server by using FTP.

So i googled on the net and i found a very interesting stored procedure written by Nigel Rivett
that will upload a file from the database.
But before using this stored procedure on SQL Server 2005,XP_CMDSHELL must be enabled,
because it's disabled by default on SQL Server 2005 for security reasons.
There are two ways to enable this option: Surface Area Configuration tool or sp_configure.
Enabling this option via Surface Area Configuration tool is rather straight forward.
Here is the instructions to enable xp_cmdshell in SQL Server 2005 via Surface Area Configuration tool:

1. Click the Start button.

2. Select All Programs.

3. Navigate to the Microsoft SQL Server 2005 folder.

4. On the flyout, mouseover Configuration Tools.

5. Select SQL Server Surface Area Configuration.

6. The SQL Server 2005 Surface Area Configuration window will appear.

7. At the bottom of the window, select Surface Area Configuration for Features.

8. In the left pane, under Database Engine, select xp_cmdshell.

9. Check the Enable xp_cmdshell checkbox.

10. Click OK.

11. Close the SQL Server 2005 Surface Area Configuration window.

Here is the script to enable xp_cmdshell in SQL Server 2005 via sp_configure:

EXEC master.dbo.sp_configure 'show advanced options', 1

RECONFIGURE

EXEC master.dbo.sp_configure 'xp_cmdshell', 1

RECONFIGURE


-- FTP Put file using t-sql.
-- Author Nigel Rivett

This needs a work directory to create a FTP command file to execute.
In a multi-user system include the spid in the filename to make it unique for the connection.


if exists (select * from sysobjects where id = object_id(N'[dbo].[s_ftp_PutFile]') and OBJECTPROPERTY(id, N'IsProcedure') = 1)
drop procedure [dbo].[s_ftp_PutFile]
GO


Create procedure s_ftp_putfile
@FTPServer varchar(128) ,
@FTPUser varchar(128) ,
@FTPPWD varchar(128) ,
@FTPPath varchar(128) ,
@FTPFileName varchar(128) ,
@SourcePath varchar(128) ,
@SourceFile varchar(128) ,
@workdir varchar(128)
as


declare @cmd varchar(1000)
declare @workfilename varchar(128)

/* usage:
exec s_ftp_putfile
@FTPServer = 'ftpserver' ,
@FTPUser = 'user' ,
@FTPPWD = 'password' ,
@FTPPath = 'path/' ,
@FTPFileName = 'test.txt' ,
@SourcePath = 'c:\' ,
@SourceFile = 'test.txt' ,
@workdir = 'c:\temp\'
*/

select @workfilename = 'ftpcmd.txt'

-- deal with special characters for echo commands
select @FTPServer = replace(replace(replace(@FTPServer, '', '^'),'<','^<'),'>','^>')
select @FTPUser = replace(replace(replace(@FTPUser, '', '^'),'<','^<'),'>','^>')
select @FTPPWD = replace(replace(replace(@FTPPWD, '', '^'),'<','^<'),'>','^>')
select @FTPPath = replace(replace(replace(@FTPPath, '', '^'),'<','^<'),'>','^>')

select @cmd = 'echo ' + 'open ' + @FTPServer
+ ' > ' + @workdir + @workfilename
exec master..xp_cmdshell @cmd
select @cmd = 'echo ' + @FTPUser
+ '>> ' + @workdir + @workfilename
exec master..xp_cmdshell @cmd
select @cmd = 'echo ' + @FTPPWD
+ '>> ' + @workdir + @workfilename
exec master..xp_cmdshell @cmd
select @cmd = 'echo ' + 'put ' + @SourcePath + @SourceFile + ' ' + @FTPPath + @FTPFileName
+ ' >> ' + @workdir + @workfilename
exec master..xp_cmdshell @cmd
select @cmd = 'echo ' + 'quit'
+ ' >> ' + @workdir + @workfilename
exec master..xp_cmdshell @cmd

select @cmd = 'ftp -s:' + @workdir + @workfilename

create table #a (id int identity(1,1), s varchar(1000))
insert #a
exec master..xp_cmdshell @cmd

select id, ouputtmp = s from #a

go

Converting the database mirroring from High Availability to High Performance

In the previous article i showed you how to configure database mirroring using the high availability configuration through a SQLCMD master script.
What if we want to change the configuration from high availability mode to high performance mode,we will need to clean the configuration and reconfigure it again?
The answer is no,we can convert the configuration.
All what we need to do is to set both the witness and the safety off

-- ConvertToHighPerf.sql

/*========================================================
File: ConvertToHighPerf.sql

Summary: Change the High Availability configuration
over to High Performance.
Turn off the witness, turn off safety!

Date: August 2007
==========================================================*/

:SETVAR PrincipalServer MSHEHADEHVPC\SQLDev01
:SETVAR MirrorServer MSHEHADEHVPC\SQLDev02
:SETVAR Database2Mirror AdventureWorksDW
go

:ON ERROR EXIT
go

:CONNECT $(PrincipalServer)

ALTER DATABASE $(Database2Mirror)
SET WITNESS OFF
go

ALTER DATABASE $(Database2Mirror)
SET SAFETY OFF
go

SELECT DATABASEPROPERTYEX(N'$(Database2Mirror)', N'Status')
-- Returns ONLINE
SELECT db_name(sd.[database_id]) AS [Database Name],
sd.mirroring_guid,
sd.mirroring_state,
sd.mirroring_state_desc,
sd.mirroring_partner_name,
sd.mirroring_witness_name,
sd.mirroring_witness_state,
sd.mirroring_witness_state_desc,
sd.mirroring_role,
sd.mirroring_role_desc,
sd.mirroring_role_sequence,
sd.mirroring_safety_level,
sd.mirroring_safety_level_desc,
sd.mirroring_safety_sequence,
sd.mirroring_failover_lsn
FROM sys.database_mirroring AS sd
WHERE sd.[database_id] = db_id(N'$(Database2Mirror)')
go

:CONNECT $(MirrorServer)
SELECT DATABASEPROPERTYEX(N'$(Database2Mirror)', N'Status') -- Returns RESTORING
SELECT db_name(sd.[database_id]) AS [Database Name],
sd.mirroring_guid,
sd.mirroring_state,
sd.mirroring_state_desc,
sd.mirroring_partner_name,
sd.mirroring_witness_name,
sd.mirroring_witness_state,
sd.mirroring_witness_state_desc,
sd.mirroring_role,
sd.mirroring_role_desc,
sd.mirroring_role_sequence,
sd.mirroring_safety_level,
sd.mirroring_safety_level_desc,
sd.mirroring_safety_sequence,
sd.mirroring_failover_lsn
FROM sys.database_mirroring AS sd
WHERE sd.[database_id] = db_id(N'$(Database2Mirror)')
go