looking to generate a listing of all SQL Server instances, showing
machine name
default or instance name
type of component (Database Engine or SSRS or SSIS or SSAS)
is there a powershell script that does this, or will system center show all this?
If you need to find it on a server or workstation, you can pop in the SQL disk, wait for the install center to come up and select Tools > Installed SQL Server features discovery report.
To check your whole network, check out Microsoft MAP. Works for SQL 2008. It will check:
Windows 7
Windows Vista
Windows XP Professional
Office 2010 and previous versions
Windows Server 2008 or Windows Server 2008 R2
Windows Server 2003 or Windows Server 2003 R2
Windows 2000 Professional or Windows 2000 Server
VMware ESX
VMware ESXi
VMware Server
Linux variants
LAMP application stack discovery
SQL Server 2008
I'm not sure about 2005/2000 besides db instances. Those are easy to find with sqlcmd -L. You could use wmi queries on specific servers to match service names. I believe the sql active directory services may register the services in AD...but I don't think you can rely on that.
Related
I have installed a Evaluation 180 days version of SQL Server 2012 from the official website of Microsoft, on a Windows Server 2012 R2 (with gui). At the end of the installation in the Installation center, everything passed and succedeed but when I quit the program, I don't have any way to execute SQL Server from a graphical interface. I can see MS instances created, services running but how can I get a GUI to work with SQL Server?
With the newer version of SQL Servers, the SQL Server Management Studio (the GUI) is a separate install and you will need to install it separately to the database engine installation (which is what you have done). You can download SSMS from here https://www.microsoft.com/en-us/download/details.aspx?id=29062. The page contains a lot of different download components, make sure you check the appropriate install and click download.
ENU\x64\SQLManagementStudio_x64_ENU.exe if you want the 64bit installation of SQL Management Studio
ENU\x86\SQLManagementStudio_x86_ENU.exe for the 32bit version.
you Need to Install SSMS
SQL Server Management Studio (SSMS) is a tool to manage and administer SQL Server and SQL Database.
SSMS is offered free of charge by Microsoft.
I am poorly experienced in SQL Server installations. I have already installed 2008r2 on Microsoft Windows 8.
Now I want to install MS SQL Server 2005, but I need both MS SQL Server 2008r2 and MS SQL Server 2005.
How can I install this?
You can install both versions on same computer..
From MSDN:
SQL Server supports multiple instances of the Database Engine, Analysis Services, and Reporting Services on the same computer. You can also upgrade earlier versions of SQL Server, or install SQL Server on a computer where earlier SQL Server versions are already installed.
There's a couple of problems here; firstly SQL 2005 isn't even compatible with Windows 8. Windows 7 you can just about get away with it with some patching. Next you need to install the instances and tools in version order. So SQL 2005, then SQL 2008.
You could try uninstalling SQL2008, but you'll probably find too many updates and bits have occurred to get back to a state that might allow you to try doing SQL2005.
My recommendation would be; format the host machine. Install Windows 8. Setup HyperV virtual machines for each version of SQL Server in an operating system that's more inline with the SQL product. Eg. Win2003 for SQL2005. Win2008 for SQL 2008.
He's a block post of doing this to create a manageable developer workstation running every version of SQL Server: http://www.purplefrogsystems.com/paul/2016/05/using-hyper-v-and-powershell-to-create-the-perfect-developer-workstation/
Is there a compatibility problem that would prevent a program running under Windows XP from accessing a SQL Server 2012 Standard instance running on a Windows 2008 server on the same domain?
This might be a stupid question; I know that it is not possible to install SQL Server 2012 on XP, but I cannot think of a reason why it would not allow access by a program.
So this is merely a stab in the dark. For the moment I only wish to know whether there are any problems in principle; if there are none I will try to come up with a minimal error case for my particular setup and ask a separate question.
I just confirmed that an application written in VB6 using ADO with the "Microsoft OLEDB provider for SQL Server" can connect to a SQL Server 2012 database. The connection string looks like this:
Provider=SQLOLEDB.1;
Password=PasswordHere;
Persist Security Info=False;
User ID=SomeUserName;
Initial Catalog=SomeDatabase;
Data Source=SQL2012Instance
The operating system is Microsoft Windows XP Service Pack 3.
The operating system hosting the SQL database is Win-7.
The database engine is Microsoft SQL Server 2012 - 11.0.2100.60 (x64)
I want to install SharedManagementObjects for SQL server 2012 express on a windows xp sp3 machine that has SQL Server 2008 R2 Express edition but does not have any edition of SQL Server 2012.
But one of the prerequisites for installing "SharedManagementObjects for SQL server 2012" is that microsoft sql server 2012 system CLR types must be installed.
I see i can download the SQLSysClrTypes.msi i need from Microsoft® SQL Server® 2012 Feature Pack
but am not certain it will successfully install on a windows XP SP3 machine that has .NET 4.0 and Windows installer 4.5 but no SQL Server 2012.
EDIT:
Same problem as this http://social.msdn.microsoft.com/Forums/nl/sqlsmoanddmo/thread/6bcde08f-e848-40a0-bc1f-e2f803a125da
I want to do this because i have an application whose backend database can either be SQL Server 2008 R2(for clients running windows XP SP3) or SQL Sever 2012(for clients on Windows Vista and above).
This application uses SMO for doing programmatic backup and restore operations.
Now in my application when i reference SMO for SQL Server 2008 R2, backup and restore fails on systems that have SQL server 2012.
If in my application i reference SMO for SQL Server 2012, backup and restore fails on systems that have SQL server 2008 R2 (i.e XP3 clients).
What is the common best way of handling such a requirement? Or what alternatives do i have?
All i need is for the WinForms application to support both SQL Server 2008 R2 and SQL Server 2012 and their corresponding versions of SMO.
The System Requirements section on that download page is pretty clear:
System requirements
Supported operating systems: Windows 7, Windows
Server 2008 R2, Windows Server 2008 Service Pack 2, Windows Vista
Service Pack 2
There's no mention of Windows XP SP3 - so no, you cannot install this SMO library on Windows XP SP3. Time to upgrade.
I´ve an app that uses ReportViewer 2012. It needs SQLSysClrTypes 2012. I´ve tried to install it on XP but it says it needs .Net Framework 2, 3.5 or 4. Framework .Net 4 was installed but it doesn´t detect it, so I´ve installed .Net v2 and could successfully installed the SQLSysClrTypes.
Don´t know if this applies for SMO, but the CLR Types 2012 could be installed in XP.
I have a database in SQL server which is created on xp and to be opened on vista
When i try opening it on Vista.
Would this be possible
Thanks
Sun
SQL Server creates files that SQL Server can read. The file formats are independent of Windows versions.
What you should be aware of/considering are SQL Server versions and editions.
For instance, if you create a DB using SQL Server 2008 R2, you will not be able to attach/restore such a database using SQL Server 2005 or 2008, no matter what OS you're working on.
Similarly, if you've applied a particular service pack to the installation where the .mdf originates, you need to be working at the same or later service pack on the system where you want to read the file.
Similarly, if you create a database that uses features that are only available in higher level editions of SQL Server - i.e. something only available in Enterprise/Developer edition - you may have issues using the same database on a Standard Edition installation.
You don't open a sql server database with "xp" or "vista". You open the database in Sql Server. That's all that matters here: does the machine have the correct version of Sql Server available? Note that no version of Windows ships with Sql Server installed by default.
Also, unless you're talking about Sql Server Compact Edition you might want to re-think this. Full editions of Sql Server belong on the server editions of Windows. If you're building a database for an app that will live on individual user's desktop and the database will only serve the instance of the app on the machine, do not use sql server for that database. Instead, use something like Sql Server Compact Edition (it uses a different engine than full sql server that is more desktop-friendly), SQLite, or even Access.
Yes, there is no reason why this should not work.
As #Demian said, you can not open database created in SQL Server 2008 R2 in SQL Server 2008. But alternatively if you are sure that your database is not using any features specific to R2, you can script out whole database and then create similar database by running those scripts into SQL Server 2008 (ofcourse with some changes in script). And then just write some insert scripts to import data from 2008R2 to 2008 (Or you can use SSIS to dump data from one location to another location)
I think the question itself is pretty unclear. No explaination of environment of both XP and Vista machines (e.g. DBMS versions including SPs) or how you are trying to open/access database (using attach or by restoring backup). Without proper information I don't think there is any EXACT solution.