Showing posts with label default. Show all posts
Showing posts with label default. Show all posts

Monday, March 19, 2012

[SQL2005] Binding defaults without using sp_bindefault

The SQL2005 documentation states the sp_bindefault will be gone in the next
version and the DEFAULT keyword should be used with CREATE TABLE or ALTER
TABLE statements. But I seem to have run into a situation where that only th
e
stored procedure approach works.
script 1:
CREATE DEFAULT abc AS 1
script 2:
CREATE TABLE xyz(
id int IDENTITY(1,1) NOT NULL,
thingy int DEFAULT abc)
This will result in the following error: "The name "abc" is not permitted in
this context. Valid expressions are constants, constant expressions, and (in
some contexts) variables. Column names are not permitted."
It works perfectly when I use the sp_bindefault procedure instead, so I do
have a solution, but can it be done without? I am probably missing something
very simple, so any help is welcome. TIA!Check documentation for CREATE DEFAULT and you will see that this will also
disappear. What BOL is
trying to say is that default objects will disappear, while default constrai
nts is the way to go.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"PaulSand" <PaulSand@.discussions.microsoft.com> wrote in message
news:F6F545C2-D304-46BA-A5D4-DC07660BAECE@.microsoft.com...
> The SQL2005 documentation states the sp_bindefault will be gone in the nex
t
> version and the DEFAULT keyword should be used with CREATE TABLE or ALTER
> TABLE statements. But I seem to have run into a situation where that only
the
> stored procedure approach works.
> script 1:
> CREATE DEFAULT abc AS 1
> script 2:
> CREATE TABLE xyz(
> id int IDENTITY(1,1) NOT NULL,
> thingy int DEFAULT abc)
> This will result in the following error: "The name "abc" is not permitted
in
> this context. Valid expressions are constants, constant expressions, and (
in
> some contexts) variables. Column names are not permitted."
> It works perfectly when I use the sp_bindefault procedure instead, so I do
> have a solution, but can it be done without? I am probably missing somethi
ng
> very simple, so any help is welcome. TIA!
>
>
>|||Don't bind defaults, ADD them:
alter table <table name>
add constraint abc
default (1)
for <column name>
ML
http://milambda.blogspot.com/|||I could do that, but the whole idea for me was to define a centralized
default, so when I change that, the changes will be reflected in every colum
n
binded to that default.
"ML" wrote:

> Don't bind defaults, ADD them:
> alter table <table name>
> add constraint abc
> default (1)
> for <column name>
>
> ML
> --
> http://milambda.blogspot.com/|||Is it possible to bind a single default constraint to multiple columns in
multiple tables? I.e. I have a date column in every table which should be
filled with a default value if none is provided.
At the moment I made a default for it and linked the name of the default to
the date column. In my database design tool, I only have to change the
default value in one place if I ever decide the current one is not right
anymore. Let the tool create a script for me and it is changed.
With constraints I have to change the default value in every single table
(200+), while I could do it with just one simple change when using
sp_bindefault was allowed. Or can it be done more easily?
"Tibor Karaszi" wrote:

