Microsoft Azure + SQL Database - sql-server

How can i create a SQL Server 2008 SQL Database with microsoft azure.
Looks like it is defaulted to
productversion : 11.0.9214.43
productlevel : RTM
edition : SQL Azure
Please help me

SQL Azure is a cloud service version of SQL Server. You can't opt to use different versions of it (and it's actually slightly different to the regular server hosted version of SQL Server)
If you need a specific version of SQL Server hosted in Azure, you'll need to create a Virtual Machine and run it there.
Have a look through the VM Gallery to see if they have a pre-built VM Image with SQL 2008 installed,
Alternatively, spin up a Vanilla Window Server VM, and install SQL Server yourself.

Related

How to migrate collections from TFS 2017 to Azure DevOps Server 2019 (Different DB servers)

I have been handling an aging Windows Server 2008 machine with TFS upgraded in place to 2017.2. Now, with Azure DevOps Server 2019, support for Windows Server 2008 is no longer available. Also, the existing SQL Server is 2012 and is no longer supported as well. I cannot upgrade the database to SQL Server 2014+ as there is the OS restriction. and in our company, upgrading OS in-place is not allowed.
Existing setup is as follows:
Windows Server 2008 (One VM)
TFS 2017.2
SQL Server 2012 Ent (On same VM)
Non-HTTPS machine name URL Team Portal access over Intranet
I prepared a brand new Windows Server 2016 for the Azure DevOps 2019.0.1. I also was able to get hold of a SQL AlwaysON Cluster based off SQL Server 2017 Ent just for Azure DevOps.
If I proceed with DevOps setup, I'll target the new DB Cluster and it will set up the new DB accordingly.
How do I move my existing collections to the new cluster (easy: restore DBs on the new cluster)?
Will Azure DevOps just accept the new collections?
All migration topics I've read are always assuming DB server and TFS server are the same and do not change.
Ideal path:
Install the SQL Server matching your original environment.
Attach the databases
Install a version of TFS that supports your SQL server version that is the same or newer than the original server.
Walk through the configuration wizard.
uninstall TFS server
Detach databases and uninstall SQL Server
Install the desired SQL Server version with the same instance name.
Attach databases
Install latest version of Azure DevOps Server
Walk through the Upgrade wizard.
Full details here:
https://devblogs.microsoft.com/premier-developer/move-or-clone-tfs-from-one-hardware-to-another-in-tfs-2017-2018/

Azure SQL Server VM with personal SQL Server production key

I created an Azure SQL Server Standard VM. As the price page showing, VM with SQL Server installed will charge additional SQL Server fee.
Now I found I have a SQL Server Enterprise key. After I upgrade my pre-installed SQL Server Standard version to Enterprise version, will I still be charged the SQL Server fee?
Thanks
After I upgrade my pre-installed Standard version Sql server to
Enterprise version. Will I still be charged the Sql Server fee?
Yes.
If you want to use your own key, you have to strat from a regular Windows Server VM (and not SQL Server VM). Then, on top of that Windows Server, you install your version of SQL Server with your key.

Missing Integration Services Catalog in Management Studio

I have SQL Server 2008 R2 SP3 standard edition installed. I access remote to the server where SQL Server is installed. The option of the integration services catalog is missing under the database connection.
I did check the followings
I have the role sysadmin when I log in SQL Server
The service of integration services is installed and running.
The installation of the management studio is complete
I am missing the Microsoft SQL Server Integration Services when I run the Dcomcnfg.exe under Services, Computers, My Computer, and DCOM Config. Weird I am missing this. I wanted to find this to give appropriate permissions, but can't since the node is not there.
Any ideas? Help!
That's because you're using SSMS 2008. The Integration Services Catalog was introduced with SQL Server 2012. The older client doesn't know that's a "thing."
I prefer to manage servers with the latest and greatest version of SSMS which is now a free download.
Microsoft® SQL Server® 2014
Choose "MgmtStudio 32BIT\SQLManagementStudio_x86_ENU.exe"
For clarification
Integration Services Catalog
Integration Services Object Explorer
I had the same problem, Integration Server Catalog is invisible
This is my solution:
Check your installation edition of SQL Server.
How to check? right click on the node of (SQL Server...) on SSMS - click properties - in "general" check the "product" name.
If you still use "SQL Server Developer Edition", some features will not available.
the solution is download SQL Server Enterprise Edition.
I have no idea for Standard Edition, but maybe you can also use Enterprise Edition.
This is link for download : download SQL Server 2014
Click setup.exe to install and choose New SQL Server Stand-alone Installation select the feature you need. I think you can also select Integration Services in Feature Selection.. then fill the instance name and instance ID. continue the installation process until complete.
Open SQL Server Management Studio. Database Engine connection -> Server Name: (Server Name) / (Instance ID)
You will see the Integration Server Catalog. In the picture bellow, you can compare the display between SQL Server Developer Edition (above) & SQL Server Enterprise Edition (bottom with instance name).
I hope it can help..
Final result:
I got same issue and i have installed SSMS 17.0 and now i am able to create the SSISDB catalog with encryption password.
It's working as expected.

