Your feedback is highly appreciated! Let's make Vertabelo even better.

0
Answered

Account Expired

dhaval patel 8 years ago updated by Adam Mościcki 7 years ago 1

I only had the trial account for 7 days ... is that all you provide as a trial period ?

Answer
Adam Mościcki 7 years ago

Hello,


Yes, that is all.

In some cases we extend a trial period for one more week. I have extended yours too.


Best regards,

Adam

Answer
Adam Mościcki 8 years ago

Hello,


Yes, it does. Instruction:


Best regards,

Adam

0
Answered

How can I extract sql script only for changes that we made on our model

Kesiya Abraham 8 years ago updated by anonymous 8 years ago 6

If I add a new column,how can I generate SQL script for that particular change

Answer
anonymous 8 years ago

Hello,


There is no way to that easily right now. You can generate 'drop' script and 'creation' script, but it works only for fresh databases and requires deletion of data in the table.


We've implemented a migration tool which can do that, but we are still testing it. We are going to release it in about 2 weeks.


I hope this helps.




0
Answered

Where I can find invoices?

Vlad Kucherov 8 years ago updated by anonymous 8 years ago 8

Hi,


I want to export all the invoices for my payments.

Where I can find them?

0
Fixed

cannot view my own imported sql database

Denise Field 8 years ago updated by anonymous 8 years ago 7

The file imports successfully but then will not view, I click on the database and get

Oops we've got a problem. Something went wrong ... Reload page


I just upgraded to the premium subscriptin specifically to be able to to this, but if it doesn't work this is useless to me, can you sort it.


<


-- phpMyAdmin SQL Dump

-- version 4.2.7.1

-- http://www.phpmyadmin.net

--

-- Host: 127.0.0.1

-- Generation Time: Sep 30, 2016 at 10:49 AM

-- Server version: 5.5.39

-- PHP Version: 5.4.31

SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";

SET time_zone = "+00:00";

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;

/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;

/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;

/*!40101 SET NAMES utf8 */;

--

-- Database: `reviews`

--

-- --------------------------------------------------------

--

-- Table structure for table `broker`

--

