Doubts regarding Sales Forecast model

I have few more clarification regarding time series.

Firstly

In my model the month level product sales value represented across 1^st day of every month.So that the key time column is of datetime datatype containing a sequence of dates representing the 1^st day of every month of the year.

Eg: 2006-01-01, 2006-02-01………. etc. all in (yy-mm-dd) format

But

when I make prediction for next five months, though it makes monthly

predictions the date part for the months are random whereas I expect

the date part to be 1^st of every month.What is the reason for this and how can I overcome it.

Secondly

Predicted

sales values for some time period are negative though I do not have any

negative value in the training data. What is the reason for this and

how can I rectify it?

Thirdly

In

one of your earlier posts you had said that the time series algorithm

does not have any built in time intelligence but uses the key time

column as a time sequence stamp. So If have to make predictions for a

particular time period where the time slice for each time period is 25

days or 50 days etc, then I understand that the input data used to

train the model should be in the same time sequence.

Or

Can I specify the span of the time period according to which the prediction needs to be made?

Basically

how can I use the same time series model to make monthly, yearly,

quarterly, daily or predictions or for custom time period like I have

mentioned above.

1: There really isn't a workaround - you should use your own logic for dates

2: There is a parameter MINIMUM_PREDICTION_VALUE (or something like that) that you can set to 0, and you won't get negative predictions.

3: You should make unique models for each period you want to analyze - the patterns and periodicities are different, and need different analyses.

|||Thanks Jamie

Doubts on Indexing.

Hi,

set @.DN=''

set @.DN=@.DN+'AA9999'

select @.ID = ID from TableA where status='A' and ColumnA like '%'+@.DN

ColumnA is NonClusteredIndex

When I use = symbol it goes for Index Seek (like below query) otherwise its going for table scan. Could anyone advice me which index need to be used for getting 'Index Seek' when I use like Operator. Basically TableA has millions of records.

select @.ID = ID from TableA where status='A' and Code = 'AA9999'

Regards

JMR

I think it is the normal behavior because SQL have to compare all ColumnA values with a pattern and have to go row to row; in the other select SQL look at an unique values.

So, it is recommended to avoid like operator in WHERE clause.

|||

If you use LIKE + '%xxxxx' , there is no option; It forced to use Scan. Bcs we don't know where start. When the pattern will match.

If you use LIKE + 'xxxx%', it might use Index Scan / Seek depend with your data density.

bcs the LIke 'xxxx%' will be converted as col >= 'xxxx' and col < 'xxxxY';

Doubts about Transaction Log

