MSDTC and Win2K3: version

Showing posts with label version. Show all posts

Friday, March 23, 2012

MSQL Server Version with service pack

I just installed sp3 from micrsofot. how I would know that which service pack I have installed on MSSQL 2000.
thanks for help in advance.
KMType SELECT @.@.Version in the query analyzer and it will tell you all the version info on your SQL Server.|||Or you may go to Enterprise Manager and Right Click on the Server--Properties and under the Gereral Tab it gives you the SP information.

SQL 2000----No SP--8.00.194
SQL 2000------SP1--8.00.384
SQL 2000------SP2--8.00.534
SQL 2000------SP3--8.00.760|||I must say I had a devil of a time connecting to remote sites with ent manager. Until I finally installed sp3 - now I connect up with ease. must of been some bug in the software (winXP) sql server2k that the sp3 fixes.

MSOLAP.DLL Version Numbers

I have been trying to install some third party software that checks for
pre-requisite software in my computer. The third party software is
returning the following diagnostic result (saying I do not heve the correct version of PTS).
Microsoft PivotTable Service 2000
Required: OLAP Server 8.0.986.0
Currently: OLAP Server 8.0.760.0
Status: Error

It is my understanding that "PTS" is MSOLAP.DLL.

I have Analysis Server 2000 SP3 installed and all appears OK.
According to other posts in this group, the correct version of
msolap.dll (pivot table services) for SP3 and SP3A is 8.0.760.0.

My version of msolap.dll currently installed is 8.0.2039.0, which I
believe to be the SP4 version of PTS

The third party software is searching for a version 8.0.986.0.
Nowhere in the MSDN world can I find ANY mention of 8.0.986.0 as a
version number of anything.

Is this an error in the third party diagnostic?
Where would they possibly be getting that version number (8.0.986.0)?
What do you think they are looking at when they say "OLAP SERVER"

The third party support people are saying I must uninstall Analysis

Server 2000 and then download and install PTSFullSP4.exe. I am not

prepared to take so drastic a step, especially given the strange

Product Titles and version numbers they are looking for.
Can anyone shed some light on this issue?

Version 8.00.2039 corresponds to the service pack 4 of SQL Server 2000.

So looks like you've got SP4 of PTS installed and not SP3.

From the error message it looks like the software you trying to install requires SP4 version of Analysis Server.

You can try and run SP4 setup for Analysis Services from

http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-99a9-b7f0213f8bc5&DisplayLang=en

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

msmqtask.dll

I tried to install the ENT edition of 2005, the release version. I continue to get an error stating the the install was unable to build the type lib for Microsoft.SqlServer.MsmqTask.dll.

I tried multiple uninstalls scenaios, including cleaning the registry, cleaning the file system, using the cleanup tool from the CTP, and I uninstalled MSMQ.

I can not seem to find my way out of this bag. The net result is that I can not import an existing Database. At least that's the first problem I found.

This is an issue when Microsoft.SqlServer.MSMQTask is left behind in COM+ catalog. You can workaround it by:

1. Open Administrative Tools\Component Services

2. Go to Component Services\Computers\My Computer\COM+ Applications

3. Delete Microsoft.SqlServer.MSMQTask

|||

And what if you get this error and the Microsoft.SqlServer.MSMQTask is not there?

I clicked on ignore eventually, but this should not be ok.

msmqtask.dll

I tried to install the ENT edition of 2005, the release version. I continue to get an error stating the the install was unable to build the type lib for Microsoft.SqlServer.MsmqTask.dll.

I tried multiple uninstalls scenaios, including cleaning the registry, cleaning the file system, using the cleanup tool from the CTP, and I uninstalled MSMQ.

I can not seem to find my way out of this bag. The net result is that I can not import an existing Database. At least that's the first problem I found.

This is an issue when Microsoft.SqlServer.MSMQTask is left behind in COM+ catalog. You can workaround it by:

1. Open Administrative Tools\Component Services

2. Go to Component Services\Computers\My Computer\COM+ Applications

3. Delete Microsoft.SqlServer.MSMQTask

|||

And what if you get this error and the Microsoft.SqlServer.MSMQTask is not there?

I clicked on ignore eventually, but this should not be ok.

msmqtask.dll

I tried to install the ENT edition of 2005, the release version. I continue to get an error stating the the install was unable to build the type lib for Microsoft.SqlServer.MsmqTask.dll.

I tried multiple uninstalls scenaios, including cleaning the registry, cleaning the file system, using the cleanup tool from the CTP, and I uninstalled MSMQ.

I can not seem to find my way out of this bag. The net result is that I can not import an existing Database. At least that's the first problem I found.

This is an issue when Microsoft.SqlServer.MSMQTask is left behind in COM+ catalog. You can workaround it by:

1. Open Administrative Tools\Component Services

2. Go to Component Services\Computers\My Computer\COM+ Applications

3. Delete Microsoft.SqlServer.MSMQTask

|||

And what if you get this error and the Microsoft.SqlServer.MSMQTask is not there?

I clicked on ignore eventually, but this should not be ok.

|||The error also happens due to invalid or not enough rights in all the HKCR\Microsoft.SqlServer.Dts.Tasks. ... keys. The administrator group has only read access. Setting all keys of this group to full access solves this problem|||I found some access denied keys, HKCR\Microsoft.SqlServer.DTS.TAks.MessageQueueTask.DataFileMessage keys....

MessageQueueTask
MessageQueueTask.ServerCompMQTask

There might be a few others becuase I gave permissions to a few before I starts running REGMON.

Monday, March 19, 2012

msg 4820 Bulk insert error -- "Unknown version of format file"

Hi all,

ISSUE:
====================
In SQL 2005 (sp2) I get the following error when preforming a bulk
insert with an associated xml format file:
"Could not bulk insert. Unknown version of format file"

Question:
====================
I am unsure what they mean by "unknown version". Specifically the
format file in question was created using bcp. Also the entire table
scenario was created from a msdn example.

Any ideas? have you seen this before?

NOTE: i can reproduce this issue outside the example but will refer to
msdn considering it is simple and easily reproducible.

Scenario
====================
I can reproduce this error with the BULK INSERT example discussed on
msdn (example A)
http://msdn2.microsoft.com/en-us/library/ms191234.aspx

TO REPRODUCE:

* In short the table structure is:
Person (Age int, FirstName varchar(20), LastName varchar(30))

* Data File Template:
Age<tab>Firstname<tab>Lastname<return>

* xml file format from bcp (and described on msdn)
<?xml version="1.0"?>
<BCPFORMAT
xmlns="http://schemas.microsoft.com/sqlserver/2004/bulkload/format"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RECORD>
<FIELD ID="1" xsi:type="CharTerm" TERMINATOR="\t"
MAX_LENGTH="12"/>
<FIELD ID="2" xsi:type="CharTerm" TERMINATOR="\t"
MAX_LENGTH="20" COLLATION="SQL_Latin1_General_CP1_CI_AS"/>
<FIELD ID="3" xsi:type="CharTerm" TERMINATOR="\r\n"
MAX_LENGTH="30"
COLLATION="SQL_Latin1_General_CP1_CI_AS"/>
</RECORD>
<ROW>
<COLUMN SOURCE="1" NAME="age" xsi:type="SQLINT"/>
<COLUMN SOURCE="2" NAME="firstname" xsi:type="SQLVARYCHAR"/>
<COLUMN SOURCE="3" NAME="lastname" xsi:type="SQLVARYCHAR"/>
</ROW>
</BCPFORMAT>

* Here is some the actual sql statement that pulls this all together
BULK INSERT mytestnames
FROM 'C:\datatest\exampledata-c.Dat'
WITH (FORMATFILE = 'C:\datatest\examplefmt.Fmt');

Thanks in advanced for any feedback.

Cheers!

Hi,

plz can you show your XML format file "examplefmt.Fmt".

there must be something like this:

examplefmt.Fmt

...

