Unknown type - sys.date

Comments

• Andy C S Redgate › Posts: 173

  July 25, 2013 10:16AM

  Can you clarify exactly what it is you're doing? You said "linking my database to a SQL 2005 server" - what do you mean by that?
  
  Usually this kind of error suggests a SQL Server version mismatch - if you're linking to a repository of scripts generated by SQL Source Control on a different version of SQL Server, SQL Source Control may not be able to apply them to your database because the object creation scripts may use features not present in SQL 2005.

  Andy Campbell Smith
  
  Red Gate Technical Support Engineer

  0 · Share on Twitter
• Totu Posts: 14

  June 23, 2014 6:29AM

  Hi,
  
  Last Friday I bumped into the same error message in one for our CD pipelines, here is my fix:
  
  As Andy described, the error is thrown because the product thinks you have an old version of SQL Server as a source or target. Why does it think like that when my SQL Server is 2008 R2?
  
  When I was looking at the logs I found this line that gave me a hint:

  Warning: The SQL Server version specified for the scripts folder
  

  
  I went into the RedGateDatabaseInfo.xml and looked for something about the version and removed the DatabaseVersion tag. After running the pipeline again, it successfully finished.
  
  I hope this helps.
  
  Cheers,
  Balint

  Bálint Bartha, Skyscanner

  0 · Share on Twitter
• James B Redgate › Posts: 1,124 Silver 4

  June 26, 2014 10:58AM

  That's correct- the xml file will normally be populated with information about the server and database version, and if these are incorrect it'll change the behaviour.
  I believe it used to default to assuming 2005 which is why this error used to come up a lot more regularly- I think we may have changed the default to a more recent version which is why removing the info perhaps helped.

  Systems Software Engineer

  Redgate Software

  0 · Share on Twitter