Hello to Everybody!
I have a doubts about Transaction Log. What's happen when I execute the
follow command
BACKUP LOG [database] WITH NO_LOG ou BACKUP LOG [database] WITH TRUN
CATE_ONLY
So, When should I use this command to avoid fill up the log?
Thanks a Lot
Juliano HortaDon't use it. Either have the db in simple recovery mode. Or do regular tran
saction log backups (the
log is emptied when you do a log backup).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Juliano H via droptable.com" <forum@.droptable.com> wrote in message
news:541010E0E3B40@.droptable.com...
> Hello to Everybody!
> I have a doubts about Transaction Log. What's happen when I execute the
> follow command
> BACKUP LOG [database] WITH NO_LOG ou BACKUP LOG [database] WITH TR
UNCATE_ONLY
> So, When should I use this command to avoid fill up the log?
> Thanks a Lot
> Juliano Horta|||Only use this if you do not need to be recoverable via trans log, if so
maybe you should just use simple recovery mode
Below is from BOL
Note If backing up the log does not appear to truncate most of the log, an
old open transaction may exist in the log. Log space can be monitored with
DBCC SQLPERF (LOGSPACE). For more information, see Transaction Log Backups.
NO_LOG | TRUNCATE_ONLY
Removes the inactive part of the log without making a backup copy of it and
truncates the log. This option frees space. Specifying a backup device is
unnecessary because the log backup is not saved. NO_LOG and TRUNCATE_ONLY
are synonyms.
After backing up the log using either NO_LOG or TRUNCATE_ONLY, the changes
recorded in the log are not recoverable. For recovery purposes, immediately
execute BACKUP DATABASE.
"Juliano H via droptable.com" <forum@.droptable.com> wrote in message
news:541010E0E3B40@.droptable.com...
> Hello to Everybody!
> I have a doubts about Transaction Log. What's happen when I execute the
> follow command
> BACKUP LOG [database] WITH NO_LOG ou BACKUP LOG [database] WITH
> TRUNCATE_ONLY
> So, When should I use this command to avoid fill up the log?
> Thanks a Lot
> Juliano Horta|||Hi,
To add on to Tibor and David; Go ahead with SIMPLE recovery model if you do
not require a point in time recovery.
There is no difference between NO_LOG and TRUNCATE_ONLY. Both are same and
will truncate the inactive
portion of the log.
Thanks
Hari
SQL Server MVP
"David J. Cartwright" <davidcartwright@.hotmail.com> wrote in message
news:uYKNlZKtFHA.3080@.TK2MSFTNGP15.phx.gbl...
> Only use this if you do not need to be recoverable via trans log, if so
> maybe you should just use simple recovery mode
>
> Below is from BOL
>
> Note If backing up the log does not appear to truncate most of the log,
> an old open transaction may exist in the log. Log space can be monitored
> with DBCC SQLPERF (LOGSPACE). For more information, see Transaction Log
> Backups.
>
> NO_LOG | TRUNCATE_ONLY
> Removes the inactive part of the log without making a backup copy of it
> and truncates the log. This option frees space. Specifying a backup device
> is unnecessary because the log backup is not saved. NO_LOG and
> TRUNCATE_ONLY are synonyms.
> After backing up the log using either NO_LOG or TRUNCATE_ONLY, the changes
> recorded in the log are not recoverable. For recovery purposes,
> immediately execute BACKUP DATABASE.
>
> "Juliano H via droptable.com" <forum@.droptable.com> wrote in message
> news:541010E0E3B40@.droptable.com...
>

Doubts about Transaction Log

Hello to Everybody!
I have a doubts about Transaction Log. What's happen when I execute the
follow command
BACKUP LOG [database] WITH NO_LOG ou BACKUP LOG [database] WITH TRUNCATE_ONLY
So, When should I use this command to avoid fill up the log?
Thanks a Lot
Juliano Horta
Don't use it. Either have the db in simple recovery mode. Or do regular transaction log backups (the
log is emptied when you do a log backup).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Juliano H via droptable.com" <forum@.droptable.com> wrote in message
news:541010E0E3B40@.droptable.com...
> Hello to Everybody!
> I have a doubts about Transaction Log. What's happen when I execute the
> follow command
> BACKUP LOG [database] WITH NO_LOG ou BACKUP LOG [database] WITH TRUNCATE_ONLY
> So, When should I use this command to avoid fill up the log?
> Thanks a Lot
> Juliano Horta
|||Only use this if you do not need to be recoverable via trans log, if so
maybe you should just use simple recovery mode
Below is from BOL
Note If backing up the log does not appear to truncate most of the log, an
old open transaction may exist in the log. Log space can be monitored with
DBCC SQLPERF (LOGSPACE). For more information, see Transaction Log Backups.
NO_LOG | TRUNCATE_ONLY
Removes the inactive part of the log without making a backup copy of it and
truncates the log. This option frees space. Specifying a backup device is
unnecessary because the log backup is not saved. NO_LOG and TRUNCATE_ONLY
are synonyms.
After backing up the log using either NO_LOG or TRUNCATE_ONLY, the changes
recorded in the log are not recoverable. For recovery purposes, immediately
execute BACKUP DATABASE.
"Juliano H via droptable.com" <forum@.droptable.com> wrote in message
news:541010E0E3B40@.droptable.com...
> Hello to Everybody!
> I have a doubts about Transaction Log. What's happen when I execute the
> follow command
> BACKUP LOG [database] WITH NO_LOG ou BACKUP LOG [database] WITH
> TRUNCATE_ONLY
> So, When should I use this command to avoid fill up the log?
> Thanks a Lot
> Juliano Horta
|||Hi,
To add on to Tibor and David; Go ahead with SIMPLE recovery model if you do
not require a point in time recovery.
There is no difference between NO_LOG and TRUNCATE_ONLY. Both are same and
will truncate the inactive
portion of the log.
Thanks
Hari
SQL Server MVP
"David J. Cartwright" <davidcartwright@.hotmail.com> wrote in message
news:uYKNlZKtFHA.3080@.TK2MSFTNGP15.phx.gbl...
> Only use this if you do not need to be recoverable via trans log, if so
> maybe you should just use simple recovery mode
>
> Below is from BOL
>
> Note If backing up the log does not appear to truncate most of the log,
> an old open transaction may exist in the log. Log space can be monitored
> with DBCC SQLPERF (LOGSPACE). For more information, see Transaction Log
> Backups.
>
> NO_LOG | TRUNCATE_ONLY
> Removes the inactive part of the log without making a backup copy of it
> and truncates the log. This option frees space. Specifying a backup device
> is unnecessary because the log backup is not saved. NO_LOG and
> TRUNCATE_ONLY are synonyms.
> After backing up the log using either NO_LOG or TRUNCATE_ONLY, the changes
> recorded in the log are not recoverable. For recovery purposes,
> immediately execute BACKUP DATABASE.
>
> "Juliano H via droptable.com" <forum@.droptable.com> wrote in message
> news:541010E0E3B40@.droptable.com...
>

Doubts about Transaction Log

Hello to Everybody!
I have a doubts about Transaction Log. What's happen when I execute the
follow command
BACKUP LOG [database] WITH NO_LOG ou BACKUP LOG [database] WITH TRUNCATE_ONLY
So, When should I use this command to avoid fill up the log?
Thanks a Lot
Juliano HortaDon't use it. Either have the db in simple recovery mode. Or do regular transaction log backups (the
log is emptied when you do a log backup).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Juliano H via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:541010E0E3B40@.SQLMonster.com...
> Hello to Everybody!
> I have a doubts about Transaction Log. What's happen when I execute the
> follow command
> BACKUP LOG [database] WITH NO_LOG ou BACKUP LOG [database] WITH TRUNCATE_ONLY
> So, When should I use this command to avoid fill up the log?
> Thanks a Lot
> Juliano Horta|||Only use this if you do not need to be recoverable via trans log, if so
maybe you should just use simple recovery mode
Below is from BOL
Note If backing up the log does not appear to truncate most of the log, an
old open transaction may exist in the log. Log space can be monitored with
DBCC SQLPERF (LOGSPACE). For more information, see Transaction Log Backups.
NO_LOG | TRUNCATE_ONLY
Removes the inactive part of the log without making a backup copy of it and
truncates the log. This option frees space. Specifying a backup device is
unnecessary because the log backup is not saved. NO_LOG and TRUNCATE_ONLY
are synonyms.
After backing up the log using either NO_LOG or TRUNCATE_ONLY, the changes
recorded in the log are not recoverable. For recovery purposes, immediately
execute BACKUP DATABASE.
"Juliano H via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:541010E0E3B40@.SQLMonster.com...
> Hello to Everybody!
> I have a doubts about Transaction Log. What's happen when I execute the
> follow command
> BACKUP LOG [database] WITH NO_LOG ou BACKUP LOG [database] WITH
> TRUNCATE_ONLY
> So, When should I use this command to avoid fill up the log?
> Thanks a Lot
> Juliano Horta|||Hi,
To add on to Tibor and David; Go ahead with SIMPLE recovery model if you do
not require a point in time recovery.
There is no difference between NO_LOG and TRUNCATE_ONLY. Both are same and
will truncate the inactive
portion of the log.
Thanks
Hari
SQL Server MVP
"David J. Cartwright" <davidcartwright@.hotmail.com> wrote in message
news:uYKNlZKtFHA.3080@.TK2MSFTNGP15.phx.gbl...
> Only use this if you do not need to be recoverable via trans log, if so
> maybe you should just use simple recovery mode
>
> Below is from BOL
>
> Note If backing up the log does not appear to truncate most of the log,
> an old open transaction may exist in the log. Log space can be monitored
> with DBCC SQLPERF (LOGSPACE). For more information, see Transaction Log
> Backups.
>
> NO_LOG | TRUNCATE_ONLY
> Removes the inactive part of the log without making a backup copy of it
> and truncates the log. This option frees space. Specifying a backup device
> is unnecessary because the log backup is not saved. NO_LOG and
> TRUNCATE_ONLY are synonyms.
> After backing up the log using either NO_LOG or TRUNCATE_ONLY, the changes
> recorded in the log are not recoverable. For recovery purposes,
> immediately execute BACKUP DATABASE.
>
> "Juliano H via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
> news:541010E0E3B40@.SQLMonster.com...
>> Hello to Everybody!
>> I have a doubts about Transaction Log. What's happen when I execute the
>> follow command
>> BACKUP LOG [database] WITH NO_LOG ou BACKUP LOG [database] WITH
>> TRUNCATE_ONLY
>> So, When should I use this command to avoid fill up the log?
>> Thanks a Lot
>> Juliano Horta
>

