Showing posts with label edition. Show all posts
Showing posts with label edition. Show all posts

Thursday, March 22, 2012

current users

Is there a limit on how many concurrent users that can use SQL Server 2005 Express Edition?

I haven't been able to find any facts about that

Hi,

no there isn′t and there never has been. MSDE either didn′t havelimited concurrent users, the workload governor only throttled the query performance for more than 5 users.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Jens is correct, we do not limit the number of concurrent users in SQL Express. We have also removed the workload governer in SQL Express as well. Check out Euan Garden's Blog for a historical discussion on the workload governer in MSDE.

http://blogs.msdn.com/euanga/archive/2006/03/09/545576.aspx

Mike - SQL Express team

sql

Thursday, March 8, 2012

Cumulative database size limit

Hello all,
I have SQL 2000 SP 3 running on a Windows 2000 server. It used to be a
Desktop edition of SQL Server which we then upgraded to the SQL 2000
i.e. the SQL Server name is of the type: abcd\efg. I am trying to
increase the size of the database but it gives me the following error:
error 1827 create/alter database failed because the resulting cumulative
database size would exceed your licensed limit of 2048 MB per database.
We have checked with the vendor and they do not have any such
restrictions. Is this a SQL Desktop edition restriction? If so, this
database has already been converted to SQL 2000. Have any ideas?
Thanks,
Raziq.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!Is it possible that SQL Server did not successfully get upgraded. You can
verify this by looking at the SQL Server errorlog. It will tell you the
exact version that you are running. If it does not say SQL Server 2000
Standard or SQL Server 2000 Enterprise Edition then it did not get upgraded
successfully.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Hi Rand thanks for your response. It is SQL 2000. The errorlog is
listing it as version 8.00.760.
Any other ideas?
Raziq.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||What is the output of select @.@.version and select serverproperty('Edition')
?
It certainly sounds like it thinks it's Personal/Desktop edition
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raziq Shekha" <raziq_shekha@.anadarko.com> wrote in message
news:OAuC1Gy%23DHA.2512@.TK2MSFTNGP11.phx.gbl...
> Hi Rand thanks for your response. It is SQL 2000. The errorlog is
> listing it as version 8.00.760.
> Any other ideas?
> Raziq.
>
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!|||Hi Jasper,
You are right when I run the @.@.version it is coming back with the
desktop edition. But I did run the upgrade utility. Ok, what can I do
to make it the Enterprise Edition?
Raziq.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||I would probably start from scratch by detaching all my user
databases.Script all logins and jobs and save all DTS packages as structured
storage files then uninstall the existing instance and do a clean install of
Enterprise Edition. If you want to avoid any login->user SID mapping issues
afterwards you can export the logins as detailed here
http://support.microsoft.com/defaul...b;en-us;Q246133
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raziq Shekha" <raziq_shekha@.anadarko.com> wrote in message
news:uJ%234kc7%23DHA.4060@.TK2MSFTNGP10.phx.gbl...
> Hi Jasper,
> You are right when I run the @.@.version it is coming back with the
> desktop edition. But I did run the upgrade utility. Ok, what can I do
> to make it the Enterprise Edition?
> Raziq.
>
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!|||Thanks for your help Jasper.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!

Cumulative database size limit

Hello all,
I have SQL 2000 SP 3 running on a Windows 2000 server. It used to be a
Desktop edition of SQL Server which we then upgraded to the SQL 2000
i.e. the SQL Server name is of the type: abcd\efg. I am trying to
increase the size of the database but it gives me the following error:
error 1827 create/alter database failed because the resulting cumulative
database size would exceed your licensed limit of 2048 MB per database.
We have checked with the vendor and they do not have any such
restrictions. Is this a SQL Desktop edition restriction? If so, this
database has already been converted to SQL 2000. Have any ideas?
Thanks,
Raziq.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!Is it possible that SQL Server did not successfully get upgraded. You can
verify this by looking at the SQL Server errorlog. It will tell you the
exact version that you are running. If it does not say SQL Server 2000
Standard or SQL Server 2000 Enterprise Edition then it did not get upgraded
successfully.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Culture in MSSQL 2005 express edition

