Wednesday, 30 June 2010

DB2 – Create a Database

OK for my next DB2 trick and remaining off the path of the righteous for the time being we will look at creating a DB2 database. I assume that you have the DB2 RDBMS software installed, you can get a free 'community' copy of the express edition, follow this link for the download. Being a SQL DBA with an MSDN subscription I installed DB2 on Windows Server R2 2003 running on VM Workstation. It can also run on a variety of *nix OS too.

As with SQL Server there are many ways to create a database in DB2. In this example I am going to use the wizard, I'm new to this so I'll go with the simple approach. Assuming you have all the components installed, as I do, you need to fire up Control Manager.

Note: There are differences in the physical architecture of database files when comparing DB2 to SQL Server. As my understanding improves I may write a little about that topic but for now we'll focus on using wizard and creating a database.

Before we start let me give you a bit of background on this server I setup, I'm not yet all the knowledgeable on ideal performance layout for DB2 and as this was setup for me to learn a bit more about DB2 so I configured my server with a C:\ drive which houses the OS and the DB2 software and an E:\ drive which I intended to use for the data.

We'll now create a database using the wizard in Control Manager. So how do I open Control Manager, here's how I do it on my Windows Box:

Click

  • <Start>
  • <All Programs>
  • <IBM DB2>
  • <DBCOPY1(DEFAULT)>
  • <General Administration Tools>
  • <Control Centre>

ControlManager

When Control Manager opens you are asked prompted by the Control Center View box to specify the view that you want. "Advanced" was selected by default so I went with that and clicked OK. My DB2 instance and the databases installed as part of the install were already registered. These are Sample and Schedule:

CMopen

To create a database:

  • Right Click <All Databases>
  • Select <Create Database>
  • Select <Standard>

This starts up the Create Database Wizard:

Enter a name for your database in my case I called it GETEST and I set the default path for the database to be the e:\ drive and a folder called data.

I took all other default settings, Let DB2 manage my storage (automatic storage). I left the default bufferpool and table space page size at 4K:

 

CreateDB

I made no changes on the storage tab, because I specified a default path and let DB2 manage my storage on the name tab I have no changes to make here. Click <Next>

For simplicity I make no changes on the Region tab and I take the default settings. Click <Next>

on the summary tab it give you a "Show Command" button which gives you the underlying code that will execute

CREATE DATABASE GETEST
AUTOMATIC STORAGE YES ON 'E:\DATA'
DBPATH ON 'E:\DATA'

USING CODESET IBM-1252 TERRITORY US COLLATE USING SYSTEM PAGESIZE 4096;

So there we go as you can see that the syntax is very similar to its TSQL equivalent.

Click on <Finish>

This should cause DB2 to go away and create you a nice new database.

except in my case it doesn't create a database. I get the following error:

"SQL1052N  The database path "E:\DATA" does not exist.

Explanation :

The path specified in the "<path>" parameter of the command is not
valid. Either there is no path with that name, or a path has been
specified when the DB2_CREATE_DB_ON_PATH registry variable is disabled
(Windows only).

Well I the path is there so it must be the later in the explanation " a path has been specified when the DB2_CREATE_DB_ON_PATH registry variable is disabled (Windows only)"

Well it is windows, so I guess this is viable.

So how do I enable this registry variable. It is very simple.

Open a command prompt on the server and run the following:

db2set DB2_CREATE_DB_ON_PATH=YES

You won't get any message confirming it has been set or any errors telling you it hasn't worked, when I run it i just got another command prompt.

You then need to restart the DB2 Service, mine is listed in the services as:
DB2 - DB2COPY1 - DB2

Restart that service.

and re-run the wizard and you should get yourself a brand new DB2 database.

Monday, 28 June 2010

DB2 Editions

This is a little bit off topic for me but on Friday I was asked to look at a DB2 instance and sort out some issues with the CPU maxing out. Make no mistake I’m no DB2 expert, but I have done some small pieces of work on it previously, and about a year ago I started making some notes . I’m going to turn these notes into blog posts, this will help my learning and give a place to reference and maybe it will help someone else out on the way.