Doubts about SQL-DMO

Hello, All!
I've saw many information and commands about SQL-DMO, but I don't know what's
is this and how to use it yet. Could you please explain me how to use and
when is better to use this kind of command?
Thanks
Juliano Horta
Message posted via http://www.droptable.com
Its a way to administer SQL Server programmatically.
HTH; Jens Suessmeyer.

Doubts about SQL-DMO

Hello, All!
I've saw many information and commands about SQL-DMO, but I don't know what's
is this and how to use it yet. Could you please explain me how to use and
when is better to use this kind of command?
Thanks
Juliano Horta
--
Message posted via http://www.sqlmonster.comIts a way to administer SQL Server programmatically.
HTH; Jens Suessmeyer.

Doubts about SQL-DMO

Hello, All!
I've saw many information and commands about SQL-DMO, but I don't know what'
s
is this and how to use it yet. Could you please explain me how to use and
when is better to use this kind of command?
Thanks
Juliano Horta
Message posted via http://www.droptable.comIts a way to administer SQL Server programmatically.
HTH; Jens Suessmeyer.

Doubts about sp_spaceused

Hello, All!
I'm making a maintenance in my DataBases and I have doubts about somethings.
Could you help me?
One of my DataBases, the DataFile has 1,8GB and the LOG File has 400MB. I
executed Shrink DataBase and my DataBases fell down to 700MB.
But, When I execute the Stored Procedure sp_spaceused, it comes for
unallocated space -1050MB.
What's mean?
What I need to do to revert it? The other information when I run sp_spaceused
is:
DataBase
BDSeg_Bosch
DataBase size: 700MB
Unallocated space: -1050MB
reserved: 1691176 KB
data: 225336 KB
index_size: 1442216 KB
unused: 23624 KB
Thanks
Juliano Horta
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200603/1
Run:
DBCC UPDATEUSAGE (0)
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"julianohorta via droptable.com" <u13014@.uwe> wrote in message
news:5dfad6bddc673@.uwe...
Hello, All!
I'm making a maintenance in my DataBases and I have doubts about somethings.
Could you help me?
One of my DataBases, the DataFile has 1,8GB and the LOG File has 400MB. I
executed Shrink DataBase and my DataBases fell down to 700MB.
But, When I execute the Stored Procedure sp_spaceused, it comes for
unallocated space -1050MB.
What's mean?
What I need to do to revert it? The other information when I run
sp_spaceused
is:
DataBase
BDSeg_Bosch
DataBase size: 700MB
Unallocated space: -1050MB
reserved: 1691176 KB
data: 225336 KB
index_size: 1442216 KB
unused: 23624 KB
Thanks
Juliano Horta
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200603/1
|||Did you run DBCC UPDATEUSAGE command before running sp_spaceused?
"julianohorta via droptable.com" <u13014@.uwe> wrote in message
news:5dfad6bddc673@.uwe...
> Hello, All!
> I'm making a maintenance in my DataBases and I have doubts about
> somethings.
> Could you help me?
> One of my DataBases, the DataFile has 1,8GB and the LOG File has 400MB. I
> executed Shrink DataBase and my DataBases fell down to 700MB.
> But, When I execute the Stored Procedure sp_spaceused, it comes for
> unallocated space -1050MB.
> What's mean?
> What I need to do to revert it? The other information when I run
> sp_spaceused
> is:
> DataBase
> BDSeg_Bosch
> DataBase size: 700MB
> Unallocated space: -1050MB
> reserved: 1691176 KB
> data: 225336 KB
> index_size: 1442216 KB
> unused: 23624 KB
> Thanks
> Juliano Horta
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200603/1

