November 9, 2015 at 7:04 am
Tried this out today as I was quite impressed with CTP2.
Anyone had any pleasent experiences with it?
Im going to install this once more on a new machine but it would appear that doing pretty much anything within SSMS results in an exception. I've traced them down to it running queries for system fields that do not even exist.
E.g create a table and you will see this this "Msg 207, Level 16, State 1, Line 7
Invalid column name 'server_id'". In a nice message box of course. You cannot view the properties of the database either using the GUI
the and profiler shows queries such as this:
SELECT
svrs.data_source AS [RemoteDataArchiveEndpoint],
svrs.name AS [RemoteDataArchiveLinkedServer],
rdad.remote_database_name AS [RemoteDatabaseName]
FROM
sys.remote_data_archive_databases rdad
INNER JOIN sys.servers svrs ON rdad.server_id = svrs.server_id
I'll give this another a go. They couldn't have just released a preview with more bugs than SQL 7, surely?
Rob
November 9, 2015 at 11:25 am
http://connect.microsoft.com and file a bug. It's a preview, bugs are expected.
That said, I saw CTP 3 in use by a lot of people over the last 2 weeks, so maybe it's something about what pieces you installed. Be sure to give as much detail as possible on the bug report.
Install it on a VM, then you can just trash and rebuild the VM when the next CTP comes out.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 10, 2015 at 12:29 pm
I used a 2016 CTP2 client to manage a CTP3 server, once I upgraded the client all was well! I spent a little time checking what had changed and it looked like just the name of the field, must have failed a code review!
.. now onto seeing how this works with SCCM 2016....
Rob
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply