Howdy,
My company is setting up a new dedicated hosting server and we're debating
using the new SQL 2005 verse the MSDE. I'm not familiar with the new
version, so I have one big question:: Outside of the connection string, will
any syntax in my existing ASP.NET script/stored procs have to change to
support SQL 2005? Is the migration process painless?
I've searched MSDN but really can't find what I'm looking for.
Thanks,
David Lozzi
Web Applications Developer
dlozzi@.(remove-this)delphi-ts.comHello David,
> Outside of the
> connection string, will any syntax in my existing ASP.NET
> script/stored procs have to change to support SQL 2005?
Without specifics, its hard to say precisely. Some things change some, a
few a lot, most hardly at all. There's an upgrade advisor tool on the distri
bution
media and here [0] that I'd recommend starting with. It should catch a major
ity
of the changes needed with a minimum of effort.
> Is the
> migration process painless?
Again, that depends on what you've done in the past. I suspect not, but the
upgrade advisor will help you know more for sure.
[0]: http://www.microsoft.com/downloads/...&displaylang=en
Thank you,
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/
Showing posts with label setting. Show all posts
Showing posts with label setting. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
MSDE Settings not being used
I'm trying to install MSDE 2000 in and XP environment. I want to install it in a specific sub-directory therfore, I'm using a setting ini file to give the instance name, target dir and data dir. I've included both the command line and ini file below:
Command Line Entry:
C:\MSDE2000\setup.exe SAPWD="xxxxxx" /settings "C:\SageQuestLou\DispatcherDB.INI" /L*v C:\SageQuestLou\MSDE.LOG
Settings file:
INSTANCENAME=SageQuest
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
DATADIR="C:\SageQuestLou\Data\"
TARGETDIR="C:\SageQuestLou\"
The installation does occur successfully however it installs using default parameters. However I don't know what the SA password is and it's not where I want it to be.
Can some tell me what wrong with my command line or ini file?
Thanks
Louis
try this to solve pwd problem:
setup /settings="C:\SageQuestLou\DispatcherDB.INI" /i
DISABLENETWORKPROTOCOLS=0 SAPWD=xxxxx SecurityMode=SQL /L*v
C:\SageQuestLou\MSDE.LOG
I'm guessing the SecurityMode param might help here.
"Louis" <anonymous@.discussions.microsoft.com> wrote in message
news:41C137B8-4DEB-430C-A10D-95200B9060A4@.microsoft.com...
> I'm trying to install MSDE 2000 in and XP environment. I want to install
it in a specific sub-directory therfore, I'm using a setting ini file to
give the instance name, target dir and data dir. I've included both the
command line and ini file below:
> Command Line Entry:
> C:\MSDE2000\setup.exe SAPWD="xxxxxx" /settings
"C:\SageQuestLou\DispatcherDB.INI" /L*v C:\SageQuestLou\MSDE.LOG
> Settings file:
> INSTANCENAME=SageQuest
> DISABLENETWORKPROTOCOLS=0
> SECURITYMODE=SQL
> DATADIR="C:\SageQuestLou\Data\"
> TARGETDIR="C:\SageQuestLou\"
> The installation does occur successfully however it installs using default
parameters. However I don't know what the SA password is and it's not where
I want it to be.
> Can some tell me what wrong with my command line or ini file?
>
> Thanks
> Louis
Command Line Entry:
C:\MSDE2000\setup.exe SAPWD="xxxxxx" /settings "C:\SageQuestLou\DispatcherDB.INI" /L*v C:\SageQuestLou\MSDE.LOG
Settings file:
INSTANCENAME=SageQuest
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
DATADIR="C:\SageQuestLou\Data\"
TARGETDIR="C:\SageQuestLou\"
The installation does occur successfully however it installs using default parameters. However I don't know what the SA password is and it's not where I want it to be.
Can some tell me what wrong with my command line or ini file?
Thanks
Louis
try this to solve pwd problem:
setup /settings="C:\SageQuestLou\DispatcherDB.INI" /i
DISABLENETWORKPROTOCOLS=0 SAPWD=xxxxx SecurityMode=SQL /L*v
C:\SageQuestLou\MSDE.LOG
I'm guessing the SecurityMode param might help here.
"Louis" <anonymous@.discussions.microsoft.com> wrote in message
news:41C137B8-4DEB-430C-A10D-95200B9060A4@.microsoft.com...
> I'm trying to install MSDE 2000 in and XP environment. I want to install
it in a specific sub-directory therfore, I'm using a setting ini file to
give the instance name, target dir and data dir. I've included both the
command line and ini file below:
> Command Line Entry:
> C:\MSDE2000\setup.exe SAPWD="xxxxxx" /settings
"C:\SageQuestLou\DispatcherDB.INI" /L*v C:\SageQuestLou\MSDE.LOG
> Settings file:
> INSTANCENAME=SageQuest
> DISABLENETWORKPROTOCOLS=0
> SECURITYMODE=SQL
> DATADIR="C:\SageQuestLou\Data\"
> TARGETDIR="C:\SageQuestLou\"
> The installation does occur successfully however it installs using default
parameters. However I don't know what the SA password is and it's not where
I want it to be.
> Can some tell me what wrong with my command line or ini file?
>
> Thanks
> Louis
Monday, March 19, 2012
msde memory setting
What memory settings should i configure to tune msde?
Sometimes it will be installed on a PC but at other times it will be an app
server. On the app server i want to take advantage of the increase in memory.
hi,
Keeper wrote:
> What memory settings should i configure to tune msde?
> Sometimes it will be installed on a PC but at other times it will be
> an app server. On the app server i want to take advantage of the
> increase in memory.
usually you should not manually "tune" SQL Server as it is tailored to self
configure it self...
on the other hand, SQL Server is very resources intensive, and is designed
to take advantage of all the installed available memory (in sys32 processes
limit
)
and it's a very challenging taks to manual configure it for best
performance..
remember that memory usage is database and application dependent, but usage
and workloads dependent too...
Loosely speaking, SQL Server organize it's memory allocation in two distinct
regions, the "buffer pool" (BPool) and the "memory to leave" (MemToLeave)
regions. (I'm excluding use of AWE in order to provide easy understanding
and because MSDE does not admit it)..
so... the BPool is the primary region SQL Server uses for it's internal
matter, while MemToLeave consists of the virtual memory space within the 1gb
user mode address space and the memory not used by the BPool.
when SQL Server starts, it begins calculating the upper limit the BPool can
reach... if no MaxMemory is set, this value will be set to the amount of the
physical memory or the size of the user mode address space (1gb) , minus the
size of the MemToLeave, whichever is less..
by default, MemToLeave is set to 384mb, 128mb of them are for worker thread
stacks and 256mb for allocation outside the BPool, such as memory for OLE-DB
providers, linked server drivers, NetLib dlls, in process COM objects space
and memory requirements and so on..
when MaxMemory value is explicitally set, this upper limit will only address
BPool region needs...
so only the address space of BPool pages is limited by this configuration
value, while SQL Server memory requirememts outside BPool allocation are not
limited this way...
more, each connection, live or sleeping, will eat about 24kb of memory,
calculated as 12 KB + 3 times the Network Packet Size (default setting that
can be partially customized via sp_configure system stored procedure
modifying the 'user connections' setting), used to store the data structures
holding the connection 's context, as long as for buffer used to send and
receive the relative associated network streams (default to 4KB network
packet setting), that can be stolen from the buffer pool memory region
and/or the MemToLeave memory area...
not limiting the resources, SQL Server can reclaim that memory (up to 1 gb,
in our example) for it's uses, and it will perhaps release it only under
pressure by the OS claiming for additional memory, if it's the case, else it
will maintain that memory in order to cache pages and execution plans...
under OS pressure, SQL Server will try having the Lazy Writer releasing
resources, but you are not granted that this will occur, even if SQL Server
will always try to leave some memory for other OS needs, usually between 4
and 10mb of RAM... so, on SQL Server dedicated servers, you usually see
memory usage climbing to the top and staying there for long time, becouse of
SQL Server tends to keep pages read from disk in memory to increase further
and successive access to those pages, as long as query plans and so on... on
a heavy loaded server, if you add web server duty, you will have resources
contentions for sure...
I strongly advice you for
http://www.windowsitpro.com/Article/...908/37908.html and
http://www.windowsitpro.com/Article/...890/37890.html
another interesting readings:
http://msdn.microsoft.com/library/de...v_03252004.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi,
Keeper wrote:
> What memory settings should i configure to tune msde?
> Sometimes it will be installed on a PC but at other times it will be
> an app server. On the app server i want to take advantage of the
> increase in memory.
usually you should not manually "tune" SQL Server as it is tailored to self
configure it self...
on the other hand, SQL Server is very resources intensive, and is designed
to take advantage of all the installed available memory (in sys32 processes
limit )
and it's a very challenging taks to manual configure it for best
performance..
remember that memory usage is database and application dependent, but usage
and workloads dependent too...
Loosely speaking, SQL Server organize it's memory allocation in two distinct
regions, the "buffer pool" (BPool) and the "memory to leave" (MemToLeave)
regions. (I'm excluding use of AWE in order to provide easy understanding
and because MSDE does not admit it)..
so... the BPool is the primary region SQL Server uses for it's internal
matter, while MemToLeave consists of the virtual memory space within the 1gb
user mode address space and the memory not used by the BPool.
when SQL Server starts, it begins calculating the upper limit the BPool can
reach... if no MaxMemory is set, this value will be set to the amount of the
physical memory or the size of the user mode address space (1gb) , minus the
size of the MemToLeave, whichever is less..
by default, MemToLeave is set to 384mb, 128mb of them are for worker thread
stacks and 256mb for allocation outside the BPool, such as memory for OLE-DB
providers, linked server drivers, NetLib dlls, in process COM objects space
and memory requirements and so on..
when MaxMemory value is explicitally set, this upper limit will only address
BPool region needs...
so only the address space of BPool pages is limited by this configuration
value, while SQL Server memory requirememts outside BPool allocation are not
limited this way...
more, each connection, live or sleeping, will eat about 24kb of memory,
calculated as 12 KB + 3 times the Network Packet Size (default setting that
can be partially customized via sp_configure system stored procedure
modifying the 'user connections' setting), used to store the data structures
holding the connection 's context, as long as for buffer used to send and
receive the relative associated network streams (default to 4KB network
packet setting), that can be stolen from the buffer pool memory region
and/or the MemToLeave memory area...
not limiting the resources, SQL Server can reclaim that memory (up to 1 gb,
in our example) for it's uses, and it will perhaps release it only under
pressure by the OS claiming for additional memory, if it's the case, else it
will maintain that memory in order to cache pages and execution plans...
under OS pressure, SQL Server will try having the Lazy Writer releasing
resources, but you are not granted that this will occur, even if SQL Server
will always try to leave some memory for other OS needs, usually between 4
and 10mb of RAM... so, on SQL Server dedicated servers, you usually see
memory usage climbing to the top and staying there for long time, becouse of
SQL Server tends to keep pages read from disk in memory to increase further
and successive access to those pages, as long as query plans and so on... on
a heavy loaded server, if you add web server duty, you will have resources
contentions for sure...
I strongly advice you for
http://www.windowsitpro.com/Article/...908/37908.html and
http://www.windowsitpro.com/Article/...890/37890.html
another interesting readings:
http://msdn.microsoft.com/library/de...v_03252004.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||i appreciate the information
thanx
"Andrea Montanari" wrote:
> hi,
> Keeper wrote:
> usually you should not manually "tune" SQL Server as it is tailored to self
> configure it self...
> on the other hand, SQL Server is very resources intensive, and is designed
> to take advantage of all the installed available memory (in sys32 processes
> limit )
> and it's a very challenging taks to manual configure it for best
> performance..
> remember that memory usage is database and application dependent, but usage
> and workloads dependent too...
> Loosely speaking, SQL Server organize it's memory allocation in two distinct
> regions, the "buffer pool" (BPool) and the "memory to leave" (MemToLeave)
> regions. (I'm excluding use of AWE in order to provide easy understanding
> and because MSDE does not admit it)..
> so... the BPool is the primary region SQL Server uses for it's internal
> matter, while MemToLeave consists of the virtual memory space within the 1gb
> user mode address space and the memory not used by the BPool.
> when SQL Server starts, it begins calculating the upper limit the BPool can
> reach... if no MaxMemory is set, this value will be set to the amount of the
> physical memory or the size of the user mode address space (1gb) , minus the
> size of the MemToLeave, whichever is less..
> by default, MemToLeave is set to 384mb, 128mb of them are for worker thread
> stacks and 256mb for allocation outside the BPool, such as memory for OLE-DB
> providers, linked server drivers, NetLib dlls, in process COM objects space
> and memory requirements and so on..
> when MaxMemory value is explicitally set, this upper limit will only address
> BPool region needs...
> so only the address space of BPool pages is limited by this configuration
> value, while SQL Server memory requirememts outside BPool allocation are not
> limited this way...
> more, each connection, live or sleeping, will eat about 24kb of memory,
> calculated as 12 KB + 3 times the Network Packet Size (default setting that
> can be partially customized via sp_configure system stored procedure
> modifying the 'user connections' setting), used to store the data structures
> holding the connection 's context, as long as for buffer used to send and
> receive the relative associated network streams (default to 4KB network
> packet setting), that can be stolen from the buffer pool memory region
> and/or the MemToLeave memory area...
> not limiting the resources, SQL Server can reclaim that memory (up to 1 gb,
> in our example) for it's uses, and it will perhaps release it only under
> pressure by the OS claiming for additional memory, if it's the case, else it
> will maintain that memory in order to cache pages and execution plans...
> under OS pressure, SQL Server will try having the Lazy Writer releasing
> resources, but you are not granted that this will occur, even if SQL Server
> will always try to leave some memory for other OS needs, usually between 4
> and 10mb of RAM... so, on SQL Server dedicated servers, you usually see
> memory usage climbing to the top and staying there for long time, becouse of
> SQL Server tends to keep pages read from disk in memory to increase further
> and successive access to those pages, as long as query plans and so on... on
> a heavy loaded server, if you add web server duty, you will have resources
> contentions for sure...
> I strongly advice you for
> http://www.windowsitpro.com/Article/...908/37908.html and
> http://www.windowsitpro.com/Article/...890/37890.html
> another interesting readings:
> http://msdn.microsoft.com/library/de...v_03252004.asp
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
Sometimes it will be installed on a PC but at other times it will be an app
server. On the app server i want to take advantage of the increase in memory.
hi,
Keeper wrote:
> What memory settings should i configure to tune msde?
> Sometimes it will be installed on a PC but at other times it will be
> an app server. On the app server i want to take advantage of the
> increase in memory.
usually you should not manually "tune" SQL Server as it is tailored to self
configure it self...
on the other hand, SQL Server is very resources intensive, and is designed
to take advantage of all the installed available memory (in sys32 processes
limit
)and it's a very challenging taks to manual configure it for best
performance..
remember that memory usage is database and application dependent, but usage
and workloads dependent too...
Loosely speaking, SQL Server organize it's memory allocation in two distinct
regions, the "buffer pool" (BPool) and the "memory to leave" (MemToLeave)
regions. (I'm excluding use of AWE in order to provide easy understanding
and because MSDE does not admit it)..
so... the BPool is the primary region SQL Server uses for it's internal
matter, while MemToLeave consists of the virtual memory space within the 1gb
user mode address space and the memory not used by the BPool.
when SQL Server starts, it begins calculating the upper limit the BPool can
reach... if no MaxMemory is set, this value will be set to the amount of the
physical memory or the size of the user mode address space (1gb) , minus the
size of the MemToLeave, whichever is less..
by default, MemToLeave is set to 384mb, 128mb of them are for worker thread
stacks and 256mb for allocation outside the BPool, such as memory for OLE-DB
providers, linked server drivers, NetLib dlls, in process COM objects space
and memory requirements and so on..
when MaxMemory value is explicitally set, this upper limit will only address
BPool region needs...
so only the address space of BPool pages is limited by this configuration
value, while SQL Server memory requirememts outside BPool allocation are not
limited this way...
more, each connection, live or sleeping, will eat about 24kb of memory,
calculated as 12 KB + 3 times the Network Packet Size (default setting that
can be partially customized via sp_configure system stored procedure
modifying the 'user connections' setting), used to store the data structures
holding the connection 's context, as long as for buffer used to send and
receive the relative associated network streams (default to 4KB network
packet setting), that can be stolen from the buffer pool memory region
and/or the MemToLeave memory area...
not limiting the resources, SQL Server can reclaim that memory (up to 1 gb,
in our example) for it's uses, and it will perhaps release it only under
pressure by the OS claiming for additional memory, if it's the case, else it
will maintain that memory in order to cache pages and execution plans...
under OS pressure, SQL Server will try having the Lazy Writer releasing
resources, but you are not granted that this will occur, even if SQL Server
will always try to leave some memory for other OS needs, usually between 4
and 10mb of RAM... so, on SQL Server dedicated servers, you usually see
memory usage climbing to the top and staying there for long time, becouse of
SQL Server tends to keep pages read from disk in memory to increase further
and successive access to those pages, as long as query plans and so on... on
a heavy loaded server, if you add web server duty, you will have resources
contentions for sure...
I strongly advice you for
http://www.windowsitpro.com/Article/...908/37908.html and
http://www.windowsitpro.com/Article/...890/37890.html
another interesting readings:
http://msdn.microsoft.com/library/de...v_03252004.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi,
Keeper wrote:
> What memory settings should i configure to tune msde?
> Sometimes it will be installed on a PC but at other times it will be
> an app server. On the app server i want to take advantage of the
> increase in memory.
usually you should not manually "tune" SQL Server as it is tailored to self
configure it self...
on the other hand, SQL Server is very resources intensive, and is designed
to take advantage of all the installed available memory (in sys32 processes
limit
)and it's a very challenging taks to manual configure it for best
performance..
remember that memory usage is database and application dependent, but usage
and workloads dependent too...
Loosely speaking, SQL Server organize it's memory allocation in two distinct
regions, the "buffer pool" (BPool) and the "memory to leave" (MemToLeave)
regions. (I'm excluding use of AWE in order to provide easy understanding
and because MSDE does not admit it)..
so... the BPool is the primary region SQL Server uses for it's internal
matter, while MemToLeave consists of the virtual memory space within the 1gb
user mode address space and the memory not used by the BPool.
when SQL Server starts, it begins calculating the upper limit the BPool can
reach... if no MaxMemory is set, this value will be set to the amount of the
physical memory or the size of the user mode address space (1gb) , minus the
size of the MemToLeave, whichever is less..
by default, MemToLeave is set to 384mb, 128mb of them are for worker thread
stacks and 256mb for allocation outside the BPool, such as memory for OLE-DB
providers, linked server drivers, NetLib dlls, in process COM objects space
and memory requirements and so on..
when MaxMemory value is explicitally set, this upper limit will only address
BPool region needs...
so only the address space of BPool pages is limited by this configuration
value, while SQL Server memory requirememts outside BPool allocation are not
limited this way...
more, each connection, live or sleeping, will eat about 24kb of memory,
calculated as 12 KB + 3 times the Network Packet Size (default setting that
can be partially customized via sp_configure system stored procedure
modifying the 'user connections' setting), used to store the data structures
holding the connection 's context, as long as for buffer used to send and
receive the relative associated network streams (default to 4KB network
packet setting), that can be stolen from the buffer pool memory region
and/or the MemToLeave memory area...
not limiting the resources, SQL Server can reclaim that memory (up to 1 gb,
in our example) for it's uses, and it will perhaps release it only under
pressure by the OS claiming for additional memory, if it's the case, else it
will maintain that memory in order to cache pages and execution plans...
under OS pressure, SQL Server will try having the Lazy Writer releasing
resources, but you are not granted that this will occur, even if SQL Server
will always try to leave some memory for other OS needs, usually between 4
and 10mb of RAM... so, on SQL Server dedicated servers, you usually see
memory usage climbing to the top and staying there for long time, becouse of
SQL Server tends to keep pages read from disk in memory to increase further
and successive access to those pages, as long as query plans and so on... on
a heavy loaded server, if you add web server duty, you will have resources
contentions for sure...
I strongly advice you for
http://www.windowsitpro.com/Article/...908/37908.html and
http://www.windowsitpro.com/Article/...890/37890.html
another interesting readings:
http://msdn.microsoft.com/library/de...v_03252004.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||i appreciate the information
thanx
"Andrea Montanari" wrote:
> hi,
> Keeper wrote:
> usually you should not manually "tune" SQL Server as it is tailored to self
> configure it self...
> on the other hand, SQL Server is very resources intensive, and is designed
> to take advantage of all the installed available memory (in sys32 processes
> limit
)> and it's a very challenging taks to manual configure it for best
> performance..
> remember that memory usage is database and application dependent, but usage
> and workloads dependent too...
> Loosely speaking, SQL Server organize it's memory allocation in two distinct
> regions, the "buffer pool" (BPool) and the "memory to leave" (MemToLeave)
> regions. (I'm excluding use of AWE in order to provide easy understanding
> and because MSDE does not admit it)..
> so... the BPool is the primary region SQL Server uses for it's internal
> matter, while MemToLeave consists of the virtual memory space within the 1gb
> user mode address space and the memory not used by the BPool.
> when SQL Server starts, it begins calculating the upper limit the BPool can
> reach... if no MaxMemory is set, this value will be set to the amount of the
> physical memory or the size of the user mode address space (1gb) , minus the
> size of the MemToLeave, whichever is less..
> by default, MemToLeave is set to 384mb, 128mb of them are for worker thread
> stacks and 256mb for allocation outside the BPool, such as memory for OLE-DB
> providers, linked server drivers, NetLib dlls, in process COM objects space
> and memory requirements and so on..
> when MaxMemory value is explicitally set, this upper limit will only address
> BPool region needs...
> so only the address space of BPool pages is limited by this configuration
> value, while SQL Server memory requirememts outside BPool allocation are not
> limited this way...
> more, each connection, live or sleeping, will eat about 24kb of memory,
> calculated as 12 KB + 3 times the Network Packet Size (default setting that
> can be partially customized via sp_configure system stored procedure
> modifying the 'user connections' setting), used to store the data structures
> holding the connection 's context, as long as for buffer used to send and
> receive the relative associated network streams (default to 4KB network
> packet setting), that can be stolen from the buffer pool memory region
> and/or the MemToLeave memory area...
> not limiting the resources, SQL Server can reclaim that memory (up to 1 gb,
> in our example) for it's uses, and it will perhaps release it only under
> pressure by the OS claiming for additional memory, if it's the case, else it
> will maintain that memory in order to cache pages and execution plans...
> under OS pressure, SQL Server will try having the Lazy Writer releasing
> resources, but you are not granted that this will occur, even if SQL Server
> will always try to leave some memory for other OS needs, usually between 4
> and 10mb of RAM... so, on SQL Server dedicated servers, you usually see
> memory usage climbing to the top and staying there for long time, becouse of
> SQL Server tends to keep pages read from disk in memory to increase further
> and successive access to those pages, as long as query plans and so on... on
> a heavy loaded server, if you add web server duty, you will have resources
> contentions for sure...
> I strongly advice you for
> http://www.windowsitpro.com/Article/...908/37908.html and
> http://www.windowsitpro.com/Article/...890/37890.html
> another interesting readings:
> http://msdn.microsoft.com/library/de...v_03252004.asp
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
Friday, March 9, 2012
MSDE Installation problem
Hi All
I am having a little trouble setting up MSDE.
I downloaded the most recent version of MSDE (sql2ksp3.exe) from the Microsoft site to my desktop.
I double clcked on the files to extract them, it created a sql2ksp3 dir on c drive.
I went to command prompt and entered the following in the c:/sql2ksp3/msde directory:
setup.exe DISABLENETWORKPROTOCOLS=1 SAPWD=**REMOVED** then enter.
The setup wizard started then finished after about 30 seconds.
I can't find MSDE anywhere as program just a folder with the original setup programs.
I know this is a total gummy question, can anyone point me in the right direction.
I didn't have MSDE or SQL Server prevoiusly on the system.
Thanks in advance
PDid you see a new icon in your systray for MSSQLServer?
I am having a little trouble setting up MSDE.
I downloaded the most recent version of MSDE (sql2ksp3.exe) from the Microsoft site to my desktop.
I double clcked on the files to extract them, it created a sql2ksp3 dir on c drive.
I went to command prompt and entered the following in the c:/sql2ksp3/msde directory:
setup.exe DISABLENETWORKPROTOCOLS=1 SAPWD=**REMOVED** then enter.
The setup wizard started then finished after about 30 seconds.
I can't find MSDE anywhere as program just a folder with the original setup programs.
I know this is a total gummy question, can anyone point me in the right direction.
I didn't have MSDE or SQL Server prevoiusly on the system.
Thanks in advance
PDid you see a new icon in your systray for MSSQLServer?
If you shell out to DOS and type in this, are any results returned?
osql -L
Terri|||Server:
---NONE----
That's what i got! Can you help me how to fix my problem|||Do you have the SQL Server icon in your systray? It looks like a gray CPU and will likely have a red square on it (and when you hover over it it will say Stopped). You need to right-click on the icon and and choose MSSQLServer - Start. Once you've done this, try the osql -L command again.
Terri|||yes i have SQL Server icon on my systray. I tried to open it but the server is empty. so i put my server name but still cannot connect. I right click also and hit start but still the same. when i hover over it it says"Not Connected". It puzzled me!!|||Hi
Thanks for the reply
No there is no SqlServer Icon.
When I do the DOS command (osql -L) it says that is not recognised as an internal or external command, operable program or batch file.
Where do I go from here
P|||Installation problems are the most insidious and the most difficult to troubleshoot.
Can you search for sqlsp.log on your machine and see if there's anything useful in it?
Terri|||Hi Terri
I just did the search for sqlsp.log and nothing came up.
I have saved the the sql2ksp3.exe to a cd so I can try it all again.
If I do, which directory should I be installing it in.
I am using XP Pro and I VS.net 2003.
Also what services should Istop to make sure nothing stuffs it up there.
I stopped my firewall and anti-virus last time, should I stop IIS and anything else?
Thanks for your help
Pete|||Also, did the event viewer show anything helpful?
Unfortunately I am not an MSDE installation expert. The best advice I can give is to search these forums for MSDE Install and see what has been advised in the past.
Are you following the instructions atMSDE 2000 for Developers Using Visual Studio .NET or something similar (such asCustomizing Desktop Engine Setup.exe)?
And also you should use verbose logging to a text file so you can review any installation problems, by using an additional command line parameter: /L*v C:\MSDEsetup.log
I would use the default directories for installation.
Terri|||Hi Terri
I tried installing the VS.net version of the MSDE without luck.
I did get a log though, but I wouldn't know where to start to look for the problem.
Is it possible to email you the log file to check out the problem.
There was no errors in the event viewer although the Dreamweaver MX Application
server did startup each time I tried to install the MSDE.
Thx
Pete|||It would better benefit you to either post the log itself here or a link to it. As much as I want to help I am not confident that I will be able to pinpoint your problem and you would benefit from other eyes looking at it as well.
Presumably the problematic area will be at the end of the log file.
Terri|||me again
the command i used was
setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1 SAPWD=RRR#$GS1 /L*V c:\msdesetup2.log
The log file is like 3,900KB so it is a little large here is the last bit
Needless to say it would take a while to find where it went wrong
Property(S): DataInstanceInstall.24170C3F_A9E4_47C1_8DFE_FD79C2714697 = C:\Program Files\Microsoft SQL Server\MSSQL$VSDOTNET\Install\
Property(S): DataInstance.24170C3F_A9E4_47C1_8DFE_FD79C2714697 = C:\Program Files\Microsoft SQL Server\MSSQL$VSDOTNET\
Property(S): Data.24170C3F_A9E4_47C1_8DFE_FD79C2714697 = C:\
Property(S): DataInstanceData.24170C3F_A9E4_47C1_8DFE_FD79C2714697 = C:\Program Files\Microsoft SQL Server\MSSQL$VSDOTNET\Data\
Property(S): DataInstanceJobs.24170C3F_A9E4_47C1_8DFE_FD79C2714697 = C:\Program Files\Microsoft SQL Server\MSSQL$VSDOTNET\JOBS\
Property(S): DataInstanceLog.24170C3F_A9E4_47C1_8DFE_FD79C2714697 = C:\Program Files\Microsoft SQL Server\MSSQL$VSDOTNET\LOG\
Property(S): InstanceName.24170C3F_A9E4_47C1_8DFE_FD79C2714697 = VSDOTNET
Property(S): PackageCode = {D29DCF7A-8199-4373-BA0D-2F3635EC940C}
Property(S): ProductState = -1
Property(S): PackagecodeChanging = 1
Property(S): INSTANCENAME = VSDOTNET
Property(S): DISABLENETWORKPROTOCOLS = 1
Property(S): SA...
Property(S): CURRENTDIRECTORY = C:\sql2ksp3\MSDE
Property(S): CLIENTUILEVEL = 2
Property(S): CLIENTPROCESSID = 1208
Property(S): VersionDatabase = 110
Property(S): VersionMsi = 2.00
Property(S): WindowsBuild = 2600
Property(S): ServicePackLevel = 1
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 1
Property(S): WindowsFolder = C:\WINDOWS\
Property(S): WindowsVolume = C:\
Property(S): System16Folder = C:\WINDOWS\System\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\DOCUME~1\pete\LOCALS~1\Temp\
Property(S): ProgramFilesFolder = C:\Program Files\
Property(S): CommonFilesFolder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\Documents and Settings\pete\Application Data\
Property(S): FavoritesFolder = C:\Documents and Settings\pete\Favorites\
Property(S): NetHoodFolder = C:\Documents and Settings\pete\NetHood\
Property(S): PersonalFolder = C:\Documents and Settings\pete\My Documents\
Property(S): PrintHoodFolder = C:\Documents and Settings\pete\PrintHood\
Property(S): RecentFolder = C:\Documents and Settings\pete\Recent\
Property(S): SendToFolder = C:\Documents and Settings\pete\SendTo\
Property(S): TemplateFolder = C:\Documents and Settings\All Users\Templates\
Property(S): CommonAppDataFolder = C:\Documents and Settings\All Users\Application Data\
Property(S): LocalAppDataFolder = C:\Documents and Settings\pete\Local Settings\Application Data\
Property(S): MyPicturesFolder = C:\Documents and Settings\pete\My Documents\My Pictures\
Property(S): AdminToolsFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
Property(S): ProgramMenuFolder = C:\Documents and Settings\All Users\Start Menu\Programs\
Property(S): StartMenuFolder = C:\Documents and Settings\All Users\Start Menu\
Property(S): DesktopFolder = C:\Documents and Settings\All Users\Desktop\
Property(S): FontsFolder = C:\WINDOWS\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): Intel = 6
Property(S): PhysicalMemory = 511
Property(S): VirtualMemory = 1010
Property(S): AdminUser = 1
Property(S): LogonUser = xxxxxx
Property(S): UserSID = S-1-5-21-3088462085-1224436771-4233946611-1005
Property(S): UserLanguageID = 3081
Property(S): ComputerName = xxxxx
Property(S): SystemLanguageID = 1033
Property(S): ScreenX = 1280
Property(S): ScreenY = 800
Property(S): CaptionHeight = 26
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): MsiNetAssemblySupport = 1.1.4322.573
Property(S): MsiWin32AssemblySupport = 5.1.2600.1515
Property(S): RedirectedDllSupport = 2
Property(S): Time = 13:10:21
Property(S): Date = 7/08/2004
Property(S): Privileged = 1
Property(S): USERNAME =
Property(S): COMPANYNAME =
Property(S): DATABASE = C:\WINDOWS\Installer\678b2d.msi
Property(S): OriginalDatabase = C:\sql2ksp3\MSDE\Setup\SqlRun01.msi
Property(S): UILevel = 3
Property(S): ACTION = INSTALL
Property(S): AgentServiceName = SQLAgent$VSDOTNET
Property(S): InstanceRegKey = Microsoft SQL Server\VSDOTNET
Property(S): InstanceSubDir = MSSQL$VSDOTNET
Property(S): SqlPerfMonRegKey = SQLCTR$VSDOTNET
Property(S): SQLServiceName = MSSQL$VSDOTNET
Property(S): SqlStates = 0
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): SqlFeature = SqlRun
Property(S): SOURCEDIR = C:\sql2ksp3\MSDE\Setup\
Property(S): SourcedirProduct = {E09B48B5-E141-427A-AB0C-D3605127224A}
Property(S): ProductToBeRegistered = 1
=== Logging stopped: 7/08/2004 13:10:21 ===
MSI (s) (20:60): Note: 1: 1708
MSI (s) (20:60): Product: Microsoft SQL Server Desktop Engine -- Installation operation failed.
MSI (s) (20:60): Cleaning up uninstalled install packages, if any exist
MSI (s) (20:60): MainEngineThread is returning 1603
MSI (c) (B8:F8): Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (B8:F8): MainEngineThread is returning 1603
=== Verbose logging stopped: 7/08/2004 13:10:21 ===
once again thx for your help
I am checking the net for solutions, maybe I shouldn't give it an instance name
Pete|||The 2 things I've been able to locate concerning this are: 1) make sure you have the latest MDAC installed and 2) make sure you have the Server service started (You Cannot Install MSDE 2000 if the Server Service Is Not Running).
And I have also seen the recommendation to look for the string "return value 3" in the log file to further identify where the point of failure is.
Terri|||Me again
I found 2 instances of return value 3:
MSI (s) (20:60): Executing op: ActionStart(Name=InstallAgentSecurity.2D02443E_7002_4C0B_ABC9_EAB2C064397B,,)
Action 13:09:53: InstallAgentSecurity.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
MSI (s) (20:60): Executing op: CustomActionSchedule(Action=InstallAgentSecurity.2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=1025,Source=BinaryData,Target=InstallSQLAgentSecurity,)
MSI (s) (20:60): Creating MSIHANDLE (260) of type 790536 for thread 2144
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (PODJIE-LAP,LocalSystem,87).
Action ended 13:09:54: InstallFinalize. Return value 3. <<=============
MSI (s) (20:60): User policy value 'DisableRollback' is 0
MSI (s) (20:60): Machine policy value 'DisableRollback' is 0
MSI (s) (20:60): Executing op: Header(Signature=1397708873,Version=200,Timestamp=822569229,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
--------------------
and here
MSI (s) (20:60): Creating MSIHANDLE (282) of type 790536 for thread 2144
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\setupex.dll
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqdedev.dll
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlsut.dll
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlunirl.dll
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlresld.dll
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.rll
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlstp.dll
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlstp.rll
Deleted Support file : C:\DOCUME~1\pete\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
Rollback: RollbackDeferProperties.2D02443E_7002_4C0B_ABC9_EAB2C064397B
MSI (s) (20:60): Executing op: ActionStart(Name=RollbackDeferProperties.2D02443E_7002_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (20:60): Executing op: CustomActionRollback(Action=RollbackDeferProperties.2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=1281,Source=BinaryData,Target=DeferProperties,)
MSI (s) (20:60): Creating MSIHANDLE (293) of type 790536 for thread 2144
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Start custom action DeferProperties
Defer Properties returns: 0
MSI (s) (20:60): Executing op: End(Checksum=0,ProgressTotal=0)
MSI (s) (20:60): Error in rollback skipped. Return: 5
MSI (s) (20:60): FEATURECACHE: Entering Invalidate
MSI (s) (20:60): Calling SRSetRestorePoint API. dwRestorePtType: 13, dwEventType: 103, llSequenceNumber: 171, szDescription: "".
MSI (s) (20:60): The call to SRSetRestorePoint API succeeded. Returned status: 0.
MSI (s) (20:60): Unlocking Server
MSI (s) (20:60): Note: 1: 33
Action ended 13:10:19: INSTALL. Return value 3.<<<===================
------------
I am checking up on MDAC side of things and i'll get back to you
Pete|||The key is definitely the "InstallSQLAgentSecurity failed". Check the article on the Server service that I provided in a previous post. And if that doesn't help matters, check out this link:InstallSQLAgentSecurity failed.
You're getting closer, I can feel it :-)
Terri
Subscribe to:
Posts (Atom)