Help Me Adapt to Microsoft SQL Server 2005.
February 12, 2009 8:08 AM Subscribe
Help me adapt to Microsoft SQL Server 2005.
Bear with me, this will seem a little chatfiltery because I'm just dumbfounded at this point.
I started with SQL Server 6.0, found it painful. Liked 6.5 better, but it was still clunky. But versions 7.0 and 2000? I love them bunches. I could just use them without fuss by opening up the management console and getting down to it. Everything was intuitive.
Then SQL Server 2005 comes along and I feel like the county cropduster who just got dropped into the cockpit of an F-14 and wishes desperately for his old prop plane back. Suddenly, I don't know where anything is. Visual Studio appears. Diagrams abound, and I'm flailing around looking to see where they've hidden basic Transact-SQL commands buried in masses of machine-generated XML. I'm digging in obscure directories to find the DTS Wizard. "Product level is insufficient" happens a lot. Copying a database, once a task I had relegated to muscle memory, just isn't happening. I avoid logging into servers via RDP, but there I am, giving it a shot because the desktop version doesn't seem to quite have everything in it.
More and more, I find myself just issuing basic SQL commands from the nearest programming language rather than interact with this enormous GUI, which has been integrated with who knows what. I know they're trying to compete with Oracle, but I'm at a loss as to how I can do some previously simple tasks, like hauling in Excel spreadsheets that get handed to me, without having to write code to do it.
Is SQL Server 2005 just like that? Or is it me?
Are there books about how to use it for the basic, dumb tasks? I don't need to worry about partitioning or some of these other very high-end tasks.
Do I really have to get a Server/Developer license just to export stuff to a frikkin' text file if I don't want to log into the server to do it? Because that just seems insane.
Has someone hacked up a free alternate interface to it, or is there a secret one that Microsoft has out there?
Is SQL Server 2008 more of the same? Even worse?
I know, someone will invariably suggest mySQL, postGreSQL, etc. Yes, I've heard of them. No, that won't be happening during my day job.
Bear with me, this will seem a little chatfiltery because I'm just dumbfounded at this point.
I started with SQL Server 6.0, found it painful. Liked 6.5 better, but it was still clunky. But versions 7.0 and 2000? I love them bunches. I could just use them without fuss by opening up the management console and getting down to it. Everything was intuitive.
Then SQL Server 2005 comes along and I feel like the county cropduster who just got dropped into the cockpit of an F-14 and wishes desperately for his old prop plane back. Suddenly, I don't know where anything is. Visual Studio appears. Diagrams abound, and I'm flailing around looking to see where they've hidden basic Transact-SQL commands buried in masses of machine-generated XML. I'm digging in obscure directories to find the DTS Wizard. "Product level is insufficient" happens a lot. Copying a database, once a task I had relegated to muscle memory, just isn't happening. I avoid logging into servers via RDP, but there I am, giving it a shot because the desktop version doesn't seem to quite have everything in it.
More and more, I find myself just issuing basic SQL commands from the nearest programming language rather than interact with this enormous GUI, which has been integrated with who knows what. I know they're trying to compete with Oracle, but I'm at a loss as to how I can do some previously simple tasks, like hauling in Excel spreadsheets that get handed to me, without having to write code to do it.
Is SQL Server 2005 just like that? Or is it me?
Are there books about how to use it for the basic, dumb tasks? I don't need to worry about partitioning or some of these other very high-end tasks.
Do I really have to get a Server/Developer license just to export stuff to a frikkin' text file if I don't want to log into the server to do it? Because that just seems insane.
Has someone hacked up a free alternate interface to it, or is there a secret one that Microsoft has out there?
Is SQL Server 2008 more of the same? Even worse?
I know, someone will invariably suggest mySQL, postGreSQL, etc. Yes, I've heard of them. No, that won't be happening during my day job.
"More and more, I find myself just issuing basic SQL commands from the nearest programming language rather than interact with this enormous GUI,"
Good, you'll learn more. SQuirrel SQL is nice cross-RDBMS GUI with some metadata (listing all objects, generating some queries) and a clean, useful query interface (multi-line query up top, results below).
Point SQuirrel at your database.
posted by orthogonality at 8:21 AM on February 12, 2009
Good, you'll learn more. SQuirrel SQL is nice cross-RDBMS GUI with some metadata (listing all objects, generating some queries) and a clean, useful query interface (multi-line query up top, results below).
Point SQuirrel at your database.
posted by orthogonality at 8:21 AM on February 12, 2009
So which license do you have? Am I right in assuming that you didn't pay for SQL and are just using whatever came with SQL Express/VS Express Free Version? SQL Express has 80% of the feature set of Workgroup and Standard, but the client tools aren't included.
In that case, as the mechanic says "now *there's* your problem..."
Download the trial version of SQL 2005 or SQL 2008 and install just the tools. If memory serves, the server engine is only good for 180 days but the tools don't expire.
Of course, if you have an actual licensed copy of SQL, all the better. We have an MSDN license for dev work but do a lot of work with Express on desktops. Still, we install the developer tools off the enterprise install disk on all workstations because they are so much better than the tools that bundle with Express.
posted by brian60640 at 8:44 AM on February 12, 2009
In that case, as the mechanic says "now *there's* your problem..."
Download the trial version of SQL 2005 or SQL 2008 and install just the tools. If memory serves, the server engine is only good for 180 days but the tools don't expire.
Of course, if you have an actual licensed copy of SQL, all the better. We have an MSDN license for dev work but do a lot of work with Express on desktops. Still, we install the developer tools off the enterprise install disk on all workstations because they are so much better than the tools that bundle with Express.
posted by brian60640 at 8:44 AM on February 12, 2009
seconding it is the tools. make sure you are using the same release of sql management studio as you are sql server. i have run into problems using sql management express with none express editions of server.
posted by phil at 8:45 AM on February 12, 2009
posted by phil at 8:45 AM on February 12, 2009
Response by poster: Well, we have a license for the SQL Server (two, since they're clustered). I've got the SQL 2005 Management Studio installed from the same set of directories (we don't get discs, due to volume licensing).
It's just that I occasionally receive bits like "Hey, can you dump that database to a text file to us in case we ever need it?" and exporting data to a text file means you need SSIS installed ("product level is insufficient ..."). Which means something beyond the simple management studio. Which means that I'm looking at license issues again. And lots of money ... for a text file.
Now, obviously, I will log onto the server to do this, or I could write some code, and either one is not hard, but this used to be something I could do with my eyes shut in SQL 2000 from the MMC based Enterprise Manager. This makes no sense to me, aside from a purely "hey, we can make more money this way" fashion. Yes, workarounds exist, but I'm so flabbergasted that it becomes a maddening itch that says this should not be that hard, so you are an idiot and are missing something obvious. That in turn implies that I have not grokked SQL 2005 at some fundamental level, which has the further implication that I am not up to snuff in this portion of my job. Hence, I need to adapt or set something on fire to vent my primal rage.
posted by adipocere at 8:59 AM on February 12, 2009
It's just that I occasionally receive bits like "Hey, can you dump that database to a text file to us in case we ever need it?" and exporting data to a text file means you need SSIS installed ("product level is insufficient ..."). Which means something beyond the simple management studio. Which means that I'm looking at license issues again. And lots of money ... for a text file.
Now, obviously, I will log onto the server to do this, or I could write some code, and either one is not hard, but this used to be something I could do with my eyes shut in SQL 2000 from the MMC based Enterprise Manager. This makes no sense to me, aside from a purely "hey, we can make more money this way" fashion. Yes, workarounds exist, but I'm so flabbergasted that it becomes a maddening itch that says this should not be that hard, so you are an idiot and are missing something obvious. That in turn implies that I have not grokked SQL 2005 at some fundamental level, which has the further implication that I am not up to snuff in this portion of my job. Hence, I need to adapt or set something on fire to vent my primal rage.
posted by adipocere at 8:59 AM on February 12, 2009
From here, SSIS should be included with Standard and Enterprise versions of SQL Server 2005. What version are you licensed for?
posted by deezil at 9:58 AM on February 12, 2009
posted by deezil at 9:58 AM on February 12, 2009
Response by poster: Deezil: It comes with SQL Server 2005, yes indeedy. Which we have. It clusters and everything.
The problem is that I don't want to install SQL Server 2005 on my desktop. Desktop means another license, ka-ching!. Which means a few grand, all so I can dump out a text file. This is the kind of problem I'm talking about, indicative of the whole mess that is 2005. It shouldn't be that hard, so either I'm missing something critical or Microsoft has.
posted by adipocere at 10:20 AM on February 12, 2009
The problem is that I don't want to install SQL Server 2005 on my desktop. Desktop means another license, ka-ching!. Which means a few grand, all so I can dump out a text file. This is the kind of problem I'm talking about, indicative of the whole mess that is 2005. It shouldn't be that hard, so either I'm missing something critical or Microsoft has.
posted by adipocere at 10:20 AM on February 12, 2009
Sounds like you grok SQL 2005 pretty well to me. I've been feeling your pain for a while now trying to develop SSIS packages and while it's very powerful, it's also overwhelming especially without training. The product level is insufficient does mean that you need SSIS installed on your machine to run the task. Here's a couple ways around that:
Next time you remote desktop into the server to export a table, save the SSIS package to the file system.
Option 1 - run package in visual studio:
- Copy .dtsx file to your workstation
- Start visual studio on your workstation
- File menu -> new project -> business intelligence project -> integration services project
- Project menu -> Add existing item (or in solution explorer right click on SSIS packages)
- Double click on package in solution explorer
- In connection manager window (usually at bottom of screen), right click on destination connection and select properties to set the file path to one accessible by your workstaion
- Debug menu -> start debugging (or click green arrow in toolbar)
Option 2 - run package in SQL Server agent:
- Start SQL Management Studio on the server (you need to create the job on the server, but can run it from the management studio on your workstation)
- Expand the server, expand SQL Server Agent
- Right click on Jobs, select New Job
- Follow steps here to create a new job, with these specifics:
- In step 6, select type as SQL Server Integration Services Package
- In step 8, select the package source as file system, and browse to the .dtsx file. On the Data Sources tab, verify the destination file
Option 2 is probably the better bet, since anyone connecting to the server via Management Studio can run the job, but if you want to get into customizing the SSIS package, then Option 1 is the ticket.
posted by hoppytoad at 10:58 AM on February 12, 2009
Next time you remote desktop into the server to export a table, save the SSIS package to the file system.
Option 1 - run package in visual studio:
- Copy .dtsx file to your workstation
- Start visual studio on your workstation
- File menu -> new project -> business intelligence project -> integration services project
- Project menu -> Add existing item (or in solution explorer right click on SSIS packages)
- Double click on package in solution explorer
- In connection manager window (usually at bottom of screen), right click on destination connection and select properties to set the file path to one accessible by your workstaion
- Debug menu -> start debugging (or click green arrow in toolbar)
Option 2 - run package in SQL Server agent:
- Start SQL Management Studio on the server (you need to create the job on the server, but can run it from the management studio on your workstation)
- Expand the server, expand SQL Server Agent
- Right click on Jobs, select New Job
- Follow steps here to create a new job, with these specifics:
- In step 6, select type as SQL Server Integration Services Package
- In step 8, select the package source as file system, and browse to the .dtsx file. On the Data Sources tab, verify the destination file
Option 2 is probably the better bet, since anyone connecting to the server via Management Studio can run the job, but if you want to get into customizing the SSIS package, then Option 1 is the ticket.
posted by hoppytoad at 10:58 AM on February 12, 2009
You have to log onto the box itself in order to use the Import/Export utilities. Yeah, it's a little annoying .
posted by spatula at 11:28 AM on February 12, 2009
posted by spatula at 11:28 AM on February 12, 2009
odinsdream: Is it anything like the installation for 2000? To install the client tools you actually start up the Server installation and you have the option to only install the client tools, not the entire server. Perhaps this technically requires another license, but I don't think so.
This is what I think I was getting to eventually with my question. I can install the tools on any machine I want here at work, and work with the central SQL server without paying for a license on my workstation, because the license is for the engine. So you should be able to just install the tools with the setup.
posted by deezil at 12:42 PM on February 12, 2009
This is what I think I was getting to eventually with my question. I can install the tools on any machine I want here at work, and work with the central SQL server without paying for a license on my workstation, because the license is for the engine. So you should be able to just install the tools with the setup.
posted by deezil at 12:42 PM on February 12, 2009
« Older Let my hair grow back, help my get email to yahoo | Help me design a navigation interface for my... Newer »
This thread is closed to new comments.
Do you have the right client tools? The old Query Analyzer/Enterprise Manager dichotomy is gone, replaced by a single tool--SQL Server Management Studio.
There's more hierarchy in the left pane: system objects are now separate, and functions are divided by types, but it isn't all that different from EM. The TSQL windows work just like QA windows used to. Most keyboard shortcuts are the same.
posted by brian60640 at 8:13 AM on February 12, 2009