Doubts about sp_spaceused

Hello, All!
I'm making a maintenance in my DataBases and I have doubts about somethings.
Could you help me?
One of my DataBases, the DataFile has 1,8GB and the LOG File has 400MB. I
executed Shrink DataBase and my DataBases fell down to 700MB.
But, When I execute the Stored Procedure sp_spaceused, it comes for
unallocated space -1050MB.
What's mean?
What I need to do to revert it? The other information when I run sp_spaceused
is:
DataBase
BDSeg_Bosch
DataBase size: 700MB
Unallocated space: -1050MB
reserved: 1691176 KB
data: 225336 KB
index_size: 1442216 KB
unused: 23624 KB
Thanks
Juliano Horta
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200603/1Run:
DBCC UPDATEUSAGE (0)
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"julianohorta via SQLMonster.com" <u13014@.uwe> wrote in message
news:5dfad6bddc673@.uwe...
Hello, All!
I'm making a maintenance in my DataBases and I have doubts about somethings.
Could you help me?
One of my DataBases, the DataFile has 1,8GB and the LOG File has 400MB. I
executed Shrink DataBase and my DataBases fell down to 700MB.
But, When I execute the Stored Procedure sp_spaceused, it comes for
unallocated space -1050MB.
What's mean?
What I need to do to revert it? The other information when I run
sp_spaceused
is:
DataBase
BDSeg_Bosch
DataBase size: 700MB
Unallocated space: -1050MB
reserved: 1691176 KB
data: 225336 KB
index_size: 1442216 KB
unused: 23624 KB
Thanks
Juliano Horta
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200603/1|||Did you run DBCC UPDATEUSAGE command before running sp_spaceused?
"julianohorta via SQLMonster.com" <u13014@.uwe> wrote in message
news:5dfad6bddc673@.uwe...
> Hello, All!
> I'm making a maintenance in my DataBases and I have doubts about
> somethings.
> Could you help me?
> One of my DataBases, the DataFile has 1,8GB and the LOG File has 400MB. I
> executed Shrink DataBase and my DataBases fell down to 700MB.
> But, When I execute the Stored Procedure sp_spaceused, it comes for
> unallocated space -1050MB.
> What's mean?
> What I need to do to revert it? The other information when I run
> sp_spaceused
> is:
> DataBase
> BDSeg_Bosch
> DataBase size: 700MB
> Unallocated space: -1050MB
> reserved: 1691176 KB
> data: 225336 KB
> index_size: 1442216 KB
> unused: 23624 KB
> Thanks
> Juliano Horta
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200603/1

Doubts about sp_spaceused