2 SQLCHAR 0 100 "," 2 firstname SQL_Latin1_General_CP1_CI_AS
...

Monday, March 12, 2012

msg 4820 Bulk insert error -- "Unknown version of format file"

Hi all,

ISSUE:
====================
In SQL 2005 (sp2) I get the following error when preforming a bulk
insert with an associated xml format file:
"Could not bulk insert. Unknown version of format file"

Any ideas? have you seen this before?

NOTE: i can reproduce this issue outside the example but will refer to
msdn considering it is simple and easily reproducible.

Scenario
====================
I can reproduce this error with the BULK INSERT example discussed on
msdn (example A)
http://msdn2.microsoft.com/en-us/library/ms191234.aspx

TO REPRODUCE:

* In short the table structure is:
Person (Age int, FirstName varchar(20), LastName varchar(30))

* Data File Template:
Age<tab>Firstname<tab>Lastname<return>

* Here is some the actual sql statement that pulls this all together
BULK INSERT mytestnames
FROM 'C:\datatest\exampledata-c.Dat'
WITH (FORMATFILE = 'C:\datatest\examplefmt.Fmt');

Thanks in advanced for any feedback.

Cheers!

Hi,

plz can you show your XML format file "examplefmt.Fmt".

there must be something like this:

examplefmt.Fmt

...

2 SQLCHAR 0 100 "," 2 firstname SQL_Latin1_General_CP1_CI_AS
...

Saturday, February 25, 2012

MSDTC Msg 8501

OS: Windows 2000

SQL Version: SQL 2000 - 8.00.818 (SP3) Standard

MSDTC Version: 03.00.00.3421

I am getting error message 8501 when I try to run any queries against this linked server from several environments (from Win2003 Server, XP). I have read that the MSDTC service needs to run under the NT AUTHORITY\NetworkService login. I cannot get it to be set to this login. How do I make this change. If I uninstall the service and reinstall, I still get it to default to local system account.

What I am needing is:

How do I set the NT Authority\NetworkService account for the MSDTC service?

How do I set the MSDTC service to run with remote connections comming in?

Please let me know what other information you will need.

Thank you for any help you may give.

One of the KBA refers:

Make sure that the Log On As account for the MSDTC service is the Network Service account. To do this, follow these steps:

Click Start, and then click Run.

In the Run dialog box, type Services.msc, and then click OK.

In the Services window, locate the Distributed Transaction Coordinator service under Name in the right pane.

Under the Log On As column, see whether the Log On As account is Network Service or Local System.

If the Log On As account is Network Service, go to step 2. If the Log On As account is Local System account, continue with these steps.

Click Start, and then click Run.

In the Run dialog box, type cmd, and then click OK.

Enable MSDTC to allow the network transaction. To do this, follow these steps:

Click Start, and then click Run.

In the Run dialog box, type dcomcnfg.exe, and then click OK.

In the Component Services window, expand Component Services, expand Computers, and then expand My Computer.

Right-click My Computer, and then click Properties.

In the My Computer Properties dialog box, click Security Configuration on the MSDTC tab.

In the Security Configuration dialog box, click to select the Network DTC Access check box.

To allow the distributed transaction to run on this computer from a remote computer, click to select the Allow Inbound check box.

To allow the distributed transaction to run on a remote computer from this computer, click to select the Allow Outbound check box.

Under the Transaction Manager Communication group, click to select the No Authentication Required option.

In the Security Configuration dialog box, click OK.

In the My Computer Properties dialog box, click OK.

|||

I have found these instructions, but they are for Windows 2003 Server and I am running Windows 2000 Server. I do appreciate your reply and I followed the directions as outlined, but the My Computer Properties within the Component Services does not show these options.

Within the Distributed Transaction Coordinator service properties I cannot get it to log on as the Network Service. I have un-installed MSDTC, deleted the registry key, re-installed MSDTC and it defaults to the Local System account, not the Network Service account. Now distributed transactions are receiving the error Msg 8501. I have deleted the linked server and re-created the linked server and I am still getting this same error.

|||