> Check documentation for CREATE DEFAULT and you will see that this will als
o disappear. What BOL is
> trying to say is that default objects will disappear, while default constr
aints is the way to go.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "PaulSand" <PaulSand@.discussions.microsoft.com> wrote in message
> news:F6F545C2-D304-46BA-A5D4-DC07660BAECE@.microsoft.com...
>|||As Tibor states in his post the default as a SQL object is on its last breat
h
(so to speak), as for the default as a constraint it cannot be reused as if
it were an object.
A constraint is a declaration, and if your requirement really is
object-oriented (rather than declarative) then maybe you could get what you
need by using a user-defined CLR type. But only for a default? I wouldn't go
down that road.
While being aware of the benefits a default provides as an object (e.g.
reusability), I still think a default is merely an attribute of the
individual column, and should be treated as such - kept in the meta world.
ML
http://milambda.blogspot.com/|||Ah hold on, I know what to do ;-)
Currently I have a UDDT for a mandatory date column and bind a default to it
when I need to. The solution is to create two UDDTs, one with and one withou
t
the constraint. It's gonna be some work to convert 200+ tables, but it's a
solution ...
"PaulSand" wrote:
> Is it possible to bind a single default constraint to multiple columns in
> multiple tables? I.e. I have a date column in every table which should be
> filled with a default value if none is provided.
> At the moment I made a default for it and linked the name of the default t
o
> the date column. In my database design tool, I only have to change the
> default value in one place if I ever decide the current one is not right
> anymore. Let the tool create a script for me and it is changed.
> With constraints I have to change the default value in every single table
> (200+), while I could do it with just one simple change when using
> sp_bindefault was allowed. Or can it be done more easily?
>
> "Tibor Karaszi" wrote:
>|||Oops, sorry for making a mess here, but that isn't a solution either ...
"PaulSand" wrote:
> Ah hold on, I know what to do ;-)
> Currently I have a UDDT for a mandatory date column and bind a default to
it
> when I need to. The solution is to create two UDDTs, one with and one with
out
> the constraint. It's gonna be some work to convert 200+ tables, but it's a
> solution ...
> "PaulSand" wrote:
>|||Mess? Aren't we learning anymore? :)
ML
http://milambda.blogspot.com/|||> Is it possible to bind a single default constraint to multiple columns in
> multiple tables?
No. In short:
Default objects are deprecated. Those does what you want to do.
Default constraints are supported and recommended way in the future. But you
create them at the
column level, so they cannot be defined-one-used-many.
You might want to post a wish to [url]http://lab.msdn.microsoft.com/productfeedback/.[/
url] The ANSI SQL
feature you are looking for is the "DOMAIN" (CREATE/ALTER DOMAIN), but that
is not implemented in
SQL Server.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"PaulSand" <PaulSand@.discussions.microsoft.com> wrote in message
news:6D87E279-5C8F-4BB6-9394-28454BD4B89D@.microsoft.com...
> Is it possible to bind a single default constraint to multiple columns in
> multiple tables? I.e. I have a date column in every table which should be
> filled with a default value if none is provided.
> At the moment I made a default for it and linked the name of the default t
o
> the date column. In my database design tool, I only have to change the
> default value in one place if I ever decide the current one is not right
> anymore. Let the tool create a script for me and it is changed.
> With constraints I have to change the default value in every single table
> (200+), while I could do it with just one simple change when using
> sp_bindefault was allowed. Or can it be done more easily?
>
> "Tibor Karaszi" wrote:
>

Tuesday, March 6, 2012

[newbe] SQL number of querries / connections limits ?

Hi all!
Can you tell me if there are any default or manually set limits of
subsequent querries / connections per user or database? I couldnt find
any in Enterprise Manager, but my Perl / ASP aplications seems to behave
as if it were some.
Perl script (DBI + Sybase DBD) is doing some quite massive inserts (a
2000 - 3000 per hour). After doing a couple of thosands it sudenly stops
- querry is sent but no result returns. If I limit the numer of being
sent per minute - the program seems to work propotionally longer, but
finally 'hangs' in the very same well.
Moreover, ASP IIS based cooperating aplication seems to reach the same
limit - after some time querries (actually doing SELECTS on data
previously INSERTED by Perl script) are processed longer than ASP
timeout allows, well the actually hangs, Profiler shows some crazy
processing times. If I reduce the number of queries per transaction -
namely changing a subquerry to join construction - it works ok. It all
makes me think I hit some limits.
I've searched the WEB archives (my MS coleeges' knowledge as well )
but couldn't find much - does any body knows sth about it?
pk
There is no hard limit on the number of connections you can have to a SQL
Server. But every connection takes up about 40KB of server memory, so there
are definitely practical limitations. Make sure that all your code drops the
connections to the server that are no longer needed.
Jacco Schalkwijk
SQL Server MVP
"Piotr Kowalski" <wywaltopkwlski@.oitotez2.pl> wrote in message
news:ctl2ea$oa9$1@.atlantis.news.tpi.pl...
> Hi all!
> Can you tell me if there are any default or manually set limits of
> subsequent querries / connections per user or database? I couldnt find any
> in Enterprise Manager, but my Perl / ASP aplications seems to behave as if
> it were some.
> Perl script (DBI + Sybase DBD) is doing some quite massive inserts (a
> 2000 - 3000 per hour). After doing a couple of thosands it sudenly stops -
> querry is sent but no result returns. If I limit the numer of being sent
> per minute - the program seems to work propotionally longer, but finally
> 'hangs' in the very same well.
> Moreover, ASP IIS based cooperating aplication seems to reach the same
> limit - after some time querries (actually doing SELECTS on data
> previously INSERTED by Perl script) are processed longer than ASP timeout
> allows, well the actually hangs, Profiler shows some crazy processing
> times. If I reduce the number of queries per transaction - namely changing
> a subquerry to join construction - it works ok. It all makes me think I
> hit some limits.
> I've searched the WEB archives (my MS coleeges' knowledge as well ) but
> couldn't find much - does any body knows sth about it?
> pk
|||Jacco Schalkwijk wrote:
> There is no hard limit on the number of connections you can have to a SQL
> Server. But every connection takes up about 40KB of server memory, so there
> are definitely practical limitations. Make sure that all your code drops the
> connections to the server that are no longer needed.
>
yeah, I've considered that.
Sybase DBI library unfortunately uses new connection every query, but
neither client's nor server's network stack reports other TCP
connections than being actually used (some 3 connection in every moment)
so older ones are properly disconnected. Maybe some "residues" still
remains on the SQL box, on the aplication layer, which aren't counted by
netstat but still reserve some resources (RAM). Enterprise manager shows
only as many proceses as really exists (3).
What about query limit? Or other limits that could come in question in
this case?
hk

