Microsoft SQL Server 2008 R2 Team Blog & Forums
Microsoft SQL Server 2008 R2 Team Blog & Forums
(needless to say - if it goes perfectly - you are darn lucky!)
Amazing: After all that trouble and installing all components with SQL Express Advance Edition, Management Studio, Advanced Tools. Voila! I can simply double click the script and it opens in the SQLQuery Debugger.
The first step from here is to establish whether the sql script has any issues (problems) simple things such as path defined for pointing to a SQL database could be incorrect.
for example: My Data path points to E:\MSSQL\DATA
but my script points to c:\Program Files\MS SQL\DATA or something like that - which simple has to be changed.
Also my database is located in the data path that I defined. - instead of the one supplied. (but that's another lesson in scripting).
to be continued....
Interesting on how I ended up on this site today of all days.
The first thing is a memory - a very distant memory. Where I had previously worked with SQL 2000 as a DBA more than 4 years ago. I quite this line and became a Security Systems Specialist. This essentially meant I never get to see a SQL console again anytime soon. Alas, it has come beckoning on my doorstep. Partly because this is in my CV as one of the technologies I intimately understand.
As I stand - none of it seems true.
The first question that popped in my mind after a collegue sent some SQL script files to run, was where do I go? How do I do that again? more than 8 hours later, I'm about to answer that question.
Here are the basic steps to get me going:
1. Find a server on the domain I can use to install MS-SQL Express 2008 (note I found out the hard way that I needed the Advanced Edition with reporting installed).
> don't forget to check your pre-requisites i.e dotnet 3.5 at least; Windows Installer 4.2 (if you are running Windows 2003)
2. Download and install MSQ SQL 2008 Management Studio (another lesson in why you should always revist technologies you've worked with before).
> Server Configuration checker also comes in handy - it is included with SQL 2008!
Now that the basics are out the way, we can proceed with what got me stuck in the first place - .sql script files!
After installing all the required components, and several reboots. The server is ready for use with Microsoft SQL 2008 R2.
(needless to say - if it goes perfectly - you are darn lucky!)
Amazing: After all that trouble and installing all components with SQL Express Advance Edition, Management Studio, Advanced Tools. Voila! I can simply double click the script and it opens in the SQLQuery Debugger.
The first step from here is to establish whether the sql script has any issues (problems) simple things such as path defined for pointing to a SQL database could be incorrect.
for example: My Data path points to E:\MSSQL\DATA
but my script points to c:\Program Files\MS SQL\DATA or something like that - which simple has to be changed.
Also my database is located in the data path that I defined. - instead of the one supplied. (but that's another lesson in scripting).
to be continued....
Comments
Post a Comment