How to findout the edition of SQL Server? like standard, enterprise...
select @.@.version gives that information?
I am using SQL 2K.
Thanks,
SmithHello
select serverproperty('Edition') will provide that information.
Check books on line for serverproperty().
select @.@.version will give the build version. SQLSecurity WebSite has a SQL
Server version database -
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
Carlos Eduardo Selonke de Souza
http://carlos.geekbunker.org
"Allen Smith" wrote:
> How to findout the edition of SQL Server? like standard, enterprise...
> select @.@.version gives that information?
> I am using SQL 2K.
> Thanks,
> Smith
>
>|||YOu are absoletely rigth.
Select @.@.Version
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Allen Smith" <ASmith_Forest@.hotmail.com> schrieb im Newsbeitrag
news:OXp78GGbFHA.348@.TK2MSFTNGP14.phx.gbl...
> How to findout the edition of SQL Server? like standard, enterprise...
> select @.@.version gives that information?
> I am using SQL 2K.
> Thanks,
> Smith
>
>|||Allen Smith wrote:
> How to findout the edition of SQL Server? like standard, enterprise...
> select @.@.version gives that information?
Though SELECT @.@.VERSION gives a long string that contains the edition
info too, you will have to copy it and paste it into the editor area to
really see that long string!
Instead, the SELECT SERVERPROPERTY('Edition') gives you just what you
wanted!|||Sarah wrote:
> Allen Smith wrote:
> Though SELECT @.@.VERSION gives a long string that contains the edition
> info too, you will have to copy it and paste it into the editor area
> to really see that long string!
> Instead, the SELECT SERVERPROPERTY('Edition') gives you just what you
> wanted!
In my case it's not a problem to see the string you get with SELECT
@.@.VERSION. If you just "expand" the result column you can scroll back and
forth to see it.
Regards
Steen
Showing posts with label version. Show all posts
Showing posts with label version. Show all posts
Sunday, March 25, 2012
@@BVersion.... Edition
How to findout the edition of SQL Server? like standard, enterprise...
select @.@.version gives that information?
I am using SQL 2K.
Thanks,
Smith
Hello
select serverproperty('Edition') will provide that information.
Check books on line for serverproperty().
select @.@.version will give the build version. SQLSecurity WebSite has a SQL
Server version database -
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
Carlos Eduardo Selonke de Souza
http://carlos.geekbunker.org
"Allen Smith" wrote:
> How to findout the edition of SQL Server? like standard, enterprise...
> select @.@.version gives that information?
> I am using SQL 2K.
> Thanks,
> Smith
>
>
|||YOu are absoletely rigth.
Select @.@.Version
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Allen Smith" <ASmith_Forest@.hotmail.com> schrieb im Newsbeitrag
news:OXp78GGbFHA.348@.TK2MSFTNGP14.phx.gbl...
> How to findout the edition of SQL Server? like standard, enterprise...
> select @.@.version gives that information?
> I am using SQL 2K.
> Thanks,
> Smith
>
>
|||Allen Smith wrote:
> How to findout the edition of SQL Server? like standard, enterprise...
> select @.@.version gives that information?
Though SELECT @.@.VERSION gives a long string that contains the edition
info too, you will have to copy it and paste it into the editor area to
really see that long string!
Instead, the SELECT SERVERPROPERTY('Edition') gives you just what you
wanted!
|||Sarah wrote:
> Allen Smith wrote:
> Though SELECT @.@.VERSION gives a long string that contains the edition
> info too, you will have to copy it and paste it into the editor area
> to really see that long string!
> Instead, the SELECT SERVERPROPERTY('Edition') gives you just what you
> wanted!
In my case it's not a problem to see the string you get with SELECT
@.@.VERSION. If you just "expand" the result column you can scroll back and
forth to see it.
Regards
Steen
select @.@.version gives that information?
I am using SQL 2K.
Thanks,
Smith
Hello
select serverproperty('Edition') will provide that information.
Check books on line for serverproperty().
select @.@.version will give the build version. SQLSecurity WebSite has a SQL
Server version database -
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
Carlos Eduardo Selonke de Souza
http://carlos.geekbunker.org
"Allen Smith" wrote:
> How to findout the edition of SQL Server? like standard, enterprise...
> select @.@.version gives that information?
> I am using SQL 2K.
> Thanks,
> Smith
>
>
|||YOu are absoletely rigth.
Select @.@.Version
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Allen Smith" <ASmith_Forest@.hotmail.com> schrieb im Newsbeitrag
news:OXp78GGbFHA.348@.TK2MSFTNGP14.phx.gbl...
> How to findout the edition of SQL Server? like standard, enterprise...
> select @.@.version gives that information?
> I am using SQL 2K.
> Thanks,
> Smith
>
>
|||Allen Smith wrote:
> How to findout the edition of SQL Server? like standard, enterprise...
> select @.@.version gives that information?
Though SELECT @.@.VERSION gives a long string that contains the edition
info too, you will have to copy it and paste it into the editor area to
really see that long string!
Instead, the SELECT SERVERPROPERTY('Edition') gives you just what you
wanted!
|||Sarah wrote:
> Allen Smith wrote:
> Though SELECT @.@.VERSION gives a long string that contains the edition
> info too, you will have to copy it and paste it into the editor area
> to really see that long string!
> Instead, the SELECT SERVERPROPERTY('Edition') gives you just what you
> wanted!
In my case it's not a problem to see the string you get with SELECT
@.@.VERSION. If you just "expand" the result column you can scroll back and
forth to see it.
Regards
Steen
@@BVersion.... Edition
How to findout the edition of SQL Server? like standard, enterprise...
select @.@.version gives that information?
I am using SQL 2K.
Thanks,
SmithHello
select serverproperty('Edition') will provide that information.
Check books on line for serverproperty().
select @.@.version will give the build version. SQLSecurity WebSite has a SQL
Server version database -
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
--
Carlos Eduardo Selonke de Souza
http://carlos.geekbunker.org
"Allen Smith" wrote:
> How to findout the edition of SQL Server? like standard, enterprise...
> select @.@.version gives that information?
> I am using SQL 2K.
> Thanks,
> Smith
>
>|||YOu are absoletely rigth.
Select @.@.Version
--
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Allen Smith" <ASmith_Forest@.hotmail.com> schrieb im Newsbeitrag
news:OXp78GGbFHA.348@.TK2MSFTNGP14.phx.gbl...
> How to findout the edition of SQL Server? like standard, enterprise...
> select @.@.version gives that information?
> I am using SQL 2K.
> Thanks,
> Smith
>
>|||Allen Smith wrote:
> How to findout the edition of SQL Server? like standard, enterprise...
> select @.@.version gives that information?
Though SELECT @.@.VERSION gives a long string that contains the edition
info too, you will have to copy it and paste it into the editor area to
really see that long string!
Instead, the SELECT SERVERPROPERTY('Edition') gives you just what you
wanted!|||Sarah wrote:
> Allen Smith wrote:
>> How to findout the edition of SQL Server? like standard,
>> enterprise... select @.@.version gives that information?
> Though SELECT @.@.VERSION gives a long string that contains the edition
> info too, you will have to copy it and paste it into the editor area
> to really see that long string!
> Instead, the SELECT SERVERPROPERTY('Edition') gives you just what you
> wanted!
In my case it's not a problem to see the string you get with SELECT
@.@.VERSION. If you just "expand" the result column you can scroll back and
forth to see it.
Regards
Steen
select @.@.version gives that information?
I am using SQL 2K.
Thanks,
SmithHello
select serverproperty('Edition') will provide that information.
Check books on line for serverproperty().
select @.@.version will give the build version. SQLSecurity WebSite has a SQL
Server version database -
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
--
Carlos Eduardo Selonke de Souza
http://carlos.geekbunker.org
"Allen Smith" wrote:
> How to findout the edition of SQL Server? like standard, enterprise...
> select @.@.version gives that information?
> I am using SQL 2K.
> Thanks,
> Smith
>
>|||YOu are absoletely rigth.
Select @.@.Version
--
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Allen Smith" <ASmith_Forest@.hotmail.com> schrieb im Newsbeitrag
news:OXp78GGbFHA.348@.TK2MSFTNGP14.phx.gbl...
> How to findout the edition of SQL Server? like standard, enterprise...
> select @.@.version gives that information?
> I am using SQL 2K.
> Thanks,
> Smith
>
>|||Allen Smith wrote:
> How to findout the edition of SQL Server? like standard, enterprise...
> select @.@.version gives that information?
Though SELECT @.@.VERSION gives a long string that contains the edition
info too, you will have to copy it and paste it into the editor area to
really see that long string!
Instead, the SELECT SERVERPROPERTY('Edition') gives you just what you
wanted!|||Sarah wrote:
> Allen Smith wrote:
>> How to findout the edition of SQL Server? like standard,
>> enterprise... select @.@.version gives that information?
> Though SELECT @.@.VERSION gives a long string that contains the edition
> info too, you will have to copy it and paste it into the editor area
> to really see that long string!
> Instead, the SELECT SERVERPROPERTY('Edition') gives you just what you
> wanted!
In my case it's not a problem to see the string you get with SELECT
@.@.VERSION. If you just "expand" the result column you can scroll back and
forth to see it.
Regards
Steen
VERSION MDAC FOR SQL server 6.5 on WIN NT 4.0
WHICH VERSION OF MDAC SHOULD I INSTLL ON WINDOWS NT 4.0
SERVER WTIH SQL 6.5 SERVER SP 5
to connect or transact or run procdure with SQL server
2000 from SQL 6.5
server
ThanksIf you need to connect to a named instance on the SQL Server 2000 machine
with creating an alias, the lowest level of MDAC should be MDAC 2.6.
However, if you want to use all the functionality of the SQL Server itself
you should install the level of MDAC that is installed on the SQL Server
2000 machine.
Rand
This posting is provided "as is" with no warranties and confers no rights.sql
SERVER WTIH SQL 6.5 SERVER SP 5
to connect or transact or run procdure with SQL server
2000 from SQL 6.5
server
ThanksIf you need to connect to a named instance on the SQL Server 2000 machine
with creating an alias, the lowest level of MDAC should be MDAC 2.6.
However, if you want to use all the functionality of the SQL Server itself
you should install the level of MDAC that is installed on the SQL Server
2000 machine.
Rand
This posting is provided "as is" with no warranties and confers no rights.sql
Thursday, March 22, 2012
Restoring a BAK Do I Need the Schema ?
Hello everyone,
I'm new to SQL Server 2005. I'm using the Express version.
A co-worker sent me a BAK file which I need to restore. My question is, do I
need to have the database structure already in place before I can do the
restore? I was wondering if there's a way to simply restore the BAK file
into an empty database and have underlying tables/sprocs automatically
created as part of the restore process. Is this possible?
Thanks very much.
Yes. You can either just restore the bak file and let it create what it
needs or you can
1. Create empty, new database with the same name
2. Do a backup of the same name as your backup
3. Put the co-worker's backup in place of the backup in 2
4. Restore the backup and tell it to overwrite an existing DB.
Alan Foxmore wrote:
> Hello everyone,
> I'm new to SQL Server 2005. I'm using the Express version.
> A co-worker sent me a BAK file which I need to restore. My question is, do I
> need to have the database structure already in place before I can do the
> restore? I was wondering if there's a way to simply restore the BAK file
> into an empty database and have underlying tables/sprocs automatically
> created as part of the restore process. Is this possible?
> Thanks very much.
>
|||Actually, step 1 to 3 are unnecessary and a waste of time. The restore process will create the
database for you.
You might need to investigate what files were used for the original database (RESTORE HEADERONLY and
RESTORE FILELISTONLY) and then specify new physical filenames when you restore (using the MOVE
option of the RESTORE command).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"MSDN" <Grunt@.newsgroup.nospam> wrote in message news:eAc3EaxkHHA.492@.TK2MSFTNGP04.phx.gbl...[vbcol=seagreen]
> Yes. You can either just restore the bak file and let it create what it needs or you can
> 1. Create empty, new database with the same name
> 2. Do a backup of the same name as your backup
> 3. Put the co-worker's backup in place of the backup in 2
> 4. Restore the backup and tell it to overwrite an existing DB.
>
> Alan Foxmore wrote:
|||I always wondered about that. I've taken to just restoring the file as I
suggested. However, when I inherited the SQL stuff that was the
technique the current admin used and recommended. It didn't make much
sense to me but at the time he new much more than I did <G>.
Tibor Karaszi wrote:
> Actually, step 1 to 3 are unnecessary and a waste of time. The restore
> process will create the database for you.
> You might need to investigate what files were used for the original
> database (RESTORE HEADERONLY and RESTORE FILELISTONLY) and then specify
> new physical filenames when you restore (using the MOVE option of the
> RESTORE command).
>
|||Perhaps that person had worked with the old architecture (6.5 and older), where you actually *had*
to create the database first?
:-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"MSDN" <Grunt@.newsgroup.nospam> wrote in message news:%23e7CJmykHHA.568@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
>I always wondered about that. I've taken to just restoring the file as I suggested. However, when
>I inherited the SQL stuff that was the technique the current admin used and recommended. It didn't
>make much sense to me but at the time he new much more than I did <G>.
>
> Tibor Karaszi wrote:
|||That would explain it. I picked it up when I migrated a SQL 7 to SQL
2000. He did have 6.5 or earlier experience. Thanks.
Tibor Karaszi wrote:
> Perhaps that person had worked with the old architecture (6.5 and
> older), where you actually *had* to create the database first?
> :-)
>
|||Thank you all... It works now. I had to change to the account under which
the service was running to the Local Account.
Thanks again.
"Alan Foxmore" <afoxmore@.yahoo.com> wrote in message
news:upPyLKxkHHA.4112@.TK2MSFTNGP04.phx.gbl...
> Hello everyone,
> I'm new to SQL Server 2005. I'm using the Express version.
> A co-worker sent me a BAK file which I need to restore. My question is, do
> I need to have the database structure already in place before I can do the
> restore? I was wondering if there's a way to simply restore the BAK file
> into an empty database and have underlying tables/sprocs automatically
> created as part of the restore process. Is this possible?
> Thanks very much.
>
I'm new to SQL Server 2005. I'm using the Express version.
A co-worker sent me a BAK file which I need to restore. My question is, do I
need to have the database structure already in place before I can do the
restore? I was wondering if there's a way to simply restore the BAK file
into an empty database and have underlying tables/sprocs automatically
created as part of the restore process. Is this possible?
Thanks very much.
Yes. You can either just restore the bak file and let it create what it
needs or you can
1. Create empty, new database with the same name
2. Do a backup of the same name as your backup
3. Put the co-worker's backup in place of the backup in 2
4. Restore the backup and tell it to overwrite an existing DB.
Alan Foxmore wrote:
> Hello everyone,
> I'm new to SQL Server 2005. I'm using the Express version.
> A co-worker sent me a BAK file which I need to restore. My question is, do I
> need to have the database structure already in place before I can do the
> restore? I was wondering if there's a way to simply restore the BAK file
> into an empty database and have underlying tables/sprocs automatically
> created as part of the restore process. Is this possible?
> Thanks very much.
>
|||Actually, step 1 to 3 are unnecessary and a waste of time. The restore process will create the
database for you.
You might need to investigate what files were used for the original database (RESTORE HEADERONLY and
RESTORE FILELISTONLY) and then specify new physical filenames when you restore (using the MOVE
option of the RESTORE command).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"MSDN" <Grunt@.newsgroup.nospam> wrote in message news:eAc3EaxkHHA.492@.TK2MSFTNGP04.phx.gbl...[vbcol=seagreen]
> Yes. You can either just restore the bak file and let it create what it needs or you can
> 1. Create empty, new database with the same name
> 2. Do a backup of the same name as your backup
> 3. Put the co-worker's backup in place of the backup in 2
> 4. Restore the backup and tell it to overwrite an existing DB.
>
> Alan Foxmore wrote:
|||I always wondered about that. I've taken to just restoring the file as I
suggested. However, when I inherited the SQL stuff that was the
technique the current admin used and recommended. It didn't make much
sense to me but at the time he new much more than I did <G>.
Tibor Karaszi wrote:
> Actually, step 1 to 3 are unnecessary and a waste of time. The restore
> process will create the database for you.
> You might need to investigate what files were used for the original
> database (RESTORE HEADERONLY and RESTORE FILELISTONLY) and then specify
> new physical filenames when you restore (using the MOVE option of the
> RESTORE command).
>
|||Perhaps that person had worked with the old architecture (6.5 and older), where you actually *had*
to create the database first?
:-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"MSDN" <Grunt@.newsgroup.nospam> wrote in message news:%23e7CJmykHHA.568@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
>I always wondered about that. I've taken to just restoring the file as I suggested. However, when
>I inherited the SQL stuff that was the technique the current admin used and recommended. It didn't
>make much sense to me but at the time he new much more than I did <G>.
>
> Tibor Karaszi wrote:
|||That would explain it. I picked it up when I migrated a SQL 7 to SQL
2000. He did have 6.5 or earlier experience. Thanks.
Tibor Karaszi wrote:
> Perhaps that person had worked with the old architecture (6.5 and
> older), where you actually *had* to create the database first?
> :-)
>
|||Thank you all... It works now. I had to change to the account under which
the service was running to the Local Account.
Thanks again.
"Alan Foxmore" <afoxmore@.yahoo.com> wrote in message
news:upPyLKxkHHA.4112@.TK2MSFTNGP04.phx.gbl...
> Hello everyone,
> I'm new to SQL Server 2005. I'm using the Express version.
> A co-worker sent me a BAK file which I need to restore. My question is, do
> I need to have the database structure already in place before I can do the
> restore? I was wondering if there's a way to simply restore the BAK file
> into an empty database and have underlying tables/sprocs automatically
> created as part of the restore process. Is this possible?
> Thanks very much.
>
Sunday, March 11, 2012
.net version of Detect Anomalies in Excel
Is there an equivalent or similar .net sample for detecting data Anomalies?
Detect Anomalies in Excel
http://zones.advisor.com/doc/14413
Please check out the Data Mining Addins for Office 2007. There's a task "Detect Outliers" which might work for you. More details about the addins are available at http://www.sqlserverdatamining.com
Thanks
|||I can say that I've never even tried it ... but I would need to obtain the Add-in source code and alter it for my purposes. Office/Excel will not suffice. I need to expose this functionality via a web interface and so it must also be a highly scalable solution. C# preferable.|||This tip http://www.sqlserverdatamining.com/DMCommunity/TipsNTricks/861.aspx gives the basic idea. You can also check out the live sample at http://www.sqlserverdatamining.com/DMCommunity/LiveSamples/46.aspx that shows anomaly detection in a web application - source code is provided. The Excel Addin adds the automatic creation of a mining model with some nice heuristics for column selection, and the visualization part. Those are mostly dependent on your application and the Excel code wouldn't really help I believe.
The two sources above should give you everything you need. I once presented the implementation of the above web application at TechEd, so it should be in the TechEd archives (although I forget which year it was)
-Jamie
.NET version of DB Hammer
Where can I get .net version of DB Hammer?
J Justin
I need to bulk load my test database with dummy data. SQL Server resource
kit contains tools like DBGen and DBHammer. Is there any .NET version of
these tools?
Thanks for any input.
J Justin
"Justin" <justin@.gjsoft.com> wrote in message
news:#vuucgJ$EHA.3708@.TK2MSFTNGP14.phx.gbl...
> Where can I get .net version of DB Hammer?
> J Justin
>
J Justin
I need to bulk load my test database with dummy data. SQL Server resource
kit contains tools like DBGen and DBHammer. Is there any .NET version of
these tools?
Thanks for any input.
J Justin
"Justin" <justin@.gjsoft.com> wrote in message
news:#vuucgJ$EHA.3708@.TK2MSFTNGP14.phx.gbl...
> Where can I get .net version of DB Hammer?
> J Justin
>
.net version of crystal reports?
is there a .net version for crystal reports, if i do my reports in 8.5 and load them in a .net application. would it be a problem?
i would be happy if someone could clarify my confusion!
thanksYes there is a .Net version that is supplied with MS Visual Studio .Net. Your 8.5 reports will be fine under CR.Net, but if you create new reports under .Net, you will not be able to open them in 8.5|||who owns the .net version of the crystal reports, is it by microsoft corporation or seagate?|||Beats me :)
i would be happy if someone could clarify my confusion!
thanksYes there is a .Net version that is supplied with MS Visual Studio .Net. Your 8.5 reports will be fine under CR.Net, but if you create new reports under .Net, you will not be able to open them in 8.5|||who owns the .net version of the crystal reports, is it by microsoft corporation or seagate?|||Beats me :)
Thursday, March 8, 2012
.Net interface to vss for sql 2000 stored procedures
We would like to use the version control for sql stored procedures through
.net, however, according to Microsoft's implementation procedures it gives
developers "sa" authority. Does anyone know how we can set this up without
the developers having "sa" authority on our database?You can use Windows Authentication for developers staff
"sgerwie" wrote:
> We would like to use the version control for sql stored procedures through
> .net, however, according to Microsoft's implementation procedures it gives
> developers "sa" authority. Does anyone know how we can set this up without
> the developers having "sa" authority on our database?|||We do use Windows Authentication for the developers, however, in order to se
t
this up, SQL services has to run with "sa" authority and Admin rights on the
server, therefore, it automatically gives everyone "sa" rights to SQL. It
doesn't matter
"MAURICIO" wrote:
[vbcol=seagreen]
> You can use Windows Authentication for developers staff
> "sgerwie" wrote:
>
.net, however, according to Microsoft's implementation procedures it gives
developers "sa" authority. Does anyone know how we can set this up without
the developers having "sa" authority on our database?You can use Windows Authentication for developers staff
"sgerwie" wrote:
> We would like to use the version control for sql stored procedures through
> .net, however, according to Microsoft's implementation procedures it gives
> developers "sa" authority. Does anyone know how we can set this up without
> the developers having "sa" authority on our database?|||We do use Windows Authentication for the developers, however, in order to se
t
this up, SQL services has to run with "sa" authority and Admin rights on the
server, therefore, it automatically gives everyone "sa" rights to SQL. It
doesn't matter
"MAURICIO" wrote:
[vbcol=seagreen]
> You can use Windows Authentication for developers staff
> "sgerwie" wrote:
>
.net framework version
We have an application that requires a different version of .net framework
(not 2.0). Can the SQL Server 2005 client tools be installed with a different
version of .net framework? I would rather the programmers use the SQL 2005
tools instead of SQL 2000.
Thanks.
Esteban Arturo
SQL Server tools require 2.0 but you can have multiple versions of the .NET
Framework installed so installing SQL Server doesn't limit your ability to
use the older version of the framework.
Roman
Roman Rehak
http://sqlblog.com/blogs/roman_rehak
"Esteban Arturo" <EstebanArturo@.discussions.microsoft.com> wrote in message
news:30738F85-0D35-41B4-9E76-BDA05A96B1B7@.microsoft.com...
> We have an application that requires a different version of .net framework
> (not 2.0). Can the SQL Server 2005 client tools be installed with a
> different
> version of .net framework? I would rather the programmers use the SQL 2005
> tools instead of SQL 2000.
> Thanks.
> --
> Esteban Arturo
(not 2.0). Can the SQL Server 2005 client tools be installed with a different
version of .net framework? I would rather the programmers use the SQL 2005
tools instead of SQL 2000.
Thanks.
Esteban Arturo
SQL Server tools require 2.0 but you can have multiple versions of the .NET
Framework installed so installing SQL Server doesn't limit your ability to
use the older version of the framework.
Roman
Roman Rehak
http://sqlblog.com/blogs/roman_rehak
"Esteban Arturo" <EstebanArturo@.discussions.microsoft.com> wrote in message
news:30738F85-0D35-41B4-9E76-BDA05A96B1B7@.microsoft.com...
> We have an application that requires a different version of .net framework
> (not 2.0). Can the SQL Server 2005 client tools be installed with a
> different
> version of .net framework? I would rather the programmers use the SQL 2005
> tools instead of SQL 2000.
> Thanks.
> --
> Esteban Arturo
.Net Framework Data Provider for SQL Server
If I try to create a database reference in VS 2008 B2 I get an error with "This server version is not supported. Only serves up to Microsoft SQL Server 2005 are supported."
Is this a problem with the SqlClient provider? Or is this a problem with VS integration with Katmai?
? VS Integration with Katmai. The designers don't support this yet. There will be a fix for this in a later release. Cheers, Bob Beauchemin SQLskills ""Scott Sharpe"@.discussions.microsoft.com" <"=?UTF-8?B?U2NvdHQgU2hhcnBl?="@.discussions.microsoft.com> wrote in message news:9c9cb3d8-3d35-448c-858c-644b593f2e16@.discussions.microsoft.com... If I try to create a database reference in VS 2008 B2 I get an error with "This server version is not supported. Only serves up to Microsoft SQL Server 2005 are supported." Is this a problem with the SqlClient provider? Or is this a problem with VS integration with Katmai?.NET Framework 2.0 question
This question also posted to microsoft.public.sqlserver.notificationsvcs.
Notification Services in SQL Server 2005 requires the .NET Framework 2.0. There is no version of the notification services dll built against version 1.1 in SQL Server 2005.
Thanks
-shyam|||
Notification Services on SQL 2005 utilizes .NET Framework version 2.0.
(correct?)
If so, will there be a version of
microsoft.sqlserver.notificationservices.dll for SQL 2005 NS that will
allow me to create subscription management applications using VS 2003
and .NET Framework 1.1? Or must I use VS 2005 and .NET Framework 2.0?
Thanks,
Peter
Hi Peter -
SQL Server 2005 does come with v2.0 of the .NET framework, but I cannot speak as to whether Notification Services uses it or a prior version.
I'm setting up a test vpc for the exact scenario you mentioned. I expect it to work.
Here is an excerpt from BOL (April CTP) that doesn't directly address your question, but still may be applicable.
<excerpt>
Notification Services could not create an instance of the event provider. This error can occur if a custom event provider was not built using version 1.0.3705 of the .NET Framework. When Notification Services and a custom component use different versions of the .NET Framework, differences in the class libraries can cause application errors.
UserAction
When possible, build custom components with version 1.0.3705 of the .NET Framework. If you must build custom components with version 1.1.4322 of the .NET Framework, you can force Notification Services to use the same version. To do this, add a <startup> node to the NSService.exe.config file, which is in the vN.N.N.N\Bin folder of Notification Services. The following example shows the <startup> node:
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<startup>
<supportedRuntime version="v1.1.4322"/>
<supportedRuntime version="v1.0.3705"/>
</startup>
...
The <supportedRuntime> elements restrict the versions of the .NET Framework that Notification Services can use. The order of the listed versions determines the order in which Notification Services attempts to load the .NET Framework versions. In the example above, Notification Services will first attempt to load version 1.1.4322 of the .NET Framework. If it is not available, Notification Services will attempt to load version 1.0.3705 of the .NET Framework.
You must restart the instance of Notification Services to apply changes made to NSService.exe.config.
</excerpt>
Of course you can still use COM Interop, but who would want to do that? :)
HTH...
--
Joe Webb
SQL Server MVP
~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811
I support PASS, the Professional Association for SQL Server.
(www.sqlpass.org)
Notification Services in SQL Server 2005 requires the .NET Framework 2.0. There is no version of the notification services dll built against version 1.1 in SQL Server 2005.
The only way I know of to work around this, if you must build your client app against the .NET framework 1.1, is to create a web service wrapper around the NS APIs you need, using the .NET Framework 2.0. You will then be able to invoke methods on the web service from a .NET 1.1 application.
Obviously, this method is a little cumbersome. If at all possible, I highly recommend you move your subscription management application to .NET 2.0.
-shyam
Learn more about SQL-NS:
http://www.amazon.com/exec/obidos/tg/detail/-/0672326647/
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.|||
So, are BOL docs in the April CTP wrong in this respect? (I haven't checked the June CTP yet.)
--
Joe Webb
SQL Server MVP
~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811
I support PASS, the Professional Association for SQL Server. (www.sqlpass.org)
|||No, there is no version of the microsoft.sqlserver.notificationservices.dll that can be called from .Net Framework 1.1. You will need to use .Net Framework 2.0.
-Lukasz
|||It seems like that content was held over from the NS2.0 release - it doesn't apply to SQL 2005. I'll check with our doc writer to have it removed/corrected.Thanks
-shyam|||
This topic had not been updated for SQL Server 2005. The topic was rewritten shortly after the April CTP. Sorry about the old content.
|||Thank you everyone for the quick responses!Peter
Tuesday, March 6, 2012
.NET 2.0 and .NET 1.1 co-existence?
I downloaded Quest Software's freeware version of
Comparison Suite. When I attempt to install, it tells
me that it requires .NET framework 1.1.4322. I already
have .NET 2.0 installed (as part of the MS-SQL native client install)
and I really don't want to mess that up.
Comparison Suite. When I attempt to install, it tells
me that it requires .NET framework 1.1.4322. I already
have .NET 2.0 installed (as part of the MS-SQL native client install)
and I really don't want to mess that up.
Is it *safe* to have the installer download/install .NET 1.1
to coexist with 2.0? Is it likely to work?Yes, you can install the various versions of .NET side-by-side and they will
live happily together.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Larry Bertolini" <bertolini.1@.osu.eduwrote in message
news:ehnt6m$ssp$1@.charm.magnus.acs.ohio-state.edu...
Quote:
Originally Posted by
>I downloaded Quest Software's freeware version of
Comparison Suite. When I attempt to install, it tells
me that it requires .NET framework 1.1.4322. I already
have .NET 2.0 installed (as part of the MS-SQL native client install)
and I really don't want to mess that up.
>
Is it *safe* to have the installer download/install .NET 1.1
to coexist with 2.0? Is it likely to work?
Subscribe to:
Posts (Atom)