Hello, All!
I'm making a maintenance in my DataBases and I have doubts about somethings.
Could you help me?
One of my DataBases, the DataFile has 1,8GB and the LOG File has 400MB. I
executed Shrink DataBase and my DataBases fell down to 700MB.
But, When I execute the Stored Procedure sp_spaceused, it comes for
unallocated space -1050MB.
What's mean?
What I need to do to revert it? The other information when I run sp_spaceuse
d
is:
DataBase
BDSeg_Bosch
DataBase size: 700MB
Unallocated space: -1050MB
reserved: 1691176 KB
data: 225336 KB
index_size: 1442216 KB
unused: 23624 KB
Thanks
Juliano Horta
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200603/1Run:
DBCC UPDATEUSAGE (0)
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"julianohorta via droptable.com" <u13014@.uwe> wrote in message
news:5dfad6bddc673@.uwe...
Hello, All!
I'm making a maintenance in my DataBases and I have doubts about somethings.
Could you help me?
One of my DataBases, the DataFile has 1,8GB and the LOG File has 400MB. I
executed Shrink DataBase and my DataBases fell down to 700MB.
But, When I execute the Stored Procedure sp_spaceused, it comes for
unallocated space -1050MB.
What's mean?
What I need to do to revert it? The other information when I run
sp_spaceused
is:
DataBase
BDSeg_Bosch
DataBase size: 700MB
Unallocated space: -1050MB
reserved: 1691176 KB
data: 225336 KB
index_size: 1442216 KB
unused: 23624 KB
Thanks
Juliano Horta
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200603/1|||Did you run DBCC UPDATEUSAGE command before running sp_spaceused?
"julianohorta via droptable.com" <u13014@.uwe> wrote in message
news:5dfad6bddc673@.uwe...
> Hello, All!
> I'm making a maintenance in my DataBases and I have doubts about
> somethings.
> Could you help me?
> One of my DataBases, the DataFile has 1,8GB and the LOG File has 400MB. I
> executed Shrink DataBase and my DataBases fell down to 700MB.
> But, When I execute the Stored Procedure sp_spaceused, it comes for
> unallocated space -1050MB.
> What's mean?
> What I need to do to revert it? The other information when I run
> sp_spaceused
> is:
> DataBase
> BDSeg_Bosch
> DataBase size: 700MB
> Unallocated space: -1050MB
> reserved: 1691176 KB
> data: 225336 KB
> index_size: 1442216 KB
> unused: 23624 KB
> Thanks
> Juliano Horta
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200603/1

doubts about report deployment

hi all

i have doubts abt report deployment

if i am deploying report then what process exactly happens?

also is any entry made in IIS or is any new file created in IIS?

if i am deploying report on remote server then what process exactly happens?

what r the entries or files that r created on remote server?

plz help me so that i will understand this deployment process very clearly.

waiting for reply.

When you deploy a report to the Report Server it is not storing a file in the webserver. The report is actually stored a binary blob in the reporting services database. This is really cool, because it means that all you have to do is restore your ssrs database if there is a problem.

|||

thanks for helping me in understanding this concept

it is really great.

but i still have some doubt, if i am deleting actual .rdl file of report that i have deployed will report still be executed?

plz reply.

& thanks again

|||Now you've got me confused. How can you delete an .RDL file that's stored inside of a database? If you are deleting the file out of your Report Project, and you have already deployed it. As far as I know it will still be in the Reporting Server database.|||

Note: since the original .RDL file is also stored in the database, you can retrieve the .RDL file from the published report on the report server e.g. in report manager, report properties, edit report definition.

-- Robert

doubt about sqlserver data types

I'm working with sqlserver express 2005, and I have a lot of doubts about what sqlserver data types use. More exactly my doubt is about text types... nchar, nvarchar, varchar... what are the differences?

thanks.::More exactly my doubt is about text types... nchar, nvarchar, varchar... what are the
::differences?

I really hate to tell you, but there is a documentation for SQL Server that has exact definitions of every data type.