[newbe] SQL number of querries / connections limits ?

Hi all!
Can you tell me if there are any default or manually set limits of
subsequent querries / connections per user or database? I couldnt find
any in Enterprise Manager, but my Perl / ASP aplications seems to behave
as if it were some.
Perl script (DBI + Sybase DBD) is doing some quite massive inserts (a
2000 - 3000 per hour). After doing a couple of thosands it sudenly stops
- querry is sent but no result returns. If I limit the numer of being
sent per minute - the program seems to work propotionally longer, but
finally 'hangs' in the very same well.
Moreover, ASP IIS based cooperating aplication seems to reach the same
limit - after some time querries (actually doing SELECTS on data
previously INSERTED by Perl script) are processed longer than ASP
timeout allows, well the actually hangs, Profiler shows some crazy
processing times. If I reduce the number of queries per transaction -
namely changing a subquerry to join construction - it works ok. It all
makes me think I hit some limits.
I've searched the WEB archives (my MS coleeges' knowledge as well :))
but couldn't find much - does any body knows sth about it?
pkThere is no hard limit on the number of connections you can have to a SQL
Server. But every connection takes up about 40KB of server memory, so there
are definitely practical limitations. Make sure that all your code drops the
connections to the server that are no longer needed.
--
Jacco Schalkwijk
SQL Server MVP
"Piotr Kowalski" <wywaltopkwlski@.oitotez2.pl> wrote in message
news:ctl2ea$oa9$1@.atlantis.news.tpi.pl...
> Hi all!
> Can you tell me if there are any default or manually set limits of
> subsequent querries / connections per user or database? I couldnt find any
> in Enterprise Manager, but my Perl / ASP aplications seems to behave as if
> it were some.
> Perl script (DBI + Sybase DBD) is doing some quite massive inserts (a
> 2000 - 3000 per hour). After doing a couple of thosands it sudenly stops -
> querry is sent but no result returns. If I limit the numer of being sent
> per minute - the program seems to work propotionally longer, but finally
> 'hangs' in the very same well.
> Moreover, ASP IIS based cooperating aplication seems to reach the same
> limit - after some time querries (actually doing SELECTS on data
> previously INSERTED by Perl script) are processed longer than ASP timeout
> allows, well the actually hangs, Profiler shows some crazy processing
> times. If I reduce the number of queries per transaction - namely changing
> a subquerry to join construction - it works ok. It all makes me think I
> hit some limits.
> I've searched the WEB archives (my MS coleeges' knowledge as well :)) but
> couldn't find much - does any body knows sth about it?
> pk|||Jacco Schalkwijk wrote:
> There is no hard limit on the number of connections you can have to a SQL
> Server. But every connection takes up about 40KB of server memory, so there
> are definitely practical limitations. Make sure that all your code drops the
> connections to the server that are no longer needed.
>
yeah, I've considered that.
Sybase DBI library unfortunately uses new connection every query, but
neither client's nor server's network stack reports other TCP
connections than being actually used (some 3 connection in every moment)
so older ones are properly disconnected. Maybe some "residues" still
remains on the SQL box, on the aplication layer, which aren't counted by
netstat but still reserve some resources (RAM). Enterprise manager shows
only as many proceses as really exists (3).
What about query limit? Or other limits that could come in question in
this case?
hk

