Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. SQL Server Setup. Sign in to vote. Thanks for your help Thursday, December 27, PM.
You need to have Sql SP2 to run in Vista it is a prerequisite. If you have installed 32 bit of sql download X86 else for 64 bit of sql download x64, if you have Itanium processor go for IA For these programmers, Microsoft's delay won't make much of a difference. But for many companies with MSDE-based applications - mostly small enterprises without a large IT staff to manage system upgrades - headaches loom.
Once Microsoft rolls out a Vista-compatible version of that software, they'll need to upgrade and test all over again. They can download the test version of SQL Server and start preparing their database applications for an upgrade, says Chris Alliegro, an analyst at Directions on Microsoft.
But even that step won't be easy. Before company programmers start testing SQL's beta, they'll have to identify all of the database applications they're running that rely on MSDE. For companies that have acquired other businesses, reorganized divisions, or outsourced IT personnel, that's a mighty tall order. And here's the rub: Until Microsoft releases a Vista-compatible version of SQL Server , all that testing will be for naught, since they won't be able to install it on users' desktops.
So good luck trying to get approval from your company's budget cops. And you don't know when you'll be able to run it? With database software for small and medium-sized businesses the fastest-growing segment of the market, Microsoft may well be alienating the sector it can least afford to lose in its campaign to boost database sales.
The key word here is "eventually. Now, they're discovering that they still have to wait for a database component that works with it. No wonder Google Charts is beating Microsoft in other arenas: This is a company that has forgotten how to execute its own playbook of launching a coordinated wave of products that all work together.
No doubt Microsoft will get this straightened out - eventually. By then, it just might be time to launch another version of Windows. By Owen Thomas , Business 2. I'm using Vista Business with Sql Dev. Were you able to install Reporting Services?
I thought you had a similar problem in an earlier thread, did you figure it out? Vista is really frustrating. I did have a thread earlier. Before I bought this new computer, I tried to research as thoroughly as possible all of the hardware and software requirements. Unfortunately, I did the unforgivable and made an assumption: I mentally added "or higher" when it said it works with Windows XP, , etc.
I am somewhat new to forums, so please forgive me if I don't know all of the protocol. I am also having to learn how to use this editor. Anyway, to make a long story short, it turns out that the only version of Vista that supports the installation of SS2K5 including Reporting Services is Vista Ultimate.
What little information I have been able to find about the need for Ultimate leads me to believe that it has something to do with support for Windows Authentication.
Apparently, Vista has some new kind of security features that make it work completely differently from previous Windows Systems, and the SS development team hasn't quite caught up yet. I appreciate all of the comments and suggestions from everyone, but as far as I can tell so far, nothing works the same in Vista. Marty, you said "Anyway, to make a long story short, it turns out that the only version of Vista that supports the installation of SS2K5 including Reporting Services is Vista Ultimate.
I found that there are actually three versions that do work: Business, Enterprise, and Ultimate. But you are correct that Ultimate is the only version that a home user would be likely to purchase. At the end of installing Service Pack 2 on Vista, there is a "provisioning tool" that runs which will allow you to grant yourself SQL admin rights. If you do not run that tool, you still won't be able to connect to SQL Server even if you are a Windows admin and the installation is "successful".
If you skipped running that tool, you can grant yourself permission using the Surface Area Configuration tool:. That's where you can give yourself permission to connect and administer. When the install finished, I went to get the SP2. One of the options was to "install in an automated manner".
This turns out to be Windows Update. So I went ahead and told it to download and install all the updates it said I needed. That version of the update apparently does not present the "Provisioning Tool" -- or at least I never saw it. When I finished re-installing last night and went to install the Service Pack, I decided to download and save the patch file so that I would have it handy in case I needed to apply it again.
At the end of the update, the provisioning tool came up and I granted myself rights. However, shortly after that, I received the following two error messages:. An error has occurred while establishing a connection to the server. When connecting to SQL Server , this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
0コメント