CREATE TABLE IF NOT EXISTS `broker` (

`BrokerID` int(11) NOT NULL,

`BrokerName` varchar(50) NOT NULL,

`BrokerWebsite` varchar(50) NOT NULL,

`BrokerReview` text NOT NULL,

`BrokerCoverOverview` text NOT NULL,

`BrokerImportant` text NOT NULL,

`BrokerPolicyWording` text NOT NULL,

`BrokerPros` text NOT NULL,

`BrokerCons` text NOT NULL,

`BrokerWebsiteInfo` text NOT NULL,

`BrokerConclusion` text NOT NULL,

`BrokerImage` blob NOT NULL,

`Niche_NicheID` int(11) NOT NULL,

`Modified Date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=197 ;

--

-- Dumping data for table `broker`

--

--

-- Table structure for table `brokerpolicytype`

--

CREATE TABLE IF NOT EXISTS `brokerpolicytype` (

`BrokerPolicyTextID` int(11) NOT NULL,

`BrokerPolicyText` text NOT NULL,

`PolicyType_PolicyTypeID` int(11) NOT NULL,

`Broker_BrokerID` int(11) NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=5 ;

--

-- Dumping data for table `brokerpolicytype`

--

----------------------------------------------------

--

-- Table structure for table `calendar`

--

CREATE TABLE IF NOT EXISTS `calendar` (

`id` int(11) NOT NULL,

`title` varchar(300) NOT NULL,

`description` text,

`start_date` date NOT NULL,

`start_time` time DEFAULT NULL,

`end_date` date DEFAULT NULL,

`end_time` time DEFAULT NULL,

`recurrence` varchar(1) DEFAULT NULL,

`period` varchar(1) DEFAULT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ;

-- --------------------------------------------------------

--

-- Table structure for table `covername`

--

CREATE TABLE IF NOT EXISTS `covername` (

`CoverNameID` int(11) NOT NULL,

`CoverName` varchar(50) NOT NULL,

`Cover Icon Large` blob NOT NULL,

`Cover Icon Small` blob NOT NULL,

`Cover Name Text` text NOT NULL,

`Modified Date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=36 ;

--

-- Dumping data for table `covername`

--

-- --------------------------------------------------------

--

-- Table structure for table `coversumsinfo`

--

CREATE TABLE IF NOT EXISTS `coversumsinfo` (

`CoverID` int(11) NOT NULL,

`CoverAmount` decimal(10,2) NOT NULL,

`Notes` text NOT NULL,

`CoverName_CoverNameID` int(11) NOT NULL,

`CoverType_CoverTypeID` int(11) NOT NULL,

`PolicyName_PolicyNameID` int(11) NOT NULL,

`IncludedYN` char(1) NOT NULL DEFAULT 'Y'

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--

-- Table structure for table `covertype`

--

CREATE TABLE IF NOT EXISTS `covertype` (

`CoverTypeID` int(11) NOT NULL,

`CoverType` varchar(50) NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=4 ;

--

-- Dumping data for table `covertype`

--

-- --------------------------------------------------------

--

-- Table structure for table `images`

--

CREATE TABLE IF NOT EXISTS `images` (

`ImageID` int(11) NOT NULL,

`frontpage` blob NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=9 ;

--

-- Dumping data for table `images`

--

-- --------------------------------------------------------

--

-- Table structure for table `location`

--

CREATE TABLE IF NOT EXISTS `location` (

`LocationID` int(11) NOT NULL,

`LocationName` varchar(50) NOT NULL,

`LocationImage` blob NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=4 ;

--

-- Dumping data for table `location`

--

-- --------------------------------------------------------

--

-- Table structure for table `niche`

--

CREATE TABLE IF NOT EXISTS `niche` (

`NicheID` int(11) NOT NULL,

`NicheName` varchar(50) NOT NULL,

`NicheImage` blob NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=23 ;

--

-- Dumping data for table `niche`

--

--

-- Table structure for table `personage`

--

CREATE TABLE IF NOT EXISTS `personage` (

`personAgeID` int(11) NOT NULL,

`personAgetext` varchar(30) NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=4 ;

--

-- Dumping data for table `personage`

--

-- --------------------------------------------------------

--

-- Table structure for table `personagelocation`

--

CREATE TABLE IF NOT EXISTS `personagelocation` (

`PersonLocationID` int(11) NOT NULL,

`Location_LocationID` int(11) NOT NULL,

`PersonType_PersonTypeID` int(11) NOT NULL,

`QuoteType_QuoteTypeID` int(11) NOT NULL,

`PersonAge_personAgeID` int(11) NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--

-- Table structure for table `persontype`

--

CREATE TABLE IF NOT EXISTS `persontype` (

`PersonTypeID` int(11) NOT NULL,

`PersonTypeName` varchar(50) NOT NULL,

`PersonTypeImage` blob NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=4 ;

--

-- Dumping data for table `persontype`

--

-- --------------------------------------------------------

--

-- Table structure for table `policyname`

--

CREATE TABLE IF NOT EXISTS `policyname` (

`PolicyNameID` int(11) NOT NULL,

`PolicyName` varchar(50) NOT NULL,

`PolicyNameImage` blob NOT NULL,

`Underwriter_UnderwriterID` int(11) NOT NULL,

`BrokerPolicyType_BrokerPolicyTextID` int(11) NOT NULL,

`StarRating_StarRatingID` int(11) NOT NULL,

`Modifield Date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP

) ENGINE=InnoDB DEFAULT CHARSET=latin1 COMMENT='e.g. single trip, multi trip' AUTO_INCREMENT=10 ;

--

-- Dumping data for table `policyname`

--

-- --------------------------------------------------------

--

-- Table structure for table `policytype`

--

CREATE TABLE IF NOT EXISTS `policytype` (

`PolicyTypeID` int(11) NOT NULL,

`PolicyType` varchar(50) NOT NULL,

`PolicyTypeImage` blob NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=3 ;

--

-- Dumping data for table `policytype`

--

-- --------------------------------------------------------

--

-- Table structure for table `quotetype`

--

CREATE TABLE IF NOT EXISTS `quotetype` (

`QuoteTypeID` int(11) NOT NULL,

`QuoteTypeAmount` decimal(10,2) NOT NULL,

`QuoteTypeExcess` decimal(10,2) NOT NULL,

`QuoteTypeInformation` text NOT NULL,

`QuoteTypeImage` blob NOT NULL,

`PolicyName_PolicyNameID` int(11) NOT NULL,

`Modified Date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ;

--

-- Dumping data for table `quotetype`

--

-- --------------------------------------------------------

--

-- Table structure for table `starrating`

--

CREATE TABLE IF NOT EXISTS `starrating` (

`StarRatingID` int(11) NOT NULL,

`StarRatingNumber` int(11) NOT NULL,

`StarRatingImage` blob NOT NULL,

`StarRatingImageXS` blob NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1 COMMENT='star rating' AUTO_INCREMENT=7 ;

--

-- Dumping data for table `starrating`

--

--

-- Table structure for table `underwriter`

--

CREATE TABLE IF NOT EXISTS `underwriter` (

`UnderwriterID` int(11) NOT NULL,

`UnderwriterName` varchar(50) NOT NULL,

`UnderwriterImage` blob NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=29 ;

--

-- Dumping data for table `underwriter`

--

-- --------------------------------------------------------

--

-- Table structure for table `userspasswd`

--

CREATE TABLE IF NOT EXISTS `userspasswd` (

`login` varchar(50) NOT NULL,

`pswd` varchar(50) NOT NULL,

`user id` int(11) NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=6 ;

--

-- Dumping data for table `userspasswd`

--

--

-- Indexes for dumped tables

--

--

-- Indexes for table `broker`

--

ALTER TABLE `broker`

ADD PRIMARY KEY (`BrokerID`), ADD UNIQUE KEY `Broker_ak_1` (`BrokerName`), ADD KEY `Broker_Niche` (`Niche_NicheID`);

--

-- Indexes for table `brokerpolicytype`

--

ALTER TABLE `brokerpolicytype`

ADD PRIMARY KEY (`BrokerPolicyTextID`), ADD KEY `BrokerPolicyType_Broker` (`Broker_BrokerID`), ADD KEY `BrokerPolicyType_PolicyType` (`PolicyType_PolicyTypeID`);

--

-- Indexes for table `calendar`

--

ALTER TABLE `calendar`

ADD PRIMARY KEY (`id`);

--

-- Indexes for table `covername`

--

ALTER TABLE `covername`

ADD PRIMARY KEY (`CoverNameID`), ADD UNIQUE KEY `CoverName_ak_1` (`CoverName`);

--

-- Indexes for table `coversumsinfo`

--

ALTER TABLE `coversumsinfo`

ADD PRIMARY KEY (`CoverID`), ADD KEY `CoverSumsInfo_CoverName` (`CoverName_CoverNameID`), ADD KEY `CoverSumsInfo_CoverType` (`CoverType_CoverTypeID`), ADD KEY `CoverSumsInfo_PolicyName` (`PolicyName_PolicyNameID`);

--

-- Indexes for table `covertype`

--

ALTER TABLE `covertype`

ADD PRIMARY KEY (`CoverTypeID`), ADD UNIQUE KEY `CoverType_ak_1` (`CoverType`);

--

-- Indexes for table `images`

--

ALTER TABLE `images`

ADD PRIMARY KEY (`ImageID`);

--

-- Indexes for table `location`

--

ALTER TABLE `location`

ADD PRIMARY KEY (`LocationID`), ADD UNIQUE KEY `Location_ak_1` (`LocationName`);

--

-- Indexes for table `niche`

--

ALTER TABLE `niche`

ADD PRIMARY KEY (`NicheID`), ADD UNIQUE KEY `Niche_ak_1` (`NicheName`);

--

-- Indexes for table `personage`

--

ALTER TABLE `personage`

ADD PRIMARY KEY (`personAgeID`);

--

-- Indexes for table `personagelocation`

--

ALTER TABLE `personagelocation`

ADD PRIMARY KEY (`PersonLocationID`), ADD KEY `PersonLocation_Location` (`Location_LocationID`), ADD KEY `PersonLocation_PersonType` (`PersonType_PersonTypeID`), ADD KEY `PersonLocation_QuoteType` (`QuoteType_QuoteTypeID`), ADD KEY `PersonAge_personAgeID` (`PersonAge_personAgeID`);

--

-- Indexes for table `persontype`

--

ALTER TABLE `persontype`

ADD PRIMARY KEY (`PersonTypeID`), ADD UNIQUE KEY `PersonType_ak_1` (`PersonTypeName`);

--

-- Indexes for table `policyname`

--

ALTER TABLE `policyname`

ADD PRIMARY KEY (`PolicyNameID`), ADD KEY `PolicyName_BrokerPolicyType` (`BrokerPolicyType_BrokerPolicyTextID`), ADD KEY `PolicyName_Underwriter` (`Underwriter_UnderwriterID`), ADD KEY `StarRating_StarRatingID` (`StarRating_StarRatingID`);

--

-- Indexes for table `policytype`

--

ALTER TABLE `policytype`

ADD PRIMARY KEY (`PolicyTypeID`);

--

-- Indexes for table `quotetype`

--

ALTER TABLE `quotetype`

ADD PRIMARY KEY (`QuoteTypeID`), ADD KEY `QuoteType_PolicyName` (`PolicyName_PolicyNameID`);

--

-- Indexes for table `starrating`

--

ALTER TABLE `starrating`

ADD PRIMARY KEY (`StarRatingID`), ADD KEY `StarRatingID` (`StarRatingID`);

--

-- Indexes for table `underwriter`

--

ALTER TABLE `underwriter`

ADD PRIMARY KEY (`UnderwriterID`), ADD UNIQUE KEY `Underwriter_ak_1` (`UnderwriterName`);

--

-- Indexes for table `userspasswd`

--

ALTER TABLE `userspasswd`

ADD PRIMARY KEY (`user id`);

--

-- AUTO_INCREMENT for dumped tables

--

--

-- AUTO_INCREMENT for table `broker`

--

ALTER TABLE `broker`

MODIFY `BrokerID` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=197;

--

-- AUTO_INCREMENT for table `brokerpolicytype`

--

ALTER TABLE `brokerpolicytype`

MODIFY `BrokerPolicyTextID` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=5;

--

-- AUTO_INCREMENT for table `calendar`

--

ALTER TABLE `calendar`

MODIFY `id` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=2;

--

-- AUTO_INCREMENT for table `covername`

--

ALTER TABLE `covername`

MODIFY `CoverNameID` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=36;

--

-- AUTO_INCREMENT for table `coversumsinfo`

--

ALTER TABLE `coversumsinfo`

MODIFY `CoverID` int(11) NOT NULL AUTO_INCREMENT;

--

-- AUTO_INCREMENT for table `covertype`

--

ALTER TABLE `covertype`

MODIFY `CoverTypeID` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=4;

--

-- AUTO_INCREMENT for table `images`

--

ALTER TABLE `images`

MODIFY `ImageID` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=9;

--

-- AUTO_INCREMENT for table `location`

--

ALTER TABLE `location`

MODIFY `LocationID` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=4;

--

-- AUTO_INCREMENT for table `niche`

--

ALTER TABLE `niche`

MODIFY `NicheID` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=23;

--

-- AUTO_INCREMENT for table `personage`

--

ALTER TABLE `personage`

MODIFY `personAgeID` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=4;

--

-- AUTO_INCREMENT for table `personagelocation`

--

ALTER TABLE `personagelocation`

MODIFY `PersonLocationID` int(11) NOT NULL AUTO_INCREMENT;

--

-- AUTO_INCREMENT for table `persontype`

--

ALTER TABLE `persontype`

MODIFY `PersonTypeID` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=4;

--

-- AUTO_INCREMENT for table `policyname`

--

ALTER TABLE `policyname`

MODIFY `PolicyNameID` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=10;

--

-- AUTO_INCREMENT for table `policytype`

--

ALTER TABLE `policytype`

MODIFY `PolicyTypeID` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=3;

--

-- AUTO_INCREMENT for table `quotetype`

--

ALTER TABLE `quotetype`

MODIFY `QuoteTypeID` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=2;

--

-- AUTO_INCREMENT for table `starrating`

--

ALTER TABLE `starrating`

MODIFY `StarRatingID` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=7;

--

-- AUTO_INCREMENT for table `underwriter`

--

ALTER TABLE `underwriter`

MODIFY `UnderwriterID` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=29;

--

-- AUTO_INCREMENT for table `userspasswd`

--

ALTER TABLE `userspasswd`

MODIFY `user id` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=6;

--

-- Constraints for dumped tables

--

--

-- Constraints for table `broker`

--

ALTER TABLE `broker`

ADD CONSTRAINT `Broker_Niche` FOREIGN KEY (`Niche_NicheID`) REFERENCES `niche` (`NicheID`);

--

-- Constraints for table `brokerpolicytype`

--

ALTER TABLE `brokerpolicytype`

ADD CONSTRAINT `BrokerPolicyType_Broker` FOREIGN KEY (`Broker_BrokerID`) REFERENCES `broker` (`BrokerID`),

ADD CONSTRAINT `BrokerPolicyType_PolicyType` FOREIGN KEY (`PolicyType_PolicyTypeID`) REFERENCES `policytype` (`PolicyTypeID`);

--

-- Constraints for table `coversumsinfo`

--

ALTER TABLE `coversumsinfo`

ADD CONSTRAINT `CoverSumsInfo_CoverName` FOREIGN KEY (`CoverName_CoverNameID`) REFERENCES `covername` (`CoverNameID`),

ADD CONSTRAINT `CoverSumsInfo_CoverType` FOREIGN KEY (`CoverType_CoverTypeID`) REFERENCES `covertype` (`CoverTypeID`),

ADD CONSTRAINT `CoverSumsInfo_PolicyName` FOREIGN KEY (`PolicyName_PolicyNameID`) REFERENCES `policyname` (`PolicyNameID`);

--

-- Constraints for table `personagelocation`

--

ALTER TABLE `personagelocation`

ADD CONSTRAINT `personagelocation_ibfk_2` FOREIGN KEY (`PersonAge_personAgeID`) REFERENCES `personage` (`personAgeID`),

ADD CONSTRAINT `PersonLocation_Location` FOREIGN KEY (`Location_LocationID`) REFERENCES `location` (`LocationID`),

ADD CONSTRAINT `PersonLocation_PersonType` FOREIGN KEY (`PersonType_PersonTypeID`) REFERENCES `persontype` (`PersonTypeID`),

ADD CONSTRAINT `PersonLocation_QuoteType` FOREIGN KEY (`QuoteType_QuoteTypeID`) REFERENCES `quotetype` (`QuoteTypeID`);

--

-- Constraints for table `policyname`

--

ALTER TABLE `policyname`

ADD CONSTRAINT `PolicyName_BrokerPolicyType` FOREIGN KEY (`BrokerPolicyType_BrokerPolicyTextID`) REFERENCES `brokerpolicytype` (`BrokerPolicyTextID`),

ADD CONSTRAINT `policyname_StarRatingID` FOREIGN KEY (`StarRating_StarRatingID`) REFERENCES `starrating` (`StarRatingID`),

ADD CONSTRAINT `PolicyName_Underwriter` FOREIGN KEY (`Underwriter_UnderwriterID`) REFERENCES `underwriter` (`UnderwriterID`);

--

-- Constraints for table `quotetype`

--

ALTER TABLE `quotetype`

ADD CONSTRAINT `QuoteType_PolicyName` FOREIGN KEY (`PolicyName_PolicyNameID`) REFERENCES `policyname` (`PolicyNameID`);

/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;

/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;

/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

>

0
Not a bug

Error 'Cannot create more than one clustered index on table' when running Vertabelo generated scripts

Dave Sopko 8 years ago updated by anonymous 8 years ago 2

SQL Server. When specifying a multi-column clustered index that is not the primary key I get the following error when running the Vertabelo generated scripts.


Cannot create more than one clustered index on table 'DietCalendar'.


-- Table: DietCalendar
CREATE TABLE DietCalendar (
ID uniqueidentifier NOT NULL,
UserID uniqueidentifier NOT NULL,
EntryDate datetime2 NOT NULL,
CONSTRAINT DietCalendar_pk PRIMARY KEY (ID)
);
CREATE UNIQUE CLUSTERED INDEX UCI_DieteCalendar_UserID_EntryDate_ID on DietCalendar (UserID ASC,EntryDate ASC,ID ASC);

In order for this to be compatible with SQL Server 2012 as well as Azure SQL versions, I need Vertabelo to generate the clustered index within the 'CREATE TABLE' statement in this fashion:


CREATE TABLE DietCalendar (
ID uniqueidentifier NOT NULL,
UserID uniqueidentifier NOT NULL,
EntryDate datetime2 NOT NULL,
CONSTRAINT DietCalendar_pk PRIMARY KEY NONCLUSTERED (ID),
INDEX UCI_DieteCalendar_UserID_EntryDate_ID UNIQUE CLUSTERED (UserID ASC,EntryDate ASC,ID ASC)
);


Creating clustered indexes in Azure

http://stackoverflow.com/a/39730175/1197553


0
Fixed

Misspelling in Article Title

Kindler Chase 8 years ago updated by Agnieszka Kozubek-Krycuń (Chief Scientist) 8 years ago 1

In the blog post for SQL Windows Functions, the title is misspelled, re: "Fucntions" should be "Functions"

http://www.vertabelo.com/blog/technical-articles/exploring-window-functions-in-sql-server-part-two-aggregating-data

0

When selecting 'Generate migration from this version' I get Bad request

Dave Sopko 8 years ago 0

When selecting 'Generate migration from this version' from any entry in the Model Versions section I am navigated to the Bad request page.

+5
Under review

How to define naming conventions for objects

Shantanu Kher 9 years ago updated by Dave Sopko 8 years ago 2
I notice that Vertabelo applies some predefined conventions for naming objects like indexes. Being a Vertabelo user, can I configure these naming conventions by my own? Please advise.
0
Answered

Reverse engineer from SQL Scripts

Minglin Deng 8 years ago updated by Adam Mościcki 8 years ago 1

Hello,

Does this tool have ability to import from SQL statements?

The reverse engineering tool on your site is 3+ years old.

-- Agnieszka Kozubek 16th December 2013

https://www.vertabelo.com/blog/documentation/reverse-engineering

Any improvements on your reverse engineering since year 2013??


Thanks.

Answer
Adam Mościcki 8 years ago

Hello,


I have answered for privert ticket, but this might be helpful to others.


The reverse engineering tool imports tables from database directly.

Import from SQL script can be done on the 'new model' page.


Best regards,


Adam Mościcki