[newbe] SQL number of querries / connections limits ?

Hi all!
Can you tell me if there are any default or manually set limits of
subsequent querries / connections per user or database? I couldnt find
any in Enterprise Manager, but my PERL / ASP aplications seems to behave
as if it were some.
Perl script (DBI + Sybase DBD) is doing some quite massive inserts (a
2000 - 3000 per hour). After doing a couple of thosands it sudenly stops
- querry is sent but no result returns. If I limit the numer of being
sent per minute - the program seems to work propotionally longer, but
finally 'hangs' in the very same well.
Moreover, ASP IIS based cooperating aplication seems to reach the same
limit - after some time querries (actually doing SELECTS on data
previously INSERTED by PERL script) are processed longer than ASP
timeout allows, well the actually hangs, Profiler shows some crazy
processing times. If I reduce the number of queries per transaction -
namely changing a subquerry to join construction - it works ok. It all
makes me think I hit some limits.
I've searched the WEB archives (my MS coleeges' knowledge as well )
but couldn't find much - does any body knows sth about it?
pkThere is no hard limit on the number of connections you can have to a SQL
Server. But every connection takes up about 40KB of server memory, so there
are definitely practical limitations. Make sure that all your code drops the
connections to the server that are no longer needed.
Jacco Schalkwijk
SQL Server MVP
"Piotr Kowalski" <wywaltopkwlski@.oitotez2.pl> wrote in message
news:ctl2ea$oa9$1@.atlantis.news.tpi.pl...
> Hi all!
> Can you tell me if there are any default or manually set limits of
> subsequent querries / connections per user or database? I couldnt find any
> in Enterprise Manager, but my PERL / ASP aplications seems to behave as if
> it were some.
> PERL script (DBI + Sybase DBD) is doing some quite massive inserts (a
> 2000 - 3000 per hour). After doing a couple of thosands it sudenly stops -
> querry is sent but no result returns. If I limit the numer of being sent
> per minute - the program seems to work propotionally longer, but finally
> 'hangs' in the very same well.
> Moreover, ASP IIS based cooperating aplication seems to reach the same
> limit - after some time querries (actually doing SELECTS on data
> previously INSERTED by PERL script) are processed longer than ASP timeout
> allows, well the actually hangs, Profiler shows some crazy processing
> times. If I reduce the number of queries per transaction - namely changing
> a subquerry to join construction - it works ok. It all makes me think I
> hit some limits.
> I've searched the WEB archives (my MS coleeges' knowledge as well ) but
> couldn't find much - does any body knows sth about it?
> pk|||Jacco Schalkwijk wrote:
> There is no hard limit on the number of connections you can have to a SQL
> Server. But every connection takes up about 40KB of server memory, so ther
e
> are definitely practical limitations. Make sure that all your code drops t
he
> connections to the server that are no longer needed.
>
yeah, I've considered that.
Sybase DBI library unfortunately uses new connection every query, but
neither client's nor server's network stack reports other TCP
connections than being actually used (some 3 connection in every moment)
so older ones are properly disconnected. Maybe some "residues" still
remains on the SQL box, on the aplication layer, which aren't counted by
netstat but still reserve some resources (RAM). Enterprise manager shows
only as many proceses as really exists (3).
What about query limit? Or other limits that could come in question in
this case?
hk

Saturday, February 25, 2012

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

trying to install sql server2005 on a windows 2003 server box.

getting msg below at the sql server . i looked at other posts on trying to uninstall SQL Native Access Client and norton antivirus. i could never find the snac on the add - remove programs and this server does not have a virus protection program yet.

here's the history of the installs on the server:

wanted to test a 2005 upgrade so:

1) installed sql server 2000 then sp4 then restored some databases to it - all OK

2) tried to upgrade to sql 2005 but ran into problems and left it at that.

had a disk drive crash on the d drive so lost the installs but not the operating system

when the drive was replaced, left alone for a while

then wanted to test a straight 2005 install

1) removed the broken 2005 attempt