DB2 like SQL Server has a series of edition with different features available in each one, here are some notes on the DB2 editions:

DB2 Express C – Full functional version of DB2 that is free to download use and distribute. The C stands for Community.

DB2 Express edition – Similar to the Express C version but there is a cost for support for this edition. It is designed for a quick installation and subsequent use. It supports 2 CPUs and 4GB of RAM. It can run on Linux, Windows and Solaris.

DB2 personal edition – Designed for single user use, It frugal with resources.

DB2 Everyplace 9 – For on a range of devices, PDAs, mobile phones etc. Ideal for distributed applications.

DB2 Workgroup Edition – Allows 4 CPUS and 16GB RAM

DB2 Enterprise edition – DB2 unleashed. No limits

DB2 developer edition – Enterprise edition features for the developer.

DB2 Datawarehouse Edition – has features to support DW environments.

So that’s it, my first post on DB2 looking at the available editions, there will be some further posts to follow when I get chance to turn my notes into posts.

Friday, 25 June 2010

Lock Pages in Memory

It is generally recommended that 'lock pages in memory' be enabled for your SQL Servers to prevent the OS paging out SQL Server memory.

how do you do this?

Well, the answer is straight forward...If you have SQL Server Enterprise Edition:

You allocate the service account running SQL Server the 'Lock Pages In Memory' permission.

How Can I Tell if 'Lock Pages in Memory is Enabled?'

Note

I am using Windows 2003 R2 and SQL Server 2008 SP1 for this demo but I have also done this on Windows 2008 R2 and it works just the same way. It is a 64 bit environment.

