I have a question reharding strange behavior of Sql Server. I had sql server 2008 edition which I uninstalled and installed SSMS Express 2014 instead. However I could not perform any advanced analytics on sample northwind db i.e. lead, lag, preceding etc.
When I asked the program ##version, the output was 2008sp4.
How may it be that SSMS2014 has 2008 engine? How to fix it?
There two applications such as SQL Server and SSMS.
SQL Server is a windows service which stores data. It does not have user interface.
SSMS is an UI application which connects to SQL Server to manipulate data by T-SQL language. It has user interface.
When you execute ##version, then you get a version of SQL Server.
If you want to know your SSMS version, then just click Help -> About
Related
Recently, a tech support specialist installed SQL Server 2016 Management Studio in my computer. When I asked about the possibility of using integrated R services in SSMS, he said I need to have stand alone SQL server installed in order to use that feature (which is not going to happen as individual license is pretty expensive).
Can somebody shed some light on using R services from SQL server 2016? Do I really need stand alone SQL server? or there is a workaround?
Thank you
poshan
SQL Server 2016 Management Studio is a client tool that connects to the Microsoft SQL Server 2016. If R-service already installed (as part of setup wizard, if you have chosen Database Engine Services and R-Services (In-Database)), you can connect to the SQL Server and execute R-script from Management Studio setup in your machine.
Some useful documentation:-
https://msdn.microsoft.com/en-us/library/mt696069.aspx
I have a server running SQL Server 2008 Enterprise version which has a lot of SQL Codes and I want to upgrade it into SQL Server 2014 Enterprise version. But I don't know what will happen after I upgrade the SQL Server. Will there any SQL Code go unavailable/error? Will it run correctly after upgrading?
SQL Server 2008/2014 is a tool. It has got nothing to do with data/procedures/views etc. Data for SQL Server is stored in the form of .mdf files. So, no, your data or procedurers wont be touched. But yes lot of features are going to be deprecated in SQL Server 2014 when compared to SQL Server 2008. Full list is here. You should go through the list and find a suitable replacement for every deprecated item before migrating.
Currently I am working on a project it is request us to connect their database (Server A with Microsoft SQL Server 2014) via SSRS (Server B with Microsoft SQL Server 2005).
I keep facing the problem with this message :
The version of the report server database is either in a format that
is not valid, or it cannot be read. The found version is '162'. The
expected version is 'C.0.8.54'. To continue, update the version of the
report server database and verify access rights.
(rsInvalidReportServerDatabase) (rsRPCError) Get Online Help
Can anyone help me? Thanks a lot.
I think the problem is likely to be that the ReportServer database has been created using SQL Server 2014. Trying to connection a SQL Server 2005 Report Server installation to that database will not work because they are not compatible. If it is possible to run Reporting Services with a configuration like this at all, and I'm not sure that it is, you will need to have a ReportServer database that was created using SQL Server 2005 Reporting Services Configuration Manager.
I am working in SSMS 2012. I recently discovered that 2012 built-in functions like TRY_CONVERT and DATEFROMPARTS are not recognized by my particular instance. So, I checked my database engine (at least, I think it's the engine I'm checking) via SELECT ##VERSION, and it returned Microsoft SQL Server 2008 (RTM) - 10.01.1600.22 (X64). If this is an engine problem (i.e., I'm not using the 2012 engine), how do I update / change the engine to the 2012 version?
I can see 3 factors as play here than can confuse you:
SSMS Version: SSMS is only the GUI to access SQL Server. Later version of SSMS can access earlier version of the SQL Server Engine. The fact that you are running SSMS 2012 doesn't mean you will get access to new functions in SQL Server 2012.
SQL Server Engine Version: I think this is your problem. The result you got clearly indicate it's 2008.
Compatibility level: you can run a newer SQL Server Engine as if it's an older one. So you can run SQL Server 2012 as 2008 or even 2005. In that case, even though you engine supports these new functions, the compatibility level prevents you from using them.
I think your problem is that you are accessing SQL Server 2008 through SSMS 2012. Get the proper version of SQL Server through MSDN, SQL Server Express (free) or DreamSpark( if you are a student).
I installed WSS 2007 on one of our test server to see if sharepoint is worth going forward for our group. The problem is, it installed a version of sql server and we are using oracle. So, I will need to move sharepoint from sql server to oracle. We can't use sql server we have to use oracle.
I have two questions:
1. sql server to oracle transition for sharepoint
2. Is there a performance drawback when we move from sql server to oracle with sharepoint.
I tried to look for resources on web but couldn't find much. Any ideas/help would be appreciated.
This is not possible - SharePoint can only run on SQL Server:
Installation Guide for Microsoft Office SharePoint Server 2007
The database server must be running
Microsoft SQL Server 2005 or Microsoft
SQL Server 2000 with the most recent
service pack.
Enterprise Sharepoint? – Port it to Oracle
I have concluded my only real problem
with SharePoint is that you can’t run
it on Oracle.
If you had shown me SharePoint, not
told me it was from Microsoft and said
you can use it with Oracle as a back
end, I am sure my reaction to it would
have been far different.