2) removed the 2000

3) installed 2005 and got the error on the subject line:

TITLE: Microsoft SQL Server 2005 Setup

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

i've gone through as many of the forums that i can and have tried several things - like uninstalling 2005 and installing pieces and parts but but nothing seems to work.

Thanks!

Dan <><

It sounds like the SNAC version you have might be corrupt or incompatible.

Go to Add or Remove Programs and find the listing for "Microsoft SQL Native Client". Remove this component.

Then try the install again.

Michelle

|||

Thank you so much for replying. last attempt was to install just the sql server commonent - no others like analysis services or integration services.

i looked at the add / remove programs both before, during and after the sql server database services failed attempt and the add/remove has never shown a program called MS sql native access client (SNAC).

when i start the install, the installing prerequisites window shows the two components that will be installed: snac and the sql server 2005 setup support files. the snac goes to a green arrow almost immediately while the 2005 setup files takes a few seconds. i dont know if that helps or not.

the add remove programs just has:

microsoft .net framwork 2.0|||

It definatel looks like the problems is the "Microsoft SQL Server Native Client" layer. At this point your machine thinks that it is already installed but the install is broken.

Follow the directions in the following article to clean up the machine and then try again.

http://support.microsoft.com/kb/909967

Michelle

|||

uninstall manually - did the following (shows issues with some of the directions)

it said to delete the local security groups. but i never could figure out how to do. the article it mensions didnt (at least to me) show how to delete. so i just went on|||

i went out to the website and downloaded the .msi file for snac. it was slightly different from the .msi that came on the DVD (3511k vs 3516k).

the dvd version when i clicked on the msi file just returned me back to windows explorer.

the snac from microsoft's website executed and finally installed the snac.

the install worked perfectly after that.

thanks for your help

|||

Actually that was a good work around as downloading a newer version would have forced the install to run again where as in the previous case it was failing quickly becuase it thought it was laready installed.

Glad you got you machine back.

Michelle

|||

Hi,

I've been handling SQL Server upgrades for many years. The most dangerous path for an upgrade is to directly upgrade 2000 to 2005 (or 7.0 to 2000). That's because you create the risk of destroying the databases on the existing server and causing data loss.

The best approach embraces the fact that we typically upgrade a windows server when the mfg warranty on the hardware has expired. So, you have a new box and windows server. If you don't, the store the backups on another resource (disk, tape, flash drive, etc...) and copy from or restore from that resource. Rebuild the Windows server or uninstall SQL Server 2000. (I would have fresh windows to insure the best chance of success.)

Install SQL 2005 & configure on the new W03 SP1 server. migrate the users. (this worked easily with 2K but MS has hosed that functionality in 2005 from what I can see; you must use a script they provided that is flaky. You will need to manually create the users it fails to migrate.) Backup the dbs on 2K, shut down 2K on the old machine and restore the dbs to 2005. associate the users with the logins.

Now you have a fullly upgraded database server and your databases are unhosed. This may not be elegant but it guarantees the MS upgrade process won't destroy your databases or bring down your business for days.

If you have a completely hosed system, then rebuild the system (and the drives) and follow the steps above to a successful conclusion.

z.

Saturday, February 11, 2012

@@version, add database to a named instance?

Hi,
I have a sql 2000 personal editon(default server) and developer edition
(named) installed on a machine (windowsXP).
1) if I do 'select @.@.version' in query, I always get 'personal edition'
version information back. How can I get the version nformation of developer
edition?
2)How do I use Enterprise Manager to create a database with developer editon
server instance?
THANKS!
It tells you the version of the server you are connecting to. If you want
the version of developer edition you need to connect to it first.
"bangwo" <bangwo@.discussions.microsoft.com> wrote in message
news:977874AC-FC88-4DB2-9AA2-76095F35BABF@.microsoft.com...
> Hi,
> I have a sql 2000 personal editon(default server) and developer edition
> (named) installed on a machine (windowsXP).
> 1) if I do 'select @.@.version' in query, I always get 'personal edition'
> version information back. How can I get the version nformation of
> developer
> edition?
> 2)How do I use Enterprise Manager to create a database with developer
> editon
> server instance?
> THANKS!
|||"ME",
I couldn't find a way to 'connect' to the server instance of developer
edition in the sql enterprise maganer. Hope you can help me on this. Thanks
!!
"ME" wrote:

> It tells you the version of the server you are connecting to. If you want
> the version of developer edition you need to connect to it first.
>
> "bangwo" <bangwo@.discussions.microsoft.com> wrote in message
> news:977874AC-FC88-4DB2-9AA2-76095F35BABF@.microsoft.com...
>
>
|||well, if you open Server Network Utility you should see the instance name of
your SQL Edition server. Use that instance name to connect ...
"bangwo" <bangwo@.discussions.microsoft.com> wrote in message
news:AB497B9C-D604-4F46-B65C-F898D5D99359@.microsoft.com...[vbcol=seagreen]
> "ME",
> I couldn't find a way to 'connect' to the server instance of developer
> edition in the sql enterprise maganer. Hope you can help me on this.
> Thanks
> !!
> "ME" wrote:
|||Hello,
Go to the SQL Server log of the SQL Server Developer edition installation
(C:\program files\Microsoft SQL Server\Logs\ folder).
In the error log the name of the SQL Server installation will be shown. You
could use that information to either register to Enterprise manager or
connect to Query Analyzer. After that you could execute SELECT @.@.Version.
Thanks
hari
"bangwo" <bangwo@.discussions.microsoft.com> wrote in message
news:AB497B9C-D604-4F46-B65C-F898D5D99359@.microsoft.com...[vbcol=seagreen]
> "ME",
> I couldn't find a way to 'connect' to the server instance of developer
> edition in the sql enterprise maganer. Hope you can help me on this.
> Thanks
> !!
> "ME" wrote:

@@version, add database to a named instance?

Hi,
I have a sql 2000 personal editon(default server) and developer edition
(named) installed on a machine (windowsXP).
1) if I do 'select @.@.version' in query, I always get 'personal edition'
version information back. How can I get the version nformation of developer
edition?
2)How do I use Enterprise Manager to create a database with developer editon
server instance?
THANKS!It tells you the version of the server you are connecting to. If you want
the version of developer edition you need to connect to it first.
"bangwo" <bangwo@.discussions.microsoft.com> wrote in message
news:977874AC-FC88-4DB2-9AA2-76095F35BABF@.microsoft.com...
> Hi,
> I have a sql 2000 personal editon(default server) and developer edition
> (named) installed on a machine (windowsXP).
> 1) if I do 'select @.@.version' in query, I always get 'personal edition'
> version information back. How can I get the version nformation of
> developer
> edition?
> 2)How do I use Enterprise Manager to create a database with developer
> editon
> server instance?
> THANKS!|||"ME",
I couldn't find a way to 'connect' to the server instance of developer
edition in the sql enterprise maganer. Hope you can help me on this. Thanks
!!
"ME" wrote:

> It tells you the version of the server you are connecting to. If you want
> the version of developer edition you need to connect to it first.
>
> "bangwo" <bangwo@.discussions.microsoft.com> wrote in message
> news:977874AC-FC88-4DB2-9AA2-76095F35BABF@.microsoft.com...
>
>|||well, if you open Server Network Utility you should see the instance name of
your SQL Edition server. Use that instance name to connect ...
"bangwo" <bangwo@.discussions.microsoft.com> wrote in message
news:AB497B9C-D604-4F46-B65C-F898D5D99359@.microsoft.com...[vbcol=seagreen]
> "ME",
> I couldn't find a way to 'connect' to the server instance of developer
> edition in the sql enterprise maganer. Hope you can help me on this.
> Thanks
> !!
> "ME" wrote:
>|||Hello,
Go to the SQL Server log of the SQL Server Developer edition installation
(C:\program files\Microsoft SQL Server\Logs\ folder).
In the error log the name of the SQL Server installation will be shown. You
could use that information to either register to Enterprise manager or
connect to Query Analyzer. After that you could execute SELECT @.@.Version.
Thanks
hari
"bangwo" <bangwo@.discussions.microsoft.com> wrote in message
news:AB497B9C-D604-4F46-B65C-F898D5D99359@.microsoft.com...[vbcol=seagreen]
> "ME",
> I couldn't find a way to 'connect' to the server instance of developer
> edition in the sql enterprise maganer. Hope you can help me on this.
> Thanks
> !!
> "ME" wrote:
>