Strange, I've followed the same on a windows 2000 SP4 advanced server box without any issues.

Please specify the WIndows OS service pack level too.

GeneralSQL wrote:

I have found these instructions, but they are for Windows 2003 Server and I am running Windows 2000 Server. I do appreciate your reply and I followed the directions as outlined, but the My Computer Properties within the Component Services does not show these options.
Within the Distributed Transaction Coordinator service properties I cannot get it to log on as the Network Service. I have un-installed MSDTC, deleted the registry key, re-installed MSDTC and it defaults to the Local System account, not the Network Service account. Now distributed transactions are receiving the error Msg 8501. I have deleted the linked server and re-created the linked server and I am still getting this same error.

|||

Microsoft Windows 2000

5.00.2195

Service Pack 4

It is not advanced server, but the standard edition.

Monday, February 20, 2012

MSDN Version of SQLServer 2000 and SQLServer 2005

All,
From a SQLServer installation (both 2000 & 2005), is there a way to find out
if the installation is a MSDN installation. Select @.@.Version does not seem to
indicate anything to that effect.
The previous DBA did a SQLServer installation (2000 & 2005) and I could not
find the 32-bit version of the media. That leads me to believe that he might
have installed it from a MSDN CD/DVD.
Thanks,
rgnNo. You can only tell what edition you have installed.
Jonathan
rgn wrote:
> All,
> From a SQLServer installation (both 2000 & 2005), is there a way to find out
> if the installation is a MSDN installation. Select @.@.Version does not seem to
> indicate anything to that effect.
> The previous DBA did a SQLServer installation (2000 & 2005) and I could not
> find the 32-bit version of the media. That leads me to believe that he might
> have installed it from a MSDN CD/DVD.
> Thanks,
> rgn
>

MSDN version of SQL Server 2005 Connections

If I put an MSDN version of SQL Server 2005 on a server that has IIS
for testing does the IIS users get limited to 10 connections to SQL at
once or is it considered 1 connection?
I need to know so we can use it as a test platform of load testing of
several hundered 100 or so users before moving to the production
version of SQL...which is not here yet...I dont want to think any
problems of connections or timeouts are due to using the MSDN version
for testing and development.
Thanks, Ed,
No. Whether it's from MSDN or not has no bearing on the feature set, that
simply depends on what edition you use
(Dev/Standard/Enterprise/Workgroup/Express). What it does have a bearing on
is licensing.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"gencode" <google@.gencode.com> wrote in message
news:1131130353.177316.126630@.g14g2000cwa.googlegr oups.com...
> If I put an MSDN version of SQL Server 2005 on a server that has IIS
> for testing does the IIS users get limited to 10 connections to SQL at
> once or is it considered 1 connection?
> I need to know so we can use it as a test platform of load testing of
> several hundered 100 or so users before moving to the production
> version of SQL...which is not here yet...I dont want to think any
> problems of connections or timeouts are due to using the MSDN version
> for testing and development.
> Thanks, Ed,
>
|||Sorry, forgot to say
SQL 2005 "Enterprise Edition"
I know some MSDN things like OS limit to 10, worried that it will limit
me
Ed,
|||What I am wondering is if I use the MSDN Enterprise Edition of SQL for
the backend of my development web server will it only allow 10 people
to connect to my web pages that have codebehind accessing the database,
or get some type of connection error in my code after 10 users or will
it not limit me for my testing of over 100 web users?
All users connect via IIS, none have direct connections to SQL
Thansk again Jasper
|||No, there's no feature limitation (that I'm aware of) - it's purely a
licensing thing
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"gencode" <google@.gencode.com> wrote in message
news:1131146290.037020.56980@.g14g2000cwa.googlegro ups.com...
> What I am wondering is if I use the MSDN Enterprise Edition of SQL for
> the backend of my development web server will it only allow 10 people
> to connect to my web pages that have codebehind accessing the database,
> or get some type of connection error in my code after 10 users or will
> it not limit me for my testing of over 100 web users?
> All users connect via IIS, none have direct connections to SQL
> Thansk again Jasper
>
|||Thanks
|||Thanks