Unable to login to sql server

I dont know much about sql server.
I have just re-installed windows 7 on my laptop. After that I installed Visual Studio 2012 Express Edition. I also Installed SQL Server Management Studio 2008 R2.
Now when I try to log in to sql server management studio by using server name as . or (local) or .\SQLEXPRESS or PC-Name\SQLEXPRESS and using Windows Authentication I get the error as below.
Please dont mark this question as negative as I have searched on google for last 4 hours but did not understand the problem.
Update:
There are many reasons that may cautioning the problem:
SQL Server is not running
SQL Server is not properly configured
You try to connect with a worng instance Name
You can try the following:
Go to Mycomputer->Rigt Click->Manage->Application and Services
And from there check that SQL Server Express is running
2.From there also, gCheck the Instance name of your SQL Express and be sure when you log on to Management Studio you Provide the same Instance name
Confirm that the service is installed and running. Under Computer Management, drill-down into Services and Applications -> Services.
There should be a service named "SQL Server (SQLEXPRESS)". Try a restart or start of the service.
If any other instance of SQL Server is installed it will be listed - try connecting to LOCALHOST(whatever the instance is listed as) to verify the installation is functional.
UPDATED following further information from comments:
You may have only installed the client tools (management studio), and have not installed the database service. Ensure you have the correct installer which includes the database services engine.
First check that the SQL Server parameters are set accordingly.
Go to Start -
All Programs — Microsoft SQL Server 2008 R2 — Configuration tools —
SQL Server Configuration Manager
Under SQL Server Services, make sure that the instance is running :
SQL Server ()
SQL Server Browser
Under SQL Server Network Configuration - Protocols for (), these are enabled:
TCP/IP
Named Pipes
Do the same under SQL Native Client 10.0 under Client Protocols

confusion about SQL Server Express and localdb

I need to deploy a WCF service with a database on client machines. I am confused about SQL Server Express. I need to verify all of the following.
When attaching database files in the App_Data folder, do I still need to install SQL Server Express engine (Windows service) on client machines?
There is a flavor called SQL Server Express LocalDb. That one does not need an engine (Windows service)? But I think it need a prerequisite installation of LocalDb.
Localdb is introduced with SQL Server 2012. There is NO localdb for SQL Server 2008. Correct? I could not find 2008 version on MS site.
Do I still need to install SQL Server Express engine (A win Service)
on client machines?
Yes, they need it installed for your application to query the database. Can't really get around it.
There is a flavor called SQL Express localDb. That one does not need
an engine (win service)? but I think it need a perquisite installation
of localdb.
Yes, you'd still need to install LocalDB on the client machine. It's pretty hassle-free to do, but I think it's overkill unless you really need the full features of a SQL Server instance for your webservice.
Instead of LocalDB I'd strongly recommend using SQL Server Compact Edition - it performs the role you're thinking of (your WCF Service can simply connect directly to the database file on your client machines without installing SQL Server, and is lightweight), but doesn't need to be installed (it's simply included as a DLL with your WCF application):
Unlike other editions of Microsoft SQL Server, SQL CE runs
in-process with the application which is hosting it.
In Microsoft's own words on the differences between LocalDB and SQLCE:
LocalDB and SQL Server Compact?
Small and simple database, lightweight installation, connecting to a
database file -- this will sound familiar to any developer using SQL
Server Compact. The similarities are not accidental, as our goal for
LocalDB was to be as easy to use as SQL Server Compact (while being as
powerful and compatible with full SQL Server as SQL Express).
There are significant differences between LocalDB and SQL Server
Compact:
Execution mode: SQL Server Compact is an in-proc DLL, while LocalDB runs as a separate process.
SQL Server CE is kind of like an updated version of MS Access, the file goes with the application which can "just connect" to the database file without involving any database server installation, and its syntax/features are very close to SQL Server standard.

Resources