If you are running SQL Server with the Local System account, I know most of you are not, but for those of you that are, SQL Server will automatically 'lock pages in memory'. Bob Ward has a blog post on this here: (http://blogs.msdn.com/b/psssql/archive/2007/10/18/do-i-have-to-assign-the-lock-privilege-for-local-system.aspx)

If you are using the local system or a domain account with appropriate permissions you will see an entry similar to the following at the start of the SQL Server log:

LockPagesInMemoryIsEnabled

Therefore if you are running SQL Server using a domain account and the domain account does not have the necessary permissions to lock pages in memory then you will not have this message in the log:

LockPagesInMemoryIsNotEnabled

If you do not have 'Lock Pages In Memory' enabled and you would like too enable it then follow these steps:

Logon to the SQL Server in question

Click <Start><Run> and enter 'secpol.msc' in the run box.

In the 'Local Security Policy' window that opens expand <Local Policies> and <User Rights Assignment> in the left hand pane.

LocalSecurityPolicyWindow

In the right hand pain scroll down to the 'lock pages in memory' policy. Right Click, select <Properties> <Add User or Group> and add the domain account that is running the SQL Service and click <OK>

LockPagesInMemory

That's it, you need to restart the SQL Server service for the change to take effect, the next time that SQL Server starts up you should see

LockPagesInMemoryIsEnabled

in the SQL Server log.

Standard Edition

Up until SQL Server 2005 SP3 Cumulative Update Package 4 and SQL Server 2008 SP1 Cumulative Update Package 2 'Lock Pages in Memory' was not supported in SQL Server Standard Edition.

You may find this link helpful

http://support.microsoft.com/kb/970070

as you need to request the CUs from Microsoft. They will then send you a link to download the CU.

These two CUs add the 'lock pages in memory' option for SQL Server Standard edition.

Note you you have to enable trace flag 845 to for standard edition to be able to 'lock pages in memory.'

Virtualisation, SQL Server and Lock Pages

Are you running SQL Server in Virtual Land, well here is something else to to consider care of Mr Denny:

http://itknowledgeexchange.techtarget.com/sql-server/vmware-and-sql-and-lock-pages-in-memory/

Wednesday, 23 June 2010

24 Hours of PASS

On the 19th/20th May (last month) the Professional Association of SQL Server (PASS) held its second 24 hours of PASS event . '24 hours of PASS' consists of 24 individual hour long meetings/presentations/training session all with a SQL Server 2008 R2 theme, held online and delivered by some of the most respectable names in the SQL Server community. This is a great event well worth looking into and attending.

I was on holiday at the time so wasn't able to attend any of the events 'Live' so to speak and even if I had been able to 24 hour long sessions over the course of 1 day or 24 hours period would be too much. I need my beauty sleep. So to allow people to catch up on what they missed PASS kindly record these sessions and make them available online to watch at your convenience. Obviously you lose the ability to ask questions and interact with the presenter but it is a great opportunity to catch up on anything you missed.

You can find the sessions here:

http://www.sqlpass.org/LearningCenter/24Hours.aspx

You need to register to view them, registration is free and well worth it.

Tuesday, 22 June 2010

Windows 2008 R2 Install Error - Using VMWare Workstation

Recently I was installing Windows Server 2008 R2 Enterprise Edition onto a virtual machine (VM) I was setting up to carry out some testing when I encountered the following error:

"The unattended answer file contains an invalid product key. Either remove the invalid key or provide a valid product key in the unattended answer file to proceed with the Windows Installation."

The error box is below:

 

Windows2008Error

The VM was hosted on VMWare Workstation.

I know I had a valid key, it was a key from my MSDN subscription. After a short trawl on the internet I found a few forum posts with people encountering similar issues.

The one I used can be found below:

http://communities.vmware.com/thread/244248

From what was said in a few of these threads It seems that when setting up the VM using VMware Workstation but before I began the OS installation I had entered the Windows 2008 R2 product key as part of the VM setup wizard. VMWARE or Windows didn't like this and the forum post suggested I remove the product key.

OK no big deal, So how do I do that?

I looked at the VM settings in VMware Workstation but I could not see where the Product Key was stored and I could see no easy way to remove it. So I had to take some drastic action and delete the VM altogether recreate from scratch without entering the product in the VM setup wizard(see screen shot below).

ProductKey

You are warned that you may get prompted for the product key at a later time. Click <OK> or <Next> complete the wizard and the Windows Server 2008 R2 installation starts successfully.

Deleting the VM and re-creating it was no big deal for me but worth remembering for next time so I don't waste 10 minutes setting the VM before having to drop and re-create without entering the product key, unless somebody out there has a better way of removing the product key?

Monday, 21 June 2010

Football Update

Well the World Cup is now half way through, 32 games played, 32 games to go. The talk here in the UK has focused around England their poor start. Two games played, one goal scored, one goal conceded, two draws, no wins, no losses, and they seem to lurch from crisis to crisis.

Starting with the goalkeeper and his now infamous error, moving onto what can only be described as a very poor display against, one of the weakest, on paper anyhow, teams in the competition in Algeria and now ex-captain John Terry being publicly critical of ‘Don’ Fabio and the ‘Don’ calling this his ‘Big Mistake.’ The ‘Don’ stripped Terry of the captaincy earlier this year for Terry’s off the field antics with his best friend and England Team mates girl friend. As a direct result of this Wayne Bridge is taking no part in the World Cup and retired from International football. From a semi independent point of view it looks like Terry is determined to leave his mark on this competition one way or another.

So we look forward to England last game of the qualifying group. What is a must win game for England if they are to progress to the last 16 and between now and Wednesday they need to curb their infighting, pull together and the best out of a ‘Golden Generation’. Which I personally find a strange tag as this side has never achieved anything of significance on the international stage. There are some ‘World Class’ players in this England Squad in the form of Rooney (who in my opinion is choking under the pressure to perform) Gerrard, Lampard and even Terry. They don’t seem to be able to find the class they show for their respective clubs when playing in the same team for England. They need to work out how to do that pretty quickly if they are going to progress and sustain it if they have real aspirations of winning the competition.

(Excuse the non-sql related blog post I needed to post something so Technorati could verify my blog so that explains the code below.)

68WRKGMVPMD6

SQL Server MasterClass

This Thursday gone, (June 18th) I went to a hotel near Heathrow airport in London for what was titled a “SQL Server MasterClass” and I was not disappointed.

I have attended several taught MCP SQL Server training courses over the years and several conferences including SQL Bits and this MasterClass taken Paul Randal and Kimberly L Tripp has to be the best training/knowledge transfer day I have been on. Kimberly and Paul have an amazing knowledge of SQL Server and such a great presentation style that makes this day a must for any SQL Server professional.

The agenda looked something like this:

1. KEYNOTE Bridging the gap between Developers and DBAs – The crux of this was that Developers need to write code that scales to a high volume production environment, thus helping out the DBA and DBA’s need to be flexible and help Developers with training and advice. The key to achieving the utopia was communication and team work and this set the tone for the rest of the day.

2. This took us onto a “SQL Server Mythbusters” session. This session was based around a series of blog posts @PaulRandal (Blog) wrote in April 2010 where he gave an insight and cleared up many myths around SQL Server. If you follow the link to Paul’s blog you can read much of the subjects covered on the MasterClass. You can’t beat hearing this stuff explained to you ‘straight from the horses’ mouth’ so to speak, but it is well worth reading if you were not able to attend.

3. Partner Presentations – This session was held by two of the third party sponsors, Idera and BakBone, where they demonstrated two excellent third party tools that could be useful in managing your SQL Server environments

4.The first session after lunch was titled a ‘Database Recovery Techniques - Demo Fest’ and it lived up to its name, Paul and Kimberly, amongst other things showed how,if you really really need to can access the systems tables in 2005 and 2008 and how  to simulate a disk failure and how to recover from it.

5. Kimberly took the fifth session and it was all about GUIDs:Use Abuse and how to move forward. This was an excellent session that provided some excellent information.

6. The final session titled “Essential Database Maintenance” was a joint session that counted down a top 10 of essential maintenance tasks. The guys said they could talk for a week on this subject so condensing this information into an hour session must have been impossible.

This is must attend event for any SQL Server professional. It was a fantastic day that I’m really pleased I was a able to attend and I would recommend it to anybody working with SQL Server.

Friday, 18 June 2010

Finding Duplicates

This is just a short post that uses a contrived example to demonstrate how to find duplicate records in a table. I needed to identify some duplicate records for a supplier recently and I wanted to make some notes on what I did for future reference.


 

First I will create a very simple table for this example


 

CREATE
TABLE [dbo].[Dups]


(

[FirstName] [nvarchar](50)
NULL,

[lastName] [nvarchar](50)
NULL,

[Company] [nvarchar](50)
NULL


)

ON [PRIMARY]


 

I will then add some example data, including some duplicate rows:


 

INSERT
INTO [C_AVG].[dbo].[Dups]


(

[FirstName],

[lastName],

[Company]


)

VALUES (


'Gethyn',


'Ellis',


'GRE'


)


 


 

INSERT
INTO [C_AVG].[dbo].[Dups]


(

[FirstName],

[lastName],

[Company]


)

VALUES (


'Lisa',


'Ellis',


'GRE'


)


 

INSERT
INTO [C_AVG].[dbo].[Dups]


(

[FirstName],

[lastName],

[Company]


)

VALUES (


'Ron',


'Ellis',


'GRE'


)


 

INSERT
INTO [C_AVG].[dbo].[Dups]


(

[FirstName],

[lastName],

[Company]


)

VALUES (


'Lisa',


'Ellis',


'GRE'


)


 

INSERT
INTO [C_AVG].[dbo].[Dups]


(

[FirstName],

[lastName],

[Company]


)

VALUES (


'Lisa',


'Ellis',


'GRE'


)


 


 

When I run a very simple select against this table I get the following output:


 

Gethyn    Ellis    GRE

Lisa        Ellis    GRE

Ron        Ellis    GRE

Lisa        Ellis    GRE


 

as we can see, Lisa is included in this table twice this but if you had a table with a couple million rows in this table and you suspected that it had duplicates spotting the duplicates maybe a little more difficult the following script will identify them for you:


 

This shows that


 

SELECT FirstName, lastName, Company FROM dups

GROUP
BY FirstName, lastName, Company

HAVING (COUNT
(*)
> 1)


 

This returns all the duplicate entries:


 

Lisa    Ellis    GRE


 

This only identifies the rows that exist more than once, cleaning up duplicates through deletion will be covered in another post.


 

Friday, 11 June 2010

The Football World Cup

WorldCup This day only comes around once in every four years, we've all been waiting for it for months. It's been in the news and media, there has been a great deal written about qualification, preparation and selection and now with all that done and dusted its finally arrived...The start of the Football World Cup.

For my American friends, this is probably better known as the soccer world cup, but to me football is football and this is the football world cup.

For the next four weeks, day in day out the best players in the world will represent their countries and someone will become world champions. Italy won it last time in 2006. Spain and Brazil (as always) are the bookies favourites this time. This year it's being held in South Africa. This means that the majority of the games will be shown on TV when I'm home from work. I think there is only 1 hour difference in time, with South Africa being on GMT +2 and the UK being on British Summer Time (BST) which is GMT+1.

My team Wales, yet again, failed to qualify. They never qualify. Well that's not strictly true they did qualify back in 1958, they were knocked out in the quarter final stage by Brazil. Pele at 17 years old scored the only goal of the game and Brazil won 1-0. That was 22 years before I was born and my Dad was no more than a toddler himself.

Anyway I have entered a couple of sweep stakes 5 in total! I haven't had much luck with the teams I have drawn...The pick of my team are the USA, who although very good, I don't think will win and defending champions Italy...I can't remember the last time someone defended the trophy.

So what's this got to do with my SQL Server blog? In reality not a great deal, except my spare time, the time which I may have spent blogging, is likely to be taken up watching football on TV. It's definitely my favourite sporting occasion and I am very excited.

Wednesday, 9 June 2010

SSMS 2008 and changing a SQL 2005 SA password.

You can probably tell from some of my more recent posts that I have been doing some work lately on SQL Server 2008. I have also recently (the last two months) upgraded my work desktop to Windows 7. As a result of this of this, and the continued migration away from SQL Server 2000 I have only installed the SQL Server 2008 client tools (Management Studio) onto my desktop and I use that for working on both SQL Server 2005 and SQL Server 2008 instances.

This week, for reasons beyond the scope of this post I wanted and needed to change the sa password on one of my SQL Server 2005 instances. No problem I thought, I already had SSMS 2008 open on my desktop. I connected to the SQL Server 2005 instance using Windows Authentication. (The SA account is not generally used) I opened the security folder, and then the logins folder, right-clicked on the sa login and selected properties. The properties box opened, I typed a new 'password' into the 'password and confirm password' dialogue box and clicked <OK>. To my shock and horror I got the following error:

Cannot set a credential for principal 'sa'. (Microsoft SQL Server, Error: 15535)

Well that surprised me, if it didn't surprise you. I tried to login using the old SA password and it logged in fine. I then realised that it must be related to changing the sa password of a SQL Server 2005 instance using SSMS 2008.

Well I cheated and remote connected to the server hosting the 2005 instance, and used the SSMS 2005 installed on there. I needed to change the password quickly but I wanted to figure out what had prevented me changing the password in SSMS 2008.

Returning to my test domain later in the day, I was able to recreate the problem again, simply by trying to change the sa password of a 2005 instance using SQL Server 2008 Management Studio. I went to search the web and found this:

http://support.microsoft.com/kb/956177

The solution is very simple, the "map to credentials" check box in the properties Window is not selected. The above article explains why this is the case. Tick the box and change the password and all is well.

Tuesday, 8 June 2010

T-SQL Tuesday #007 - Policy Based Management

It's that time of the month again, time for the next round of T-SQL Tuesday posts. This month is being hosted by Jorge Segarra (Blog | Twitter) and we are blogging about new features in SQL Server 2008 and SQL Server 2008 R2. Plenty of scope then as this is quite a wide topic. I have posted previously on file streaming, you can see those posts here but for this post I am going to keep it simple and fresh and look at another new feature of SQL Server 2008, Policy Based Management.
I have been meaning to write something on policy based management for some time. Policy Based Management allows DBAs and administrators to apply policies or enforce rules on all the SQL Server 2008 instances they look after and ensure that a consistent approach is followed on all instances. It can be used by DBAs to enforce a 'standard' configuration across the SQL Server farm.

Where would you use it?

Well, firstly only on SQL Server 2008 and beyond. It won't work on 2005 or 2000.
There are numerous uses, one that I would have used in a previous job had it been available in earlier versions would have been to enforce some sort of naming convention. For example, you want developers to stick to some sort of naming convention, you may want the name of all stored procedures to start 'USP_' which makes identifying developer written stored procedures very easy and straight forward. Naming conventions is big long argument possibly for another day and I don't want to go into a big long discussion about this here, so let's assume you have brand new SQL Server 2008 Server, it's going to be a development instance, and you want to make sure that your developers stick to a naming convention for Stored Procedures so how do you use policy based management to achieve this?
Taken from Book Online (BOL):
Policies are created and managed by using Management Studio. The process includes the following steps:
1. Select a Policy-Based Management facet that contains the properties to be configured.
2. Define a condition that specifies the state of a management facet.
3. Define a policy that contains the condition, additional conditions that filter the target sets, and the evaluation mode.
4. Check whether an instance of SQL Server is in compliance with the policy.

How do we do this ourselves?

Connect to your SQL Server instance
Expand the management folder
and expand the policy management folder...and you will see three further sub folders: polices, conditions, and facets.
Im1
Expand the facet folder and look for a facet called “Stored Procedure”. Right click and select <properties>. You should see a list of properties, we will be using the 'name' property. You can then close this window.
Right click the Stored Procedure facet and select <new condition> give it a meaningful name..."SPName"
The Stored Procedure Facet should be selected.
In the expressions box click to add a clause.
Enter the following information:
Field: @Name
Operator: LIKE
Value: 'USP_%'
After entering this information this your condition should be ready. Click <OK>
DefaultTraceNotEnabled
Using the stored procedure facet we have created a condition for the Name property which specifies that stored procedure names should start with 'USP_' we now need to create a policy to enforce this condition.
Right Click the <Policies> folder and select <New policy> and we get the Create New Policy window
Give your policy a meaningful name "SPName"
Select the check condition we just created.
Specify the target databases you want enforce the policy on.
Specify the Evaluation Mode. For this we want the policy to prevent Stored Procedures so we select "On Change: Prevent"
Click on the "Description Page" on the left hand side and enter some text in the "test to display" window something like "Sorry guys, you know the rules, nice names for the SPs please."
Click OK. This creates your policy. BUT you are not done there. If you go and try and create an SP that does not follow this policy do you think SQL Server will allow you? Well yes it will, the new policy is currently in a disabled state. I think this is like this because they want you to evaluate your policy before you enable them and you can right-click and run evaluate which shows you current objects which break this policy.
So I will enable the policy by right clicking and selecting <Properties> and the ticking the <Enabled> check box.
go away and a developer tries to create an SP called '[SELECT]' and he gets this
ErrorMessage
When we change the name to ‘usp_select’ it works just fine.
That just about wraps up my TSQL Tuesday post for this month, my good friend Justin Hostettler-Davies has recently been writing a series all about the new features of SQL Server 2008. You can find his blog and his posts here.

Monday, 7 June 2010

Cannot Connect to SQL Server

I recently installed a new SQL Server 2008 instance on a brand new Windows 2008 R2. When I tried to connect to said instance using Management studio on my desktop i received the following error message:

"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)"

An initial google search on the error returned a whole bunch of information on SQL Server 2005 and enabling remote connections. Well you don't need to 'enable remote connections' as such in SQL Server 2008 but I did check that the TCP/IP protocol had been enabled in configuration manager.

I then found a useful SQL Server 2008 post which can be found here http://msdn.microsoft.com/en-us/library/bb326282.aspx . This suggested that the problem was related to the Firewall blocking remote connection. I got followed the advice and got the firewall reconfigured and I was able to connect.

Friday, 4 June 2010

SQL Server 2008 Installation Fails to Start

Recently I have been installing a new SQL Server 2008 instance on Vmware vSphere based  virtual server, the OS was Windows 2008 R2. I have done this several times before and I don't recall ever getting this issue. Seeing as it took me a short while to figure out what was going on I decided to make some notes about it here.

I attached the SQL Server 2008 iso to the VM, auto-run failed to kick in so off I went to the CD/DVD drive to start the setup manually. First up, it warned me that I needed to update Windows installer and the .Net framework to 3.5. I clicked OK to do this and it ran successfully and then the server prompted me to reboot.

When the server had restarted I ran the setup again but this time nothing happened, no error, no start screen, nothing. I did this a few times again, I rebooted again, not sure why I rebooted, more out of habit than necessity and just to make sure.

I tried setup again, same thing.

Off I went to the event viewer and I found an Error in the log that  looked something like this:

"The Windows update  could not be installed because of an error: 2149842974 "" (Command line: ""C:\Windows\system32\wusa.exe" "D:\x64\redist\Windows Installer\x64\INSTMSI45.MSU" /norestart")"

A quick google search did not return anything obvious to my situation. I even posted a question on a couple of forums.

Anyway I decided to try and get a more meaningful error and I ran the above command from a command prompt. I did in fact get a new error that said there was not enough space available on the drive, or something similar. This was a strange error because the only drive without space available was the d:\ drive...The CD/DVD drive.

Anyway I copied the contents of the DVD drive, the SQL Server 2008 setup files to a local drive on the server, with plenty of space. I then ran the setup again using the files on the local drive. This time I got the setup screen and was able to perform my installation.

Thursday, 3 June 2010

Weekly Update - Internet Issues

I haven’t written anything technical or SQL Server related for that matter on my blog for a few of weeks. Mainly because I spent a couple of  weeks in Florida celebrating my birthday. I did take my laptop on my holidays mainly because we booked everything flight, car, hotel etc online and I thought it would useful to have at hand if I needed it in an emergency. It is also useful to call home, SKYPE’s international rates are pennies and when you compare that to my mobile phone companies rates they are a bargain. The hotel in Orlando threw in free WiFi which was great.

A few days into the holiday I had a few issues trying to connect to the hotel’s wireless provider  and after some troubleshooting with the aid of the helpdesk I got connected.  I did have to uninstall my UK mobile internet provider software to be able to connect, which at the time I thought nothing about as I had all the software safely tucked away at home. Until I return home and try reinstall and the software and I get continuous errors on the setup. At the time of writing I have still not got to the bottom of the problem, granted I have not tried very hard but still!  I use the mobile broadband mainly for work I spend a lot of time out on site with clients and it comes in handy for checking mail and doing a little research. Its no big deal to me not to have it. I can pick mail on my iPhone etc but it is a just a PITA that it is not working.

I haven’t got the mobile internet fixed because I have a few things to do around the home since I got back from holiday. The garden in particular needed some attention, the grass needed cutting, fences need painting, and as the weather has been nice since we got back  to and where I live you need to make the most of the summer weather! I also have two one year old Golden Retriever dogs that missed us greatly while we were away and have been in need of lots of attention too since I have got back. I’m sure it will start raining again soon and that will give me plenty of time to get the mobile internet fixed.

I hope to get my next blog entry out for the next the T-SQL Tuesday event which all about the new features of SQL Server 2008 and SQL Server 2008 R2. Which is quite a wide subject I think you will agree. This event takes place on Tuesday 8th June and is being hosted this month by Jorge Segarre (Blog|@SQLChicken) and you can find all the details about this event on @SQLChicken’s blog.

It actually coincides quite nicely with a series of blog posts a friend of mine, Justin Hostettler-Davies, has been writing over on his blog. His series is titled “A SQL Server 2008 Feature a Day”, You can find his blog posts here.  Hopefully between now and next Tuesday I can take the opportunity to take one the new features and write a detailed blog post on one of them.

Anyway, hopefully this post has dusted off my blog and get me back into the writing groove.

Wednesday, 2 June 2010

Test Post

Test Post - This will be deleted