MSDN version of SQL Server 2005 Connections

If I put an MSDN version of SQL Server 2005 on a server that has IIS
for testing does the IIS users get limited to 10 connections to SQL at
once or is it considered 1 connection?
I need to know so we can use it as a test platform of load testing of
several hundered 100 or so users before moving to the production
version of SQL...which is not here yet...I dont want to think any
problems of connections or timeouts are due to using the MSDN version
for testing and development.
Thanks, Ed,No. Whether it's from MSDN or not has no bearing on the feature set, that
simply depends on what edition you use
(Dev/Standard/Enterprise/Workgroup/Express). What it does have a bearing on
is licensing.
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"gencode" <google@.gencode.com> wrote in message
news:1131130353.177316.126630@.g14g2000cwa.googlegroups.com...
> If I put an MSDN version of SQL Server 2005 on a server that has IIS
> for testing does the IIS users get limited to 10 connections to SQL at
> once or is it considered 1 connection?
> I need to know so we can use it as a test platform of load testing of
> several hundered 100 or so users before moving to the production
> version of SQL...which is not here yet...I dont want to think any
> problems of connections or timeouts are due to using the MSDN version
> for testing and development.
> Thanks, Ed,
>|||Sorry, forgot to say
SQL 2005 "Enterprise Edition"
I know some MSDN things like OS limit to 10, worried that it will limit
me
Ed,|||What I am wondering is if I use the MSDN Enterprise Edition of SQL for
the backend of my development web server will it only allow 10 people
to connect to my web pages that have codebehind accessing the database,
or get some type of connection error in my code after 10 users or will
it not limit me for my testing of over 100 web users?
All users connect via IIS, none have direct connections to SQL
Thansk again Jasper|||No, there's no feature limitation (that I'm aware of) - it's purely a
licensing thing
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"gencode" <google@.gencode.com> wrote in message
news:1131146290.037020.56980@.g14g2000cwa.googlegroups.com...
> What I am wondering is if I use the MSDN Enterprise Edition of SQL for
> the backend of my development web server will it only allow 10 people
> to connect to my web pages that have codebehind accessing the database,
> or get some type of connection error in my code after 10 users or will
> it not limit me for my testing of over 100 web users?
> All users connect via IIS, none have direct connections to SQL
> Thansk again Jasper
>|||Thanks|||Thanks

MSDN version of SQL Server 2005 Connections

If I put an MSDN version of SQL Server 2005 on a server that has IIS
for testing does the IIS users get limited to 10 connections to SQL at
once or is it considered 1 connection?
I need to know so we can use it as a test platform of load testing of
several hundered 100 or so users before moving to the production
version of SQL...which is not here yet...I dont want to think any
problems of connections or timeouts are due to using the MSDN version
for testing and development.
Thanks, Ed,No. Whether it's from MSDN or not has no bearing on the feature set, that
simply depends on what edition you use
(Dev/Standard/Enterprise/Workgroup/Express). What it does have a bearing on
is licensing.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"gencode" <google@.gencode.com> wrote in message
news:1131130353.177316.126630@.g14g2000cwa.googlegroups.com...
> If I put an MSDN version of SQL Server 2005 on a server that has IIS
> for testing does the IIS users get limited to 10 connections to SQL at
> once or is it considered 1 connection?
> I need to know so we can use it as a test platform of load testing of
> several hundered 100 or so users before moving to the production
> version of SQL...which is not here yet...I dont want to think any
> problems of connections or timeouts are due to using the MSDN version
> for testing and development.
> Thanks, Ed,
>|||Sorry, forgot to say
SQL 2005 "Enterprise Edition"
I know some MSDN things like OS limit to 10, worried that it will limit
me
Ed,|||What I am wondering is if I use the MSDN Enterprise Edition of SQL for
the backend of my development web server will it only allow 10 people
to connect to my web pages that have codebehind accessing the database,
or get some type of connection error in my code after 10 users or will
it not limit me for my testing of over 100 web users?
All users connect via IIS, none have direct connections to SQL
Thansk again Jasper|||No, there's no feature limitation (that I'm aware of) - it's purely a
licensing thing
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"gencode" <google@.gencode.com> wrote in message
news:1131146290.037020.56980@.g14g2000cwa.googlegroups.com...
> What I am wondering is if I use the MSDN Enterprise Edition of SQL for
> the backend of my development web server will it only allow 10 people
> to connect to my web pages that have codebehind accessing the database,
> or get some type of connection error in my code after 10 users or will
> it not limit me for my testing of over 100 web users?
> All users connect via IIS, none have direct connections to SQL
> Thansk again Jasper
>|||Thanks|||Thanks

