Create a database layout for SMS autoresponses
In this guide we create an example database layout for an autoresponding SMS application that uses data stored in an SQL database. We use the Microsoft SQL Express database server that can be downloaded from the Microsoft website.
Step 1. - Download and install Microsoft SQL Express.
You can download the Microsoft SQL Express Database Server from the following location:
Download details: Microsoft SQL Server 2019 Express EditionStep 2 - Create your database tables in Microsoft SQL Express
You can create a database and the appropriate database tables by opening a windows command prompt (Start->Run->cmd.exe), and starting the SQL Command interpreter by typing:
C:\sqlcmd -S .\SQLExpress |
Once the SQL command interpreter is running, you should enter the following commands
create database ozeki GO use ozeki GO CREATE TABLE autoreplymessage ( id int IDENTITY (1,1), keyword varchar(30), msg varchar(160), ); GO sp_addLogin 'ozekiuser', 'ozekipass' GO sp_addsrvrolemember 'ozekiuser', 'sysadmin' GO |
Step 3 - Put some data into your keyboard database
To be able to create a response automatically for certain keywords we must fill the autoreplymessage database table:
insert into autoreplymessage (keyword,msg) values ("default","There is no data for this keyword."); insert into autoreplymessage (keyword,msg) values ("red","Red is a good color."); insert into autoreplymessage (keyword,msg) values ("blue","Blue is not the best option."); GO |
Step 4 - Make Microsoft SQL Express ready to accept your username and password
Unless you have mixed mode authentication configured in SQL express, you will not be able to connect to your database from Ozeki NG because Ozeki NG runs as a system service in the background. To enable mixed - mode authentication, you should open the registry editor (Start->run->regedit.exe) and in the Registry you should change the LoginMode value from 1 to "2", here:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer LoginMode =2 |
After this change, you might have to restart the SQL Express to make sure the changes take effect.
More information