i am trying to add xml to the xml data type column. The xml contains both
english and hebrew characters. English characters are saved well, but hebrew
saved as "''?" how can i fix it?Try converting the xml to varbinary(max) before inserting. From BOL:
Text Encoding
SQL Server 2005 stores XML data in Unicode (UTF-16). XML data retrieved from
the server comes out in UTF-16 encoding. If you want a different encoding,
you have to perform the required conversion on the retrieved data.
Sometimes, the XML data may be in a different encoding. If it is, you have
to use care during data loading. For example:
a.. If your text XML is in Unicode (UCS-2, UTF-16), you can assign it to
an XML column, variable, or parameter without any problems.
b.. If the encoding is not Unicode and is implicit, because of the source
code page, the string code page in the database should be the same as or
compatible with the code points that you want to load. If required, use
COLLATE. If no such server code page exists, you have to add an explicit XML
declaration with the correct encoding.
c.. To use an explicit encoding, use either the varbinary() type, which
has no interaction with code pages, or use a string type of the appropriate
code page. Then, assign the data to an XML column, variable, or parameter.
Example: Explicitly Specifying an Encoding
Assume that you have an XML document, vcdoc, stored as varchar(max) that
does not have an explicit XML declaration. The following statement adds an
XML declaration with the encoding "iso8859-1", concatenates the XML
document, casts the result to varbinary(max) so that the byte representation
is preserved, and then finally casts it to XML. This enables the XML
processor to parse the data according to the specified encoding "iso8859-1"
and generate the corresponding UTF-16 representation for string values.
SELECT CAST(
CAST (('<?xml version="1.0" encoding="iso8859-1"?>'+ vcdoc) AS VARBINARY
(MAX))
AS XML)
David Barber [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"michael" <michael@.discussions.microsoft.com> wrote in message
news:19B65A8D-E246-46EB-A85B-C517D1830BAD@.microsoft.com...
> i am trying to add xml to the xml data type column. The xml contains both
> english and hebrew characters. English characters are saved well, but
hebrew
> saved as "''?" how can i fix it?|||Thanks a lot
"David Barber [MS]" wrote:

> Try converting the xml to varbinary(max) before inserting. From BOL:
> Text Encoding
> SQL Server 2005 stores XML data in Unicode (UTF-16). XML data retrieved fr
om
> the server comes out in UTF-16 encoding. If you want a different encoding,
> you have to perform the required conversion on the retrieved data.
> Sometimes, the XML data may be in a different encoding. If it is, you have
> to use care during data loading. For example:
> a.. If your text XML is in Unicode (UCS-2, UTF-16), you can assign it to
> an XML column, variable, or parameter without any problems.
>
> b.. If the encoding is not Unicode and is implicit, because of the sourc
e
> code page, the string code page in the database should be the same as or
> compatible with the code points that you want to load. If required, use
> COLLATE. If no such server code page exists, you have to add an explicit X
ML
> declaration with the correct encoding.
>
> c.. To use an explicit encoding, use either the varbinary() type, which
> has no interaction with code pages, or use a string type of the appropriat
e
> code page. Then, assign the data to an XML column, variable, or parameter.
>
> Example: Explicitly Specifying an Encoding
> Assume that you have an XML document, vcdoc, stored as varchar(max) that
> does not have an explicit XML declaration. The following statement adds an
> XML declaration with the encoding "iso8859-1", concatenates the XML
> document, casts the result to varbinary(max) so that the byte representati
on
> is preserved, and then finally casts it to XML. This enables the XML
> processor to parse the data according to the specified encoding "iso8859-1
"
> and generate the corresponding UTF-16 representation for string values.
>
> SELECT CAST(
> CAST (('<?xml version="1.0" encoding="iso8859-1"?>'+ vcdoc) AS VARBINARY
> (MAX))
> AS XML)
>
> --
> David Barber [MS]
> SQL Server Documentation Team
> This posting is provided "AS IS" with no warranties, and confers no rights
> "michael" <michael@.discussions.microsoft.com> wrote in message
> news:19B65A8D-E246-46EB-A85B-C517D1830BAD@.microsoft.com...
> hebrew
>
>

Sunday, February 19, 2012

CTP June Dev.Edition:TCP/IP protocol is disabled at default

I have tested Developer Edition CTP June but when I connect to remote SQL Server, "A connection was successfully established with the server, but then an error occurred during the pre-login handshake." error occured.
I find out TCP/IP protocol is disabled at default at CTP June. When you meet with same situation, try enable TCP/IP protocol being enabled on "SQL Server Configration Manager"

It's bug or by design?

Regards

Hajime GondoThis is in fact by design. As part of only making available services that you need we are defaulting the Developer Edition to not listen on TCP/IP.

-Euan|||Thanks Euan! I found topic "Network Protocols and Network Libraries".

But I can't accept this design. Bacause developer edition "must" (I think) functionaly works same as enterprise edition. If not, developer must search what is deffernt between Dev. and Ent.(such as me) This causes needless confusion.|||It does work the same as Ent and Std, the defaults are just different(this is the case with SSE as well). We provide a tool to flip the defaults.

-Euan|||It's nice that you will provide the tools. Question is, WHEN, we are waiting....|||There are 2 tools, the commandline version of setup allows much of this to be overriden and the surface area config tool allows you to flip al;l of these things asll, both have been in since the product RTM'd last year.|||

To install via the command line and turn TCP/IP on, specify the DISABLENETWORKPROTOCOLS command line parameter:

;--
; The DISABLENETWORKPROTOCOLS switch is used to disable network protocol for SQL Server instance.
; Set DISABLENETWORKPROTOCOLS = 0; for Shared Memory= On, Named Pipe= On, TCP= On
; Set DISABLENETWORKPROTOCOLS = 1; for Shared Memory= On, Named Pipe= Off (Local Only), TCP= Off
; Set DISABLENETWORKPROTOCOLS = 2; for Shared Memory= On, Named Pipe= Off (Local Only), TCP= On

; Note: DISABLENETWORKPROTOCOLS if not specified has the following defaults.
; Default value for SQL Server Express/Evaluation/Developer: DISABLENETWORKPROTOCOLS =1
; Default value for Enterprise/Standard /Workgroup: DISABLENETWORKPROTOCOLS =2

DISABLENETWORKPROTOCOLS=

To configure the TCP/IP after installation, you need to use the Surface Area Configuration tool that Euan mentioned. This blog entry describes it pretty well for SQLExpress - it applies equally well to other skus. ttp://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

Hope this helps.

-Jeffrey

CTP June Dev.Edition:TCP/IP protocol is disabled at default

I have tested Developer Edition CTP June but when I connect to remote SQL Server, "A connection was successfully established with the server, but then an error occurred during the pre-login handshake." error occured.
I find out TCP/IP protocol is disabled at default at CTP June. When you meet with same situation, try enable TCP/IP protocol being enabled on "SQL Server Configration Manager"

It's bug or by design?

Regards

Hajime GondoThis is in fact by design. As part of only making available services that you need we are defaulting the Developer Edition to not listen on TCP/IP.

-Euan|||Thanks Euan! I found topic "Network Protocols and Network Libraries".

But I can't accept this design. Bacause developer edition "must" (I think) functionaly works same as enterprise edition. If not, developer must search what is deffernt between Dev. and Ent.(such as me) This causes needless confusion.|||It does work the same as Ent and Std, the defaults are just different(this is the case with SSE as well). We provide a tool to flip the defaults.

-Euan|||It's nice that you will provide the tools. Question is, WHEN, we are waiting....|||There are 2 tools, the commandline version of setup allows much of this to be overriden and the surface area config tool allows you to flip al;l of these things asll, both have been in since the product RTM'd last year.|||

To install via the command line and turn TCP/IP on, specify the DISABLENETWORKPROTOCOLS command line parameter:

;--
; The DISABLENETWORKPROTOCOLS switch is used to disable network protocol for SQL Server instance.
; Set DISABLENETWORKPROTOCOLS = 0; for Shared Memory= On, Named Pipe= On, TCP= On
; Set DISABLENETWORKPROTOCOLS = 1; for Shared Memory= On, Named Pipe= Off (Local Only), TCP= Off
; Set DISABLENETWORKPROTOCOLS = 2; for Shared Memory= On, Named Pipe= Off (Local Only), TCP= On

; Note: DISABLENETWORKPROTOCOLS if not specified has the following defaults.
; Default value for SQL Server Express/Evaluation/Developer: DISABLENETWORKPROTOCOLS =1
; Default value for Enterprise/Standard /Workgroup: DISABLENETWORKPROTOCOLS =2

DISABLENETWORKPROTOCOLS=

To configure the TCP/IP after installation, you need to use the Surface Area Configuration tool that Euan mentioned. This blog entry describes it pretty well for SQLExpress - it applies equally well to other skus. ttp://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

Hope this helps.

-Jeffrey

Friday, February 17, 2012

CSV Render Engine

Hi

I have Reporting Services hosted on a server which has Workgroup edition of SQL Server which does not support csv export. I would like to write a csv Renderer.

I am not sure how complex this task is likely to be.
Are there any White Papers or samples that would assist ?
Any advice to point me in the right direction would be most appreciated.

Regards

JohnJames

Hi Chaps

I have just found an article on MSDN stating that
writing a Render is a very complex operation.
Will now seek another alternative.


Regards

JohnJames