MSDN Version of SQL Server

Hi,
I have SQL Server 2000 standard edition from MSDN installed on what will now
become a production server. I have since purchased a 1 processor licence. My
question is there any reason not to continue using the MSDN version in
production? Or should I uninstall it and use the purchased version.
Thanks
NIsnt there a limit to the number of CPUs and RAM that MSDN copy can handle.
We had this problem once in SQLServer 7 and we eventually had to Backup
DB/uninstall MSDN version/Install Licensed Version and
Restore the Databases.
Whatever reason, you should always install a Licensed version in a
Production Version. What if you have to call PSS for some
reason ?
Gopi
"NH" <NH@.discussions.microsoft.com> wrote in message
news:4C998CC4-C4E9-41A2-BE48-197A5A4DDE8F@.microsoft.com...
> Hi,
> I have SQL Server 2000 standard edition from MSDN installed on what will
> now
> become a production server. I have since purchased a 1 processor licence.
> My
> question is there any reason not to continue using the MSDN version in
> production? Or should I uninstall it and use the purchased version.
> Thanks
> N|||For SQL7, MSDN came with Desktop Edition (not to be

with what we no
w call Desktop Engine,
AKA MSDE). Desktop Edition has such restrictions.
For 2000, MSDN comes with Developer Edition which is identical to Enterprise
Edition, but you are
now allowed to run in production environment.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Gopinath Rajee" <gopinathr@.healthasyst.com> wrote in message
news:urNSfT2DFHA.1396@.tk2msftngp13.phx.gbl...
> Isnt there a limit to the number of CPUs and RAM that MSDN copy can handle
.
> We had this problem once in SQLServer 7 and we eventually had to Backup DB
/uninstall MSDN
> version/Install Licensed Version and
> Restore the Databases.
> Whatever reason, you should always install a Licensed version in a Product
ion Version. What if you
> have to call PSS for some
> reason ?
> Gopi
>
> "NH" <NH@.discussions.microsoft.com> wrote in message
> news:4C998CC4-C4E9-41A2-BE48-197A5A4DDE8F@.microsoft.com...
>|||Also...

> Whatever reason, you should always install a Licensed version in a Product
ion Version. What if you
> have to call PSS for some
> reason ?
I couldn't agree more. :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Gopinath Rajee" <gopinathr@.healthasyst.com> wrote in message
news:urNSfT2DFHA.1396@.tk2msftngp13.phx.gbl...
> Isnt there a limit to the number of CPUs and RAM that MSDN copy can handle
.
> We had this problem once in SQLServer 7 and we eventually had to Backup DB
/uninstall MSDN
> version/Install Licensed Version and
> Restore the Databases.
> Whatever reason, you should always install a Licensed version in a Product
ion Version. What if you
> have to call PSS for some
> reason ?
> Gopi
>
> "NH" <NH@.discussions.microsoft.com> wrote in message
> news:4C998CC4-C4E9-41A2-BE48-197A5A4DDE8F@.microsoft.com...
>|||Thanks for the replies.
However, do you know if the MSDN version of SQL Standard Edition differs
from the one you purchase?
"Tibor Karaszi" wrote:

