I have a database that was created in SQL Server 2000. Would there be any
issues if I used this database in MSDE? Does anyone know of any document
regarding this? All the articles I have read talk about MSDE databases being
compatible with SQL Server 2000. None of them discussed the reverse case.
Thanks in advance!MSDE and SQL Server is the same. There are some features not available on MSDE, but I doubt you will
run into them...
http://msdn.microsoft.com/library/en-us/architec/8_ar_ts_1cdv.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Anushree Laturkar" <anushree.laturkar@.bindview.com> wrote in message
news:ubDnKkx7EHA.2608@.TK2MSFTNGP10.phx.gbl...
>I have a database that was created in SQL Server 2000. Would there be any
> issues if I used this database in MSDE? Does anyone know of any document
> regarding this? All the articles I have read talk about MSDE databases being
> compatible with SQL Server 2000. None of them discussed the reverse case.
> Thanks in advance!
>|||As long as you are talking about MSDE 2.0, not the MSDE 1.0 that came out
with SS 7.0.
Out of curiosity, why would you want to revert back like this? If you are
looking at a development platform, why not deploy SS Developer Edition.
Microsoft has recently dropped the price on this edition down to $50 and you
get the full Enterprise Edition for development purposes without any sort of
throttles or restrictions.
Sincerely,
Anthony Thomas
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23tq6A8y7EHA.3236@.TK2MSFTNGP15.phx.gbl...
MSDE and SQL Server is the same. There are some features not available on
MSDE, but I doubt you will
run into them...
http://msdn.microsoft.com/library/en-us/architec/8_ar_ts_1cdv.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Anushree Laturkar" <anushree.laturkar@.bindview.com> wrote in message
news:ubDnKkx7EHA.2608@.TK2MSFTNGP10.phx.gbl...
>I have a database that was created in SQL Server 2000. Would there be any
> issues if I used this database in MSDE? Does anyone know of any document
> regarding this? All the articles I have read talk about MSDE databases
being
> compatible with SQL Server 2000. None of them discussed the reverse case.
> Thanks in advance!
>sql
Showing posts with label document. Show all posts
Showing posts with label document. Show all posts
Thursday, March 29, 2012
Saturday, February 25, 2012
Data XML file to SQL Server Table...
Hi,
I have the following XML document, which I want to put into SQL Server 2000 Table. How can I do that? The table name is "Orders". I am using C#.
<Order>
<Date>2007/09/02</Date>
<OrderID>200</OrderID>
<PartNumber id = “ABC10”>
<Delivery_Date>
</Delivery Date>
<Delivery_Quanity>
</Delivery_Quanity>
<Price>
</Price>
</PartNumber>
<PartNumber id = “ABC98”>
<Delivery_Date>
</Delivery Date>
<Delivery_Quanity>
</Delivery_Quanity>
<Price>
</Price>
</PartNumber>
<PartNumber id = “ABC11”>
<Delivery_Date>
</Delivery Date>
<Delivery_Quanity>
</Delivery_Quanity>
<Price>
</Price>
</PartNumber>
</Order>
Any help would be highly appreciated...
Regards,
Hi again,
Just to explain my question again,
I want the table to look like the following,
Orders:
Auto: Date: OrderID: Partnumber: Delivery_Date: Delivery_Quantity: Price:
0001 2007/09/02 200 ABC10 0 1 0
0002 2007/09/02 200 ABC10 0 2 0
0003 2007/09/02 200 ABC98 0 56 0
0004 2007/09/02 200 ABC11 0 34 0
Orders.XML
<Order>
<Date>2007/09/02</Date>
<OrderID>200</OrderID>
<PartNumber id = “ABC10”>
<Delivery_Date> <!--Can have multiple Delivery_Date, Delivery_Quantity and Price-->
</Delivery Date>
<Delivery_Quanity>
1
</Delivery_Quanity>
<Price>
</Price>
<Delivery_Date> <!--Can have multiple Delivery_Date, Delivery_Quantity and Price-->
</Delivery Date>
<Delivery_Quanity>
2
</Delivery_Quanity>
<Price>
</Price>
</PartNumber>
<PartNumber id = “ABC98”>
<Delivery_Date>
</Delivery Date>
<Delivery_Quanity>
56
</Delivery_Quanity>
<Price>
</Price>
</PartNumber>
<PartNumber id = “ABC11”>
<Delivery_Date>
</Delivery Date>
<Delivery_Quanity>
34
</Delivery_Quanity>
<Price>
</Price>
</PartNumber>
</Order>
Regards,
Friday, February 24, 2012
Data Types
Hello, Is there any document that tells you the pro/cons for using one data
type over another? I just recently upgraded from Access to SQL Server 2000.
I used the Access upgrade wizard and was wondering how it determines when to
assign types to ntext or text. Also, if the character in the text field are
less than 2000 should I convert this field to say varchar(2000) or
nvarchar(2000)?
Thanks
DonIf you need unicode then nvarchar else varchar.
Don't use text unles the field could go over 8000 chars (4000 for nvarchar).
Always review what the upgrade wizard has done - it makes all text fields nvarchar I think which is not good.
It's usually a good time to review the database design.
"Don" wrote:
> Hello, Is there any document that tells you the pro/cons for using one data
> type over another? I just recently upgraded from Access to SQL Server 2000.
> I used the Access upgrade wizard and was wondering how it determines when to
> assign types to ntext or text. Also, if the character in the text field are
> less than 2000 should I convert this field to say varchar(2000) or
> nvarchar(2000)?
> Thanks
> Don
>
>|||As Nigel says, review the actual needs, because the upgrade wizard seems to
choose large datatypes... If a tinyint will do , do not use an int or
smallint...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Don" <dons100@.ameritech.net> wrote in message
news:lCkDc.1791$kK4.474@.newssvr16.news.prodigy.com...
> Hello, Is there any document that tells you the pro/cons for using one
data
> type over another? I just recently upgraded from Access to SQL Server
2000.
> I used the Access upgrade wizard and was wondering how it determines when
to
> assign types to ntext or text. Also, if the character in the text field
are
> less than 2000 should I convert this field to say varchar(2000) or
> nvarchar(2000)?
> Thanks
> Don
>
type over another? I just recently upgraded from Access to SQL Server 2000.
I used the Access upgrade wizard and was wondering how it determines when to
assign types to ntext or text. Also, if the character in the text field are
less than 2000 should I convert this field to say varchar(2000) or
nvarchar(2000)?
Thanks
DonIf you need unicode then nvarchar else varchar.
Don't use text unles the field could go over 8000 chars (4000 for nvarchar).
Always review what the upgrade wizard has done - it makes all text fields nvarchar I think which is not good.
It's usually a good time to review the database design.
"Don" wrote:
> Hello, Is there any document that tells you the pro/cons for using one data
> type over another? I just recently upgraded from Access to SQL Server 2000.
> I used the Access upgrade wizard and was wondering how it determines when to
> assign types to ntext or text. Also, if the character in the text field are
> less than 2000 should I convert this field to say varchar(2000) or
> nvarchar(2000)?
> Thanks
> Don
>
>|||As Nigel says, review the actual needs, because the upgrade wizard seems to
choose large datatypes... If a tinyint will do , do not use an int or
smallint...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Don" <dons100@.ameritech.net> wrote in message
news:lCkDc.1791$kK4.474@.newssvr16.news.prodigy.com...
> Hello, Is there any document that tells you the pro/cons for using one
data
> type over another? I just recently upgraded from Access to SQL Server
2000.
> I used the Access upgrade wizard and was wondering how it determines when
to
> assign types to ntext or text. Also, if the character in the text field
are
> less than 2000 should I convert this field to say varchar(2000) or
> nvarchar(2000)?
> Thanks
> Don
>
Data Types
Hello, Is there any document that tells you the pro/cons for using one data
type over another? I just recently upgraded from Access to SQL Server 2000.
I used the Access upgrade wizard and was wondering how it determines when to
assign types to ntext or text. Also, if the character in the text field are
less than 2000 should I convert this field to say varchar(2000) or
nvarchar(2000)?
Thanks
DonIf you need unicode then nvarchar else varchar.
Don't use text unles the field could go over 8000 chars (4000 for nvarchar).
Always review what the upgrade wizard has done - it makes all text fields nv
archar I think which is not good.
It's usually a good time to review the database design.
"Don" wrote:
> Hello, Is there any document that tells you the pro/cons for using one dat
a
> type over another? I just recently upgraded from Access to SQL Server 200
0.
> I used the Access upgrade wizard and was wondering how it determines when
to
> assign types to ntext or text. Also, if the character in the text field a
re
> less than 2000 should I convert this field to say varchar(2000) or
> nvarchar(2000)?
> Thanks
> Don
>
>|||As Nigel says, review the actual needs, because the upgrade wizard seems to
choose large datatypes... If a tinyint will do , do not use an int or
smallint...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Don" <dons100@.ameritech.net> wrote in message
news:lCkDc.1791$kK4.474@.newssvr16.news.prodigy.com...
> Hello, Is there any document that tells you the pro/cons for using one
data
> type over another? I just recently upgraded from Access to SQL Server
2000.
> I used the Access upgrade wizard and was wondering how it determines when
to
> assign types to ntext or text. Also, if the character in the text field
are
> less than 2000 should I convert this field to say varchar(2000) or
> nvarchar(2000)?
> Thanks
> Don
>
type over another? I just recently upgraded from Access to SQL Server 2000.
I used the Access upgrade wizard and was wondering how it determines when to
assign types to ntext or text. Also, if the character in the text field are
less than 2000 should I convert this field to say varchar(2000) or
nvarchar(2000)?
Thanks
DonIf you need unicode then nvarchar else varchar.
Don't use text unles the field could go over 8000 chars (4000 for nvarchar).
Always review what the upgrade wizard has done - it makes all text fields nv
archar I think which is not good.
It's usually a good time to review the database design.
"Don" wrote:
> Hello, Is there any document that tells you the pro/cons for using one dat
a
> type over another? I just recently upgraded from Access to SQL Server 200
0.
> I used the Access upgrade wizard and was wondering how it determines when
to
> assign types to ntext or text. Also, if the character in the text field a
re
> less than 2000 should I convert this field to say varchar(2000) or
> nvarchar(2000)?
> Thanks
> Don
>
>|||As Nigel says, review the actual needs, because the upgrade wizard seems to
choose large datatypes... If a tinyint will do , do not use an int or
smallint...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Don" <dons100@.ameritech.net> wrote in message
news:lCkDc.1791$kK4.474@.newssvr16.news.prodigy.com...
> Hello, Is there any document that tells you the pro/cons for using one
data
> type over another? I just recently upgraded from Access to SQL Server
2000.
> I used the Access upgrade wizard and was wondering how it determines when
to
> assign types to ntext or text. Also, if the character in the text field
are
> less than 2000 should I convert this field to say varchar(2000) or
> nvarchar(2000)?
> Thanks
> Don
>
Data Types
Hello, I am following this article about building an ASP.Net application which uses SQL Express 2005. The document calls for building a couple of tables. One column is identified with data type of "Byte" which are is available for selection within the Visual Studio 2005 interface. The following values show in the drop down of data type in VS2005:
Bigint
Binary(5)
Bit
Char(10)
DateTime
Decimal (18,0)
Float
Image
Int
Money
NChar(10)
NText
Numeric(18,0)
Nvarchar(50)
Nvarchar(max)
Real
SmallDateTime
SmallInt
SmallMoney
Sql_Variant
Text
Timestamp
TinyInt
UniqueIdentifier
Varbinary(50)
VarBinary(max)
varchar(10)
Varchar(max)
XML
I choose Char with a size of 1. Would this be correct, or am I missing something?
Thanks in advance for your assistance!!
SqlByte maps to tinyint.Data Types
Hello, Is there any document that tells you the pro/cons for using one data
type over another? I just recently upgraded from Access to SQL Server 2000.
I used the Access upgrade wizard and was wondering how it determines when to
assign types to ntext or text. Also, if the character in the text field are
less than 2000 should I convert this field to say varchar(2000) or
nvarchar(2000)?
Thanks
Don
If you need unicode then nvarchar else varchar.
Don't use text unles the field could go over 8000 chars (4000 for nvarchar).
Always review what the upgrade wizard has done - it makes all text fields nvarchar I think which is not good.
It's usually a good time to review the database design.
"Don" wrote:
> Hello, Is there any document that tells you the pro/cons for using one data
> type over another? I just recently upgraded from Access to SQL Server 2000.
> I used the Access upgrade wizard and was wondering how it determines when to
> assign types to ntext or text. Also, if the character in the text field are
> less than 2000 should I convert this field to say varchar(2000) or
> nvarchar(2000)?
> Thanks
> Don
>
>
|||As Nigel says, review the actual needs, because the upgrade wizard seems to
choose large datatypes... If a tinyint will do , do not use an int or
smallint...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Don" <dons100@.ameritech.net> wrote in message
news:lCkDc.1791$kK4.474@.newssvr16.news.prodigy.com ...
> Hello, Is there any document that tells you the pro/cons for using one
data
> type over another? I just recently upgraded from Access to SQL Server
2000.
> I used the Access upgrade wizard and was wondering how it determines when
to
> assign types to ntext or text. Also, if the character in the text field
are
> less than 2000 should I convert this field to say varchar(2000) or
> nvarchar(2000)?
> Thanks
> Don
>
|||As Nigel says, review the actual needs, because the upgrade wizard seems to
choose large datatypes... If a tinyint will do , do not use an int or
smallint...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Don" <dons100@.ameritech.net> wrote in message
news:lCkDc.1791$kK4.474@.newssvr16.news.prodigy.com ...
> Hello, Is there any document that tells you the pro/cons for using one
data
> type over another? I just recently upgraded from Access to SQL Server
2000.
> I used the Access upgrade wizard and was wondering how it determines when
to
> assign types to ntext or text. Also, if the character in the text field
are
> less than 2000 should I convert this field to say varchar(2000) or
> nvarchar(2000)?
> Thanks
> Don
>
type over another? I just recently upgraded from Access to SQL Server 2000.
I used the Access upgrade wizard and was wondering how it determines when to
assign types to ntext or text. Also, if the character in the text field are
less than 2000 should I convert this field to say varchar(2000) or
nvarchar(2000)?
Thanks
Don
If you need unicode then nvarchar else varchar.
Don't use text unles the field could go over 8000 chars (4000 for nvarchar).
Always review what the upgrade wizard has done - it makes all text fields nvarchar I think which is not good.
It's usually a good time to review the database design.
"Don" wrote:
> Hello, Is there any document that tells you the pro/cons for using one data
> type over another? I just recently upgraded from Access to SQL Server 2000.
> I used the Access upgrade wizard and was wondering how it determines when to
> assign types to ntext or text. Also, if the character in the text field are
> less than 2000 should I convert this field to say varchar(2000) or
> nvarchar(2000)?
> Thanks
> Don
>
>
|||As Nigel says, review the actual needs, because the upgrade wizard seems to
choose large datatypes... If a tinyint will do , do not use an int or
smallint...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Don" <dons100@.ameritech.net> wrote in message
news:lCkDc.1791$kK4.474@.newssvr16.news.prodigy.com ...
> Hello, Is there any document that tells you the pro/cons for using one
data
> type over another? I just recently upgraded from Access to SQL Server
2000.
> I used the Access upgrade wizard and was wondering how it determines when
to
> assign types to ntext or text. Also, if the character in the text field
are
> less than 2000 should I convert this field to say varchar(2000) or
> nvarchar(2000)?
> Thanks
> Don
>
|||As Nigel says, review the actual needs, because the upgrade wizard seems to
choose large datatypes... If a tinyint will do , do not use an int or
smallint...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Don" <dons100@.ameritech.net> wrote in message
news:lCkDc.1791$kK4.474@.newssvr16.news.prodigy.com ...
> Hello, Is there any document that tells you the pro/cons for using one
data
> type over another? I just recently upgraded from Access to SQL Server
2000.
> I used the Access upgrade wizard and was wondering how it determines when
to
> assign types to ntext or text. Also, if the character in the text field
are
> less than 2000 should I convert this field to say varchar(2000) or
> nvarchar(2000)?
> Thanks
> Don
>
Sunday, February 19, 2012
Data type for storing MS Word documents/large data type?
Hi all,
I am bginning to build a SQL Server database that will be used to store
documents from various users. The document types will mostly be MS Word and
MS PowerPoint. I want to know what datatype to use in the database to store
these kinds of documents.
The data will be fed to SQL Server via an ASP.Net-based website. I would
also like to know if I can just use standard ASP.Net database objects to
transfer these large amounts of data.
Many thanks for any advice or a point in the right direction.
JustinHave you done any research on the pros and cons of storing the documents in
the database, vs. using a file system? It is going to be much more
efficient to store the *paths* to the files in the database. Have a read:
http://www.aspfaq.com/2149
"Justin Little" <JustinLittle@.discussions.microsoft.com> wrote in message
news:E4D7888D-C902-4B9F-AE6A-7A8FB2F6C921@.microsoft.com...
> Hi all,
> I am bginning to build a SQL Server database that will be used to store
> documents from various users. The document types will mostly be MS Word
> and
> MS PowerPoint. I want to know what datatype to use in the database to
> store
> these kinds of documents.
> The data will be fed to SQL Server via an ASP.Net-based website. I would
> also like to know if I can just use standard ASP.Net database objects to
> transfer these large amounts of data.
> Many thanks for any advice or a point in the right direction.
> Justin
>
I am bginning to build a SQL Server database that will be used to store
documents from various users. The document types will mostly be MS Word and
MS PowerPoint. I want to know what datatype to use in the database to store
these kinds of documents.
The data will be fed to SQL Server via an ASP.Net-based website. I would
also like to know if I can just use standard ASP.Net database objects to
transfer these large amounts of data.
Many thanks for any advice or a point in the right direction.
JustinHave you done any research on the pros and cons of storing the documents in
the database, vs. using a file system? It is going to be much more
efficient to store the *paths* to the files in the database. Have a read:
http://www.aspfaq.com/2149
"Justin Little" <JustinLittle@.discussions.microsoft.com> wrote in message
news:E4D7888D-C902-4B9F-AE6A-7A8FB2F6C921@.microsoft.com...
> Hi all,
> I am bginning to build a SQL Server database that will be used to store
> documents from various users. The document types will mostly be MS Word
> and
> MS PowerPoint. I want to know what datatype to use in the database to
> store
> these kinds of documents.
> The data will be fed to SQL Server via an ASP.Net-based website. I would
> also like to know if I can just use standard ASP.Net database objects to
> transfer these large amounts of data.
> Many thanks for any advice or a point in the right direction.
> Justin
>
Subscribe to:
Posts (Atom)