> Also...
>
> I couldn't agree more. :-)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Gopinath Rajee" <gopinathr@.healthasyst.com> wrote in message
> news:urNSfT2DFHA.1396@.tk2msftngp13.phx.gbl...
>
>|||MSDN doesn't come with production licenses. It might some with SE as well as
EE and Dev Ed. But you
are still not allowed to run in production environment. See
http://msdn.microsoft.com/subscript...ng/default.aspx
A quote from above:
"MSDN Universal, MSDN Enterprise, MSDN Professional and MSDN Operating Syste
ms are licensed for
single users, and can only be used by licensed subscribers. All products tha
t ship in MSDN
Subscriptions are for development and test purposes only, and cannot be used
in a live production
environment."
You also might find something valuable at :
http://msdn.microsoft.com/subscript...lt.aspx#support
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"NH" <NH@.discussions.microsoft.com> wrote in message
news:19D4DE6A-4093-48EB-B900-7606C7F42A16@.microsoft.com...
> Thanks for the replies.
> However, do you know if the MSDN version of SQL Standard Edition differs
> from the one you purchase?
> "Tibor Karaszi" wrote:
>|||Hi,
I realise MSDN versions of SQL Standard are "not allowed to run in
production environment". But what I am asking is does MSDN version of SQL
Standard differ from the version you would buy (OEM type). Are there
restrictions on RAM, connections etc etc?
"Tibor Karaszi" wrote:

> MSDN doesn't come with production licenses. It might some with SE as well
as EE and Dev Ed. But you
> are still not allowed to run in production environment. See
> http://msdn.microsoft.com/subscript...ng/default.aspx
> A quote from above:
> "MSDN Universal, MSDN Enterprise, MSDN Professional and MSDN Operating Sys
tems are licensed for
> single users, and can only be used by licensed subscribers. All products t
hat ship in MSDN
> Subscriptions are for development and test purposes only, and cannot be us
ed in a live production
> environment."
>
> You also might find something valuable at :
> http://msdn.microsoft.com/subscript...lt.aspx#support
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "NH" <NH@.discussions.microsoft.com> wrote in message
> news:19D4DE6A-4093-48EB-B900-7606C7F42A16@.microsoft.com...
>
>|||> Are there
> restrictions on RAM, connections etc etc?
No.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"NH" <NH@.discussions.microsoft.com> wrote in message
news:D3D585A4-1C12-4203-9640-8ED39685B371@.microsoft.com...
> Hi,
> I realise MSDN versions of SQL Standard are "not allowed to run in
> production environment". But what I am asking is does MSDN version of SQL
> Standard differ from the version you would buy (OEM type). Are there
> restrictions on RAM, connections etc etc?
> "Tibor Karaszi" wrote:
>|||Thanks for your help.
N
"Tibor Karaszi" wrote:

> No.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "NH" <NH@.discussions.microsoft.com> wrote in message
> news:D3D585A4-1C12-4203-9640-8ED39685B371@.microsoft.com...
>
>

MSDN SQL 2005 versions

I'm a MSDN subscriber and recently installed SQL 2005 developer edition and
noticed it installed a version of visual studio. I'd prefer to install VS
pro edition seperate from SQL 2005. Should I install SQL 2005 Standard
version instead of developer edition and then install Visual Studio Pro
edition?
I couldn't find in the SQL 2005 developer edition install options where to
choose not to install the visual studio version.If you do not want the VS part to be installed, during installation, you can
opt out of installing the Business Intelligence Development Studio. But, you
can install this becuase it gives you access to SSIS, SQLCLR, Analysis
Services projects. Once you install the VS 2005 version, you can use either
of them to do your work.
--
HTH,
SriSamp
Email: srisamp@.gmail.com
Blog: http://blogs.sqlxml.org/srinivassampath
URL: http://www32.brinkster.com/srisamp
"Scott" <sbailey@.mileslumber.com> wrote in message
news:%23Mc5DHY8FHA.4076@.tk2msftngp13.phx.gbl...
> I'm a MSDN subscriber and recently installed SQL 2005 developer edition
> and noticed it installed a version of visual studio. I'd prefer to install
> VS pro edition seperate from SQL 2005. Should I install SQL 2005 Standard
> version instead of developer edition and then install Visual Studio Pro
> edition?
> I couldn't find in the SQL 2005 developer edition install options where to
> choose not to install the visual studio version.
>|||"SriSamp" <ssampath@.sct.co.in> wrote in
news:ucxBvVY8FHA.3952@.TK2MSFTNGP12.phx.gbl:

> If you do not want the VS part to be installed, during installation,
> you can opt out of installing the Business Intelligence Development
> Studio. But, you can install this becuase it gives you access to SSIS,
> SQLCLR, Analysis Services projects.
Actually, I do not believe the VS isntalled with SQL Server gives you
access to the SQLCLR projects - I'm not 100% though.
Niels
****************************************
**********
* Niels Berglund
* http://staff.develop.com/nielsb
* nielsb@.no-spam.develop.com
* "A First Look at SQL Server 2005 for Developers"
* http://www.awprofessional.com/title/0321180593
****************************************
**********|||Niels Berglund <nielsb@.develop.com> wrote in
news:Xns9719520FAE996nielsbdevelopcom@.20
7.46.248.16:

> Actually, I do not believe the VS isntalled with SQL Server gives you
> access to the SQLCLR projects - I'm not 100% though.
I am. You cannot open SQLCLR projects with BIDS.
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging|||Sorry about that. Since what SQL Server installs is anyways BI related, I
guess SQLCLR is not allowed.
--
HTH,
SriSamp
Email: srisamp@.gmail.com
Blog: http://blogs.sqlxml.org/srinivassampath
URL: http://www32.brinkster.com/srisamp
"Ole Kristian Bangs" <olekristian.bangas@.masterminds.no> wrote in message
news:Xns971961B226E4Dolekristianbangaas@.
207.46.248.16...
> Niels Berglund <nielsb@.develop.com> wrote in
> news:Xns9719520FAE996nielsbdevelopcom@.20
7.46.248.16:
>
> I am. You cannot open SQLCLR projects with BIDS.
> --
> Ole Kristian Bangs
> MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging|||If I install VS 2005 1st, will SQL 2005 pick up on that and not install it's
VS version?
"SriSamp" <ssampath@.sct.co.in> wrote in message
news:ucxBvVY8FHA.3952@.TK2MSFTNGP12.phx.gbl...
> If you do not want the VS part to be installed, during installation, you
> can opt out of installing the Business Intelligence Development Studio.
> But, you can install this becuase it gives you access to SSIS, SQLCLR,
> Analysis Services projects. Once you install the VS 2005 version, you can
> use either of them to do your work.
> --
> HTH,
> SriSamp
> Email: srisamp@.gmail.com
> Blog: http://blogs.sqlxml.org/srinivassampath
> URL: http://www32.brinkster.com/srisamp
> "Scott" <sbailey@.mileslumber.com> wrote in message
> news:%23Mc5DHY8FHA.4076@.tk2msftngp13.phx.gbl...
>|||"Scott" <sbailey@.mileslumber.com> wrote in message
news:uCaM73d8FHA.2644@.TK2MSFTNGP10.phx.gbl...
> If I install VS 2005 1st, will SQL 2005 pick up on that and not install
> it's VS version?
>
Yes, and vice versa. Both products share the VS shell and just install
different components.
David

Friday, March 23, 2012

MSQL Server Version with service pack

MSOLAP.DLL Version Numbers

msmqtask.dll

msmqtask.dll

msmqtask.dll

Monday, March 19, 2012

msg 4820 Bulk insert error -- "Unknown version of format file"

Monday, March 12, 2012

msg 4820 Bulk insert error -- "Unknown version of format file"

Saturday, February 25, 2012

MSDTC Msg 8501

Monday, February 20, 2012

MSDN Version of SQLServer 2000 and SQLServer 2005

MSDN version of SQL Server 2005 Connections

MSDN version of SQL Server 2005 Connections

MSDN version of SQL Server 2005 Connections

MSDN Version of SQL Server

MSDN SQL 2005 versions

MSDTC and Win2K3

Blog Archive

About Me