How do I backup databases, onto Veritas Backup? In the Enterprise Edition if
I expand the database server I could select all task, backup database and
select the destination.
"OSA" <OSA@.discussions.microsoft.com> wrote in message
news:58C5D3AA-D2FC-419E-B560-DD5703546B5A@.microsoft.com...
> How do I backup databases, onto Veritas Backup? In the Enterprise Edition
if
> I expand the database server I could select all task, backup database and
> select the destination.
If you've got the Veritas netbackup SQL Server agent, you can configure
netback to capture all relevant databases. If not, you can use the SQL
Server backup database task wizard to backup your databases, then use
netbackup to backup these files.
Steve
Showing posts with label edition. Show all posts
Showing posts with label edition. Show all posts
Wednesday, March 28, 2012
New To Databasing
I have just a general question that I was hoping to have answered about the SQL Server Express edition software. I was looking at the data types that you can select from while creating tables and was wondering about other types of data that it can support. I wanted to find out if it supports audio files as one of the data types. I know from MS Access its a OLE object datatype that supports audio files. Is SQL Server Express even capable of handling such data types? Or any other data types that are not text or integers? Anybodys input would be greatly appreciated. Thanks! ~[MikE]~
|||
You can store any file (or data) as raw binary with the varbinary datatype.
Use varbinary(max) to store data larger than 8000 bytes.
|||Hey thanks for clearing that up for me, I really appreciuate the help, you're like the only one that resoponded out of 20 views, and yea I know it was probably a dumb question, but I just need to make sure. Thanks a lot! ~[MikE]~|||
No question is dumb, it would be naive to think like that. Some questions can be answered by searching but then it is not always obvious what to search for.
Browse around a bit and you might be able to help others here, with something that you have experience with. This is a community where we help each other. It might take some time but most questions gets answered.
|||Hey thanks Andreas! Im looking foward to learning a lot from everybod on here. Much Appreciated!sqlMonday, March 26, 2012
New subscription wizard never completes or even errors (SQL 2005 Trans repl with Queued Up
I am testing replication (Transactional with Queued Updating) between SQL
Server 2005 Developer Edition (which is on a domain) and SQL Express (which
is on a machine on same LAN but in a workgroup). I have configured the
publisher as its own distributor and created a publication consisting of 2
views (1 indexed, 1 regular). My problem is that when I run the New
Subscription Wizard, after clicking Finish the process hangs forever on the
first step ("Creating Subscription For ....."). No errors appear, nothing.
Clicking Stop has no effect.
Both views are tiny, only returning half a dozen rows. I have also tried
with a publication containing only one small table, and the same thing
occurs.
The publisher is clearly able to connect to the subscriber because the
linked server is created on the subscriber successfully. There is no sign of
a subscription however on the subscriber.
Here is the configuration for the subscription (following steps in New
Subscription Wizard):
Push subscription
Subscription database is new blank database
Distribution Agent Security: Run under SQL Agent service account, Connects
to distributor by impersonation, Connects to subscriber using a SysAdmin SQL
login
Schedule: runs continuously
Queued updating
Create new linked server using same SysAdmin SQL login as above
Initialize subscription immediately
What could be wrong?
Can you script out your publication creation steps and then run it manually
through Query Analyzer or the SSMS and see where it hangs. This should give
you some indication of where the problem is.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
news:eyE7utcAHHA.3396@.TK2MSFTNGP02.phx.gbl...
>I am testing replication (Transactional with Queued Updating) between SQL
>Server 2005 Developer Edition (which is on a domain) and SQL Express (which
>is on a machine on same LAN but in a workgroup). I have configured the
>publisher as its own distributor and created a publication consisting of 2
>views (1 indexed, 1 regular). My problem is that when I run the New
>Subscription Wizard, after clicking Finish the process hangs forever on the
>first step ("Creating Subscription For ....."). No errors appear, nothing.
>Clicking Stop has no effect.
> Both views are tiny, only returning half a dozen rows. I have also tried
> with a publication containing only one small table, and the same thing
> occurs.
> The publisher is clearly able to connect to the subscriber because the
> linked server is created on the subscriber successfully. There is no sign
> of a subscription however on the subscriber.
> Here is the configuration for the subscription (following steps in New
> Subscription Wizard):
> Push subscription
> Subscription database is new blank database
> Distribution Agent Security: Run under SQL Agent service account, Connects
> to distributor by impersonation, Connects to subscriber using a SysAdmin
> SQL login
> Schedule: runs continuously
> Queued updating
> Create new linked server using same SysAdmin SQL login as above
> Initialize subscription immediately
> What could be wrong?
>
|||The step that hangs is the last step - the execution of sp_link_publication
on the subscriber:
exec sp_link_publication @.publisher = N'LAURENCEN\SQL2005', @.publisher_db =
N'RMIS_QA', @.publication = N'test views', @.distributor =
N'LAURENCEN\SQL2005', @.security_mode = 0, @.login = N'xxxxx', @.password =
N'xxxx'
In the Application Event log the following error appears:
MS DTC is unable to communicate with MS DTC on a remote system. No common
RPC protocol is supported between the two systems. Please ensure that one
or more of the following RPC protocols are common to both systems: TCP/IP,
SPX, or NetBEUI. Error Specifics: .\iomgrclt.cpp:204, Pid: 904, CmdLine:
C:\WINNT\System32\msdtc.exe
I have checked that the MSDTC service is running on publisher and
subscriber. The publisher server is Windows XP SP2 and from googling it
looks like DTC is not given network access by default, however I have
enabled the required settings and the error persists:
In Admin tools.Component Services or via Component Services MSC Snap-in
- right-click the appropriate computer node and select properties
- on the MSDTC tab click Security Configuration button
- in addition to the Network DTC Access being ticked, tick Allow Remote
Clients, Allow Inbound, Allow Outbound
- restart MSDTC
The subscriber server is Windows 2000 Workstation, and it doesn't look like
there are any DTC settings to configure.
"Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
news:eyE7utcAHHA.3396@.TK2MSFTNGP02.phx.gbl...
>I am testing replication (Transactional with Queued Updating) between SQL
>Server 2005 Developer Edition (which is on a domain) and SQL Express (which
>is on a machine on same LAN but in a workgroup). I have configured the
>publisher as its own distributor and created a publication consisting of 2
>views (1 indexed, 1 regular). My problem is that when I run the New
>Subscription Wizard, after clicking Finish the process hangs forever on the
>first step ("Creating Subscription For ....."). No errors appear, nothing.
>Clicking Stop has no effect.
> Both views are tiny, only returning half a dozen rows. I have also tried
> with a publication containing only one small table, and the same thing
> occurs.
> The publisher is clearly able to connect to the subscriber because the
> linked server is created on the subscriber successfully. There is no sign
> of a subscription however on the subscriber.
> Here is the configuration for the subscription (following steps in New
> Subscription Wizard):
> Push subscription
> Subscription database is new blank database
> Distribution Agent Security: Run under SQL Agent service account, Connects
> to distributor by impersonation, Connects to subscriber using a SysAdmin
> SQL login
> Schedule: runs continuously
> Queued updating
> Create new linked server using same SysAdmin SQL login as above
> Initialize subscription immediately
> What could be wrong?
>
|||Is this an upgrade from SQL 2000? There are some issues with a remote
distributor in an upgrade. Basically the repl_distributor remote server is
modified to a linked server and there have been cases where you have to
update the passwords to get this to work. AFAIK - MSDTC is not involved in
queued replication.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
news:O%237HO7oAHHA.5068@.TK2MSFTNGP02.phx.gbl...
> The step that hangs is the last step - the execution of
> sp_link_publication on the subscriber:
> exec sp_link_publication @.publisher = N'LAURENCEN\SQL2005', @.publisher_db
> = N'RMIS_QA', @.publication = N'test views', @.distributor =
> N'LAURENCEN\SQL2005', @.security_mode = 0, @.login = N'xxxxx', @.password =
> N'xxxx'
> In the Application Event log the following error appears:
> MS DTC is unable to communicate with MS DTC on a remote system. No common
> RPC protocol is supported between the two systems. Please ensure that one
> or more of the following RPC protocols are common to both systems:
> TCP/IP, SPX, or NetBEUI. Error Specifics: .\iomgrclt.cpp:204, Pid: 904,
> CmdLine: C:\WINNT\System32\msdtc.exe
> I have checked that the MSDTC service is running on publisher and
> subscriber. The publisher server is Windows XP SP2 and from googling it
> looks like DTC is not given network access by default, however I have
> enabled the required settings and the error persists:
> In Admin tools.Component Services or via Component Services MSC Snap-in
> - right-click the appropriate computer node and select properties
> - on the MSDTC tab click Security Configuration button
> - in addition to the Network DTC Access being ticked, tick Allow Remote
> Clients, Allow Inbound, Allow Outbound
> - restart MSDTC
> The subscriber server is Windows 2000 Workstation, and it doesn't look
> like there are any DTC settings to configure.
>
> "Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
> news:eyE7utcAHHA.3396@.TK2MSFTNGP02.phx.gbl...
>
|||I figured it out after a long search.
MSDTC is involved, at least to set up the subscription. MSDTC in Windows XP
(and Win 2003 also I think) has some network access settings that are set to
prevent any access from outside by default. I mentioned these before.
However, in addition to setting these settings to allow network access,
there is a security setting for RPC, which I missed. This is the registry
key:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Win dows
NT\RPC\RestrictRemoteClients
This needs to exist and have a value of 0 (DWORD) if the subscriber is
Windows 2000.
For more info read:
http://blogs.msdn.com/florinlazar/archive/2004/06/18/159127.aspx
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx#XSLTsection128121120120
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23tmOUdqAHHA.3536@.TK2MSFTNGP03.phx.gbl...
> Is this an upgrade from SQL 2000? There are some issues with a remote
> distributor in an upgrade. Basically the repl_distributor remote server is
> modified to a linked server and there have been cases where you have to
> update the passwords to get this to work. AFAIK - MSDTC is not involved in
> queued replication.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
> news:O%237HO7oAHHA.5068@.TK2MSFTNGP02.phx.gbl...
>
Server 2005 Developer Edition (which is on a domain) and SQL Express (which
is on a machine on same LAN but in a workgroup). I have configured the
publisher as its own distributor and created a publication consisting of 2
views (1 indexed, 1 regular). My problem is that when I run the New
Subscription Wizard, after clicking Finish the process hangs forever on the
first step ("Creating Subscription For ....."). No errors appear, nothing.
Clicking Stop has no effect.
Both views are tiny, only returning half a dozen rows. I have also tried
with a publication containing only one small table, and the same thing
occurs.
The publisher is clearly able to connect to the subscriber because the
linked server is created on the subscriber successfully. There is no sign of
a subscription however on the subscriber.
Here is the configuration for the subscription (following steps in New
Subscription Wizard):
Push subscription
Subscription database is new blank database
Distribution Agent Security: Run under SQL Agent service account, Connects
to distributor by impersonation, Connects to subscriber using a SysAdmin SQL
login
Schedule: runs continuously
Queued updating
Create new linked server using same SysAdmin SQL login as above
Initialize subscription immediately
What could be wrong?
Can you script out your publication creation steps and then run it manually
through Query Analyzer or the SSMS and see where it hangs. This should give
you some indication of where the problem is.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
news:eyE7utcAHHA.3396@.TK2MSFTNGP02.phx.gbl...
>I am testing replication (Transactional with Queued Updating) between SQL
>Server 2005 Developer Edition (which is on a domain) and SQL Express (which
>is on a machine on same LAN but in a workgroup). I have configured the
>publisher as its own distributor and created a publication consisting of 2
>views (1 indexed, 1 regular). My problem is that when I run the New
>Subscription Wizard, after clicking Finish the process hangs forever on the
>first step ("Creating Subscription For ....."). No errors appear, nothing.
>Clicking Stop has no effect.
> Both views are tiny, only returning half a dozen rows. I have also tried
> with a publication containing only one small table, and the same thing
> occurs.
> The publisher is clearly able to connect to the subscriber because the
> linked server is created on the subscriber successfully. There is no sign
> of a subscription however on the subscriber.
> Here is the configuration for the subscription (following steps in New
> Subscription Wizard):
> Push subscription
> Subscription database is new blank database
> Distribution Agent Security: Run under SQL Agent service account, Connects
> to distributor by impersonation, Connects to subscriber using a SysAdmin
> SQL login
> Schedule: runs continuously
> Queued updating
> Create new linked server using same SysAdmin SQL login as above
> Initialize subscription immediately
> What could be wrong?
>
|||The step that hangs is the last step - the execution of sp_link_publication
on the subscriber:
exec sp_link_publication @.publisher = N'LAURENCEN\SQL2005', @.publisher_db =
N'RMIS_QA', @.publication = N'test views', @.distributor =
N'LAURENCEN\SQL2005', @.security_mode = 0, @.login = N'xxxxx', @.password =
N'xxxx'
In the Application Event log the following error appears:
MS DTC is unable to communicate with MS DTC on a remote system. No common
RPC protocol is supported between the two systems. Please ensure that one
or more of the following RPC protocols are common to both systems: TCP/IP,
SPX, or NetBEUI. Error Specifics: .\iomgrclt.cpp:204, Pid: 904, CmdLine:
C:\WINNT\System32\msdtc.exe
I have checked that the MSDTC service is running on publisher and
subscriber. The publisher server is Windows XP SP2 and from googling it
looks like DTC is not given network access by default, however I have
enabled the required settings and the error persists:
In Admin tools.Component Services or via Component Services MSC Snap-in
- right-click the appropriate computer node and select properties
- on the MSDTC tab click Security Configuration button
- in addition to the Network DTC Access being ticked, tick Allow Remote
Clients, Allow Inbound, Allow Outbound
- restart MSDTC
The subscriber server is Windows 2000 Workstation, and it doesn't look like
there are any DTC settings to configure.
"Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
news:eyE7utcAHHA.3396@.TK2MSFTNGP02.phx.gbl...
>I am testing replication (Transactional with Queued Updating) between SQL
>Server 2005 Developer Edition (which is on a domain) and SQL Express (which
>is on a machine on same LAN but in a workgroup). I have configured the
>publisher as its own distributor and created a publication consisting of 2
>views (1 indexed, 1 regular). My problem is that when I run the New
>Subscription Wizard, after clicking Finish the process hangs forever on the
>first step ("Creating Subscription For ....."). No errors appear, nothing.
>Clicking Stop has no effect.
> Both views are tiny, only returning half a dozen rows. I have also tried
> with a publication containing only one small table, and the same thing
> occurs.
> The publisher is clearly able to connect to the subscriber because the
> linked server is created on the subscriber successfully. There is no sign
> of a subscription however on the subscriber.
> Here is the configuration for the subscription (following steps in New
> Subscription Wizard):
> Push subscription
> Subscription database is new blank database
> Distribution Agent Security: Run under SQL Agent service account, Connects
> to distributor by impersonation, Connects to subscriber using a SysAdmin
> SQL login
> Schedule: runs continuously
> Queued updating
> Create new linked server using same SysAdmin SQL login as above
> Initialize subscription immediately
> What could be wrong?
>
|||Is this an upgrade from SQL 2000? There are some issues with a remote
distributor in an upgrade. Basically the repl_distributor remote server is
modified to a linked server and there have been cases where you have to
update the passwords to get this to work. AFAIK - MSDTC is not involved in
queued replication.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
news:O%237HO7oAHHA.5068@.TK2MSFTNGP02.phx.gbl...
> The step that hangs is the last step - the execution of
> sp_link_publication on the subscriber:
> exec sp_link_publication @.publisher = N'LAURENCEN\SQL2005', @.publisher_db
> = N'RMIS_QA', @.publication = N'test views', @.distributor =
> N'LAURENCEN\SQL2005', @.security_mode = 0, @.login = N'xxxxx', @.password =
> N'xxxx'
> In the Application Event log the following error appears:
> MS DTC is unable to communicate with MS DTC on a remote system. No common
> RPC protocol is supported between the two systems. Please ensure that one
> or more of the following RPC protocols are common to both systems:
> TCP/IP, SPX, or NetBEUI. Error Specifics: .\iomgrclt.cpp:204, Pid: 904,
> CmdLine: C:\WINNT\System32\msdtc.exe
> I have checked that the MSDTC service is running on publisher and
> subscriber. The publisher server is Windows XP SP2 and from googling it
> looks like DTC is not given network access by default, however I have
> enabled the required settings and the error persists:
> In Admin tools.Component Services or via Component Services MSC Snap-in
> - right-click the appropriate computer node and select properties
> - on the MSDTC tab click Security Configuration button
> - in addition to the Network DTC Access being ticked, tick Allow Remote
> Clients, Allow Inbound, Allow Outbound
> - restart MSDTC
> The subscriber server is Windows 2000 Workstation, and it doesn't look
> like there are any DTC settings to configure.
>
> "Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
> news:eyE7utcAHHA.3396@.TK2MSFTNGP02.phx.gbl...
>
|||I figured it out after a long search.
MSDTC is involved, at least to set up the subscription. MSDTC in Windows XP
(and Win 2003 also I think) has some network access settings that are set to
prevent any access from outside by default. I mentioned these before.
However, in addition to setting these settings to allow network access,
there is a security setting for RPC, which I missed. This is the registry
key:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Win dows
NT\RPC\RestrictRemoteClients
This needs to exist and have a value of 0 (DWORD) if the subscriber is
Windows 2000.
For more info read:
http://blogs.msdn.com/florinlazar/archive/2004/06/18/159127.aspx
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx#XSLTsection128121120120
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23tmOUdqAHHA.3536@.TK2MSFTNGP03.phx.gbl...
> Is this an upgrade from SQL 2000? There are some issues with a remote
> distributor in an upgrade. Basically the repl_distributor remote server is
> modified to a linked server and there have been cases where you have to
> update the passwords to get this to work. AFAIK - MSDTC is not involved in
> queued replication.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Laurence Neville" <laurenceneville@.hotmail.com> wrote in message
> news:O%237HO7oAHHA.5068@.TK2MSFTNGP02.phx.gbl...
>
Friday, March 23, 2012
NEW SQL Server Release`
Check this out
this is the replacement for MSDE 2000
SQL Server 2005 Express Edition (http://lab.msdn.microsoft.com/express/sql/default.aspx)
Top 10 cool things about SQL Server Express Edition (http://lab.msdn.microsoft.com/express/sql/top10/default.aspx)
SQL Server Express Books Online (http://www.microsoft.com/downloads/details.aspx?FamilyId=2ADBC1A8-AE5C-497D-B584-EAB6719300CD&displaylang=en)
by the way if you follow the first link, you will find a pretty accurate photo of rdjabarov...Check this out
you will find a pretty accurate photo of rdjabarov...
Looks pretty nice and decent just like the Express Edition. Where he's from by the way, USA!!|||Hey, you see what you started, Scott? And YOU KNOW I don't look like this!.. And where the h*** did you get 2005 Express? In Ala-freaking-bama?|||Hey now, I'm from Ala-freaking-bama|||Hey, you see what you started, Scott? And YOU KNOW I don't look like this!.. And where the h*** did you get 2005 Express? In Ala-freaking-bama?
i'm just kidding
but on further reflection he kind of looks like fabian pascal.
Pat can verify that for us because as we all know, he's fabian's best friend.|||Do you really believe that I think that way?..Well, I DO love Texas, but I am ready for a change (ideally would be to move without my kids knowing where to :D )|||Anyone else think that CLR is a bunch of nonsense?|||Anyone else think that CLR is a bunch of nonsense?
I think it's VERY neat. I also think that this will force some hard core production DBA's to have a hard look at themselves and see if the career they've chosen is what they want to continue pursuing. Personally, I am happy with a definition that is given to me, - hybrid DBA! And the direction the job description is taking is where I am at now.|||Pat can verify that for us because as we all know, he's fabian's best friend.It's good to be loved, isn't it? Actually, I've never met Fabian in person, or even seen a picture from a reliable source, so I'm no authority there. It's hard to imagine that I've never seen anyone that loves me so, isn't it?
-PatP|||Anyone else think that CLR is a bunch of nonsense?Not really, I think that the CLR brings a lot of interesting benefits, but it brings some new risks in the baggage with it.
The benefits are basically the ones that UCSD promised with the p-machine and Java didn't quite deliver with their virtual machine. A standard, more or less hardware independant virtual machine. One code base for many platforms. One target for many compilers, which allows much better tools to evolve because the economies of scale kick in much sooner.
The big risks seem to be that once something makes it into the runtime, who will ensure that it makes sense for it to stay there as it evolves. Many things that make perfect sense on the desktop (or even handheld) are a positive liability on a server!
It is a two edged sword. It brings many benefits, but at a significant cost.
-PatP|||I think it's VERY neat.
Why? And yes, PROD DBA's who sit there waiting for an alert...sure...but someones got to do that...and I'm glad it's not me...not sure if they even know what a sproc is...let alone a trigger...
And what can you do with "External Procedures" (CLR) that you can't do with T-SQL or it's extensions?
CLR is just more overhead...
And I'd love to see what they mean by Extensive XML support...
What? Did they add Relational extenders to XML?|||Well, I've run to the rescue of "External Procedures" via sp_oaxxx. You're write, the same thing can be accomplished by T-SQL, but the final choice is based on many factors. I prefer to use a tool for a task that is designed to do that task. Of course I can create a file using T-SQL, but if there is a better way to do the same thing (Scripting.FileSystemObject) I'd pick that one.|||i like the concept and intent of the Common Language Runtime.
now you can develop in your native language without having to learn an entirely new discipline.
standardization is a good thing. it allows developers to get back to the act of developing logic instead of all of these funky diversions that we have to endure.
case in point --dbforums.com
what percent of all of the questions raised here are by dba's to dba's about dba stuff.
most of them are actually developers trying to reinvent the wheel in a entirely new discipline (T-sql SQL Server etc..). by giving them a internal wrapper for all of their "stuff" they can truly screw everything up and then call us "The Consultant" to fix it (for a fee of course)|||I think Pat summed it up pretty well. There are some things that the CLR will just do better. There's also a LOT of risk if it's used wrong. The XML thing actually worries me more then the CLR though. It's harking back to the days of hierarchial design and promising "extensibility". I have a feeling we'll end up regretting the degradation of a relational environment to cater to the desires of a shortcut "extend into anything without considering the consequences" world. Oh well....rant off.|||i like the concept and intent of the Common Language Runtime.
now you can develop in your native language without having to learn an entirely new discipline.
standardization is a good thing. it allows developers to get back to the act of developing logic instead of all of these funky diversions that we have to endure.
case in point --dbforums.com
what percent of all of the questions raised here are by dba's to dba's about dba stuff.
most of them are actually developers trying to reinvent the wheel in a entirely new discipline (T-sql SQL Server etc..). by giving them a internal wrapper for all of their "stuff" they can truly screw everything up and then call us "The Consultant" to fix it (for a fee of course)
Right on, man, right on!
this is the replacement for MSDE 2000
SQL Server 2005 Express Edition (http://lab.msdn.microsoft.com/express/sql/default.aspx)
Top 10 cool things about SQL Server Express Edition (http://lab.msdn.microsoft.com/express/sql/top10/default.aspx)
SQL Server Express Books Online (http://www.microsoft.com/downloads/details.aspx?FamilyId=2ADBC1A8-AE5C-497D-B584-EAB6719300CD&displaylang=en)
by the way if you follow the first link, you will find a pretty accurate photo of rdjabarov...Check this out
you will find a pretty accurate photo of rdjabarov...
Looks pretty nice and decent just like the Express Edition. Where he's from by the way, USA!!|||Hey, you see what you started, Scott? And YOU KNOW I don't look like this!.. And where the h*** did you get 2005 Express? In Ala-freaking-bama?|||Hey now, I'm from Ala-freaking-bama|||Hey, you see what you started, Scott? And YOU KNOW I don't look like this!.. And where the h*** did you get 2005 Express? In Ala-freaking-bama?
i'm just kidding
but on further reflection he kind of looks like fabian pascal.
Pat can verify that for us because as we all know, he's fabian's best friend.|||Do you really believe that I think that way?..Well, I DO love Texas, but I am ready for a change (ideally would be to move without my kids knowing where to :D )|||Anyone else think that CLR is a bunch of nonsense?|||Anyone else think that CLR is a bunch of nonsense?
I think it's VERY neat. I also think that this will force some hard core production DBA's to have a hard look at themselves and see if the career they've chosen is what they want to continue pursuing. Personally, I am happy with a definition that is given to me, - hybrid DBA! And the direction the job description is taking is where I am at now.|||Pat can verify that for us because as we all know, he's fabian's best friend.It's good to be loved, isn't it? Actually, I've never met Fabian in person, or even seen a picture from a reliable source, so I'm no authority there. It's hard to imagine that I've never seen anyone that loves me so, isn't it?
-PatP|||Anyone else think that CLR is a bunch of nonsense?Not really, I think that the CLR brings a lot of interesting benefits, but it brings some new risks in the baggage with it.
The benefits are basically the ones that UCSD promised with the p-machine and Java didn't quite deliver with their virtual machine. A standard, more or less hardware independant virtual machine. One code base for many platforms. One target for many compilers, which allows much better tools to evolve because the economies of scale kick in much sooner.
The big risks seem to be that once something makes it into the runtime, who will ensure that it makes sense for it to stay there as it evolves. Many things that make perfect sense on the desktop (or even handheld) are a positive liability on a server!
It is a two edged sword. It brings many benefits, but at a significant cost.
-PatP|||I think it's VERY neat.
Why? And yes, PROD DBA's who sit there waiting for an alert...sure...but someones got to do that...and I'm glad it's not me...not sure if they even know what a sproc is...let alone a trigger...
And what can you do with "External Procedures" (CLR) that you can't do with T-SQL or it's extensions?
CLR is just more overhead...
And I'd love to see what they mean by Extensive XML support...
What? Did they add Relational extenders to XML?|||Well, I've run to the rescue of "External Procedures" via sp_oaxxx. You're write, the same thing can be accomplished by T-SQL, but the final choice is based on many factors. I prefer to use a tool for a task that is designed to do that task. Of course I can create a file using T-SQL, but if there is a better way to do the same thing (Scripting.FileSystemObject) I'd pick that one.|||i like the concept and intent of the Common Language Runtime.
now you can develop in your native language without having to learn an entirely new discipline.
standardization is a good thing. it allows developers to get back to the act of developing logic instead of all of these funky diversions that we have to endure.
case in point --dbforums.com
what percent of all of the questions raised here are by dba's to dba's about dba stuff.
most of them are actually developers trying to reinvent the wheel in a entirely new discipline (T-sql SQL Server etc..). by giving them a internal wrapper for all of their "stuff" they can truly screw everything up and then call us "The Consultant" to fix it (for a fee of course)|||I think Pat summed it up pretty well. There are some things that the CLR will just do better. There's also a LOT of risk if it's used wrong. The XML thing actually worries me more then the CLR though. It's harking back to the days of hierarchial design and promising "extensibility". I have a feeling we'll end up regretting the degradation of a relational environment to cater to the desires of a shortcut "extend into anything without considering the consequences" world. Oh well....rant off.|||i like the concept and intent of the Common Language Runtime.
now you can develop in your native language without having to learn an entirely new discipline.
standardization is a good thing. it allows developers to get back to the act of developing logic instead of all of these funky diversions that we have to endure.
case in point --dbforums.com
what percent of all of the questions raised here are by dba's to dba's about dba stuff.
most of them are actually developers trying to reinvent the wheel in a entirely new discipline (T-sql SQL Server etc..). by giving them a internal wrapper for all of their "stuff" they can truly screw everything up and then call us "The Consultant" to fix it (for a fee of course)
Right on, man, right on!
New SQL Server Registration
Hello,
I just installed SS2K5 Developer's edition (MSDN). I am unable to create a
new SQL Server Registration. Any help with this would be appreciated.
--
Thanks in advance,
sck10What exactly is the problem?
Try View, Registered Servers. Click and then right-click Database Engine,
New, Server Registration. Complete the data, Test and Save.
Ben Nevarez, MCDBA, OCP
Database Administrator
"sck10" wrote:
> Hello,
> I just installed SS2K5 Developer's edition (MSDN). I am unable to create a
> new SQL Server Registration. Any help with this would be appreciated.
> --
> Thanks in advance,
> sck10
>
>
I just installed SS2K5 Developer's edition (MSDN). I am unable to create a
new SQL Server Registration. Any help with this would be appreciated.
--
Thanks in advance,
sck10What exactly is the problem?
Try View, Registered Servers. Click and then right-click Database Engine,
New, Server Registration. Complete the data, Test and Save.
Ben Nevarez, MCDBA, OCP
Database Administrator
"sck10" wrote:
> Hello,
> I just installed SS2K5 Developer's edition (MSDN). I am unable to create a
> new SQL Server Registration. Any help with this would be appreciated.
> --
> Thanks in advance,
> sck10
>
>
New SQL Server Registration
Hello,
I just installed SS2K5 Developer's edition (MSDN). I am unable to create a
new SQL Server Registration. Any help with this would be appreciated.
--
Thanks in advance,
sck10What exactly is the problem?
Try View, Registered Servers. Click and then right-click Database Engine,
New, Server Registration. Complete the data, Test and Save.
Ben Nevarez, MCDBA, OCP
Database Administrator
"sck10" wrote:
> Hello,
> I just installed SS2K5 Developer's edition (MSDN). I am unable to create
a
> new SQL Server Registration. Any help with this would be appreciated.
> --
> Thanks in advance,
> sck10
>
>
I just installed SS2K5 Developer's edition (MSDN). I am unable to create a
new SQL Server Registration. Any help with this would be appreciated.
--
Thanks in advance,
sck10What exactly is the problem?
Try View, Registered Servers. Click and then right-click Database Engine,
New, Server Registration. Complete the data, Test and Save.
Ben Nevarez, MCDBA, OCP
Database Administrator
"sck10" wrote:
> Hello,
> I just installed SS2K5 Developer's edition (MSDN). I am unable to create
a
> new SQL Server Registration. Any help with this would be appreciated.
> --
> Thanks in advance,
> sck10
>
>
New SQL Server Compact edition
Does the new SQL server Compact edition RC1 (release in Dec 2006) replace the Microsoft SQL Server 2005 Mobile Edition Device SDK?
OR is this an additional database for specific requirements.
Currently developing against MS SQL Server 2005 Mobile Edition Device SDK;; if I switch to the Compact edition; is there a migration wiarzrd or Upgrade wizard available?
-jawahar
Basically, that's what I describe in my new EBook. The SQL Server 2005 Compact Edition is a replacement for (an upgrade to) for SQL Mobile. The database structures are the same so there is no need for a conversion wizard or somesuch. The real difference here is that SQLCe is tuned and licensed to run on a Windows Desktop as well where as before it was only licensed for the Tablet PC and PDAs (Windows Mobile OS). See www.hitchhikerguides.net FMI.sqlNew SQL Server 2005 instance
Hi,
I am trying to install a new SQL Server 2005 instance. When running thesetup I get a warning related to "Edition Change Check" that advisesme to run setup with SKUUPGRADE=1. I already have SQL 2005 with SP 1 installed.For the new instance that I am trying to install I use the SQL Server 2005media without sp1. What do I do? Ignore the warning and at the end reapply SP1?
Thanks
The rule thumb with SQL Server installations ignore all Windows questions just answer those relevant to you. And it is better to install the service pack after the installation just download it before you install and copy your CD content into the harddrive and run setup from the harddrive. Hope this helps.|||Sometimes is good to do just that. I have installed the newinstance and then installed the SP1 only for the new instance. There are somecheckboxes there and also you get the current version of the instance. Cool...
sqlMonday, March 12, 2012
New Processes after upgrade
Hi There
After upgrading to Sql Server 2005 Enterprise Edition , SP1.
if i run the following query:
select * from sysprocesses where waittime <> 0 order by waittime desc
I get the following result:
spid waittime lastwaittype status
10 4480 0 0x007E 78424187 ONDEMAND_TASK_QUEUE background
4 5620 0 0x009D 78418906 KSOURCE_WAKEUP background
16 4512 0 0x00A9 78418890 BROKER_TRANSMITTER background
17 4516 0 0x00A9 78418875 BROKER_TRANSMITTER background
12 5056 0 0x00AD 78418796 BROKER_EVENTHANDLER background
11 5728 0 0x0081 179140 CHECKPOINT_QUEUE background
Basscially the waittime just keeps going up infinitely for these processes, is this normal, should i be worried ?
Thanx
Have same issue with BROKER_EVENTHANDLER and BROKER_TRANSMITTER.
Normal behavior?
|||Hi
This link from microsoft describes the various Wait Types (of which there a lot more in SQL Server 2005):
http://msdn2.microsoft.com/en-us/library/ms179984.aspx
Here is some information from it about your specific items.
ONDEMAND_TASK_QUEUE waits for high priority requests (and high wait times simply indicates there have been none of these.)
KSOURCE_WAKEUP waits for requests from the Service Control Manager and long waits are to be expected (pause then unpause the SQL Server service to cause this to reset).
CHECKPOINT_QUEUE - This is the Checkpoint task waiting for the next checkpoint request (few checkpoints = large wait - and that's only 3 minutes).
BROKER_* - These are associated with the service broker and whilst it does not specifically say, I suspect if you do not have service broker servicing requests then these just wait and wait.
If you are interested in monitoring blocking then you might like to read this knowledge base article:
http://support.microsoft.com/kb/271509 - (LiveID required)
This describes sp_blocker_pss80 - a stored procedure to monitor blocked processes in SQL server 2000 up (it does however still produce these system processes in it's list).
New MS SQL Server
How do I backup databases, onto Veritas Backup? In the Enterprise Edition if
I expand the database server I could select all task, backup database and
select the destination. Which is the proper way to backup these databases.
You could get a Veritas agent that will be able to back up the database real
time. The problem with using the plain vanilla Backup EXEC is that it can't
back up a file that is in use. Alternatively, you can use a scheduled task
within Enterprise Manager to back up the database before you backup to tape.
We have ours set up this way and it works well...
Regards,
Hank Arnold
"OSA" <OSA@.discussions.microsoft.com> wrote in message
news:12671BDC-34F2-427E-80EF-753A96DC4818@.microsoft.com...
> How do I backup databases, onto Veritas Backup? In the Enterprise Edition
> if
> I expand the database server I could select all task, backup database and
> select the destination. Which is the proper way to backup these databases.
I expand the database server I could select all task, backup database and
select the destination. Which is the proper way to backup these databases.
You could get a Veritas agent that will be able to back up the database real
time. The problem with using the plain vanilla Backup EXEC is that it can't
back up a file that is in use. Alternatively, you can use a scheduled task
within Enterprise Manager to back up the database before you backup to tape.
We have ours set up this way and it works well...
Regards,
Hank Arnold
"OSA" <OSA@.discussions.microsoft.com> wrote in message
news:12671BDC-34F2-427E-80EF-753A96DC4818@.microsoft.com...
> How do I backup databases, onto Veritas Backup? In the Enterprise Edition
> if
> I expand the database server I could select all task, backup database and
> select the destination. Which is the proper way to backup these databases.
Friday, March 9, 2012
New Instance Install
I installed another instance of SQL Server onto my
machine. I currently have a personal edition and decided
to install a second instance. It failed at MDAC
installation. When I look at the setup log, it says the
installation failed.
My dilema is that I cannot start the previous installation
I had before. When I activate Enterprise Manager, I get a
Snap-in failed to initialize : Microsoft Enterprise
Manager. I tried everything I know to start SQL - but
cannot. Can someone help please?
Mary.Mary,
Try re-installing MDAC 2.7 SP1 and try it again. Let me know if it still
doesn't work
HTH
Thank you,
Saleem@.sqlnt.com
"Mary Lou" wrote:
> I installed another instance of SQL Server onto my
> machine. I currently have a personal edition and decided
> to install a second instance. It failed at MDAC
> installation. When I look at the setup log, it says the
> installation failed.
> My dilema is that I cannot start the previous installation
> I had before. When I activate Enterprise Manager, I get a
> Snap-in failed to initialize : Microsoft Enterprise
> Manager. I tried everything I know to start SQL - but
> cannot. Can someone help please?
> Mary.
>|||Saleem,
I just got back today and tried your suggestion. Saleem,
it worked like a champ. I want to thank you for your
expert advise. Have a good one.
Mary.
>--Original Message--
>Mary,
>Try re-installing MDAC 2.7 SP1 and try it again. Let me
know if it still
>doesn't work
>HTH
>Thank you,
>Saleem@.sqlnt.com
>"Mary Lou" wrote:
>> I installed another instance of SQL Server onto my
>> machine. I currently have a personal edition and
decided
>> to install a second instance. It failed at MDAC
>> installation. When I look at the setup log, it says
the
>> installation failed.
>> My dilema is that I cannot start the previous
installation
>> I had before. When I activate Enterprise Manager, I
get a
>> Snap-in failed to initialize : Microsoft Enterprise
>> Manager. I tried everything I know to start SQL - but
>> cannot. Can someone help please?
>> Mary.
>.
>
machine. I currently have a personal edition and decided
to install a second instance. It failed at MDAC
installation. When I look at the setup log, it says the
installation failed.
My dilema is that I cannot start the previous installation
I had before. When I activate Enterprise Manager, I get a
Snap-in failed to initialize : Microsoft Enterprise
Manager. I tried everything I know to start SQL - but
cannot. Can someone help please?
Mary.Mary,
Try re-installing MDAC 2.7 SP1 and try it again. Let me know if it still
doesn't work
HTH
Thank you,
Saleem@.sqlnt.com
"Mary Lou" wrote:
> I installed another instance of SQL Server onto my
> machine. I currently have a personal edition and decided
> to install a second instance. It failed at MDAC
> installation. When I look at the setup log, it says the
> installation failed.
> My dilema is that I cannot start the previous installation
> I had before. When I activate Enterprise Manager, I get a
> Snap-in failed to initialize : Microsoft Enterprise
> Manager. I tried everything I know to start SQL - but
> cannot. Can someone help please?
> Mary.
>|||Saleem,
I just got back today and tried your suggestion. Saleem,
it worked like a champ. I want to thank you for your
expert advise. Have a good one.
Mary.
>--Original Message--
>Mary,
>Try re-installing MDAC 2.7 SP1 and try it again. Let me
know if it still
>doesn't work
>HTH
>Thank you,
>Saleem@.sqlnt.com
>"Mary Lou" wrote:
>> I installed another instance of SQL Server onto my
>> machine. I currently have a personal edition and
decided
>> to install a second instance. It failed at MDAC
>> installation. When I look at the setup log, it says
the
>> installation failed.
>> My dilema is that I cannot start the previous
installation
>> I had before. When I activate Enterprise Manager, I
get a
>> Snap-in failed to initialize : Microsoft Enterprise
>> Manager. I tried everything I know to start SQL - but
>> cannot. Can someone help please?
>> Mary.
>.
>
New Instance Install
I installed another instance of SQL Server onto my
machine. I currently have a personal edition and decided
to install a second instance. It failed at MDAC
installation. When I look at the setup log, it says the
installation failed.
My dilema is that I cannot start the previous installation
I had before. When I activate Enterprise Manager, I get a
Snap-in failed to initialize : Microsoft Enterprise
Manager. I tried everything I know to start SQL - but
cannot. Can someone help please?
Mary.
Mary,
Try re-installing MDAC 2.7 SP1 and try it again. Let me know if it still
doesn't work
HTH
Thank you,
Saleem@.sqlnt.com
"Mary Lou" wrote:
> I installed another instance of SQL Server onto my
> machine. I currently have a personal edition and decided
> to install a second instance. It failed at MDAC
> installation. When I look at the setup log, it says the
> installation failed.
> My dilema is that I cannot start the previous installation
> I had before. When I activate Enterprise Manager, I get a
> Snap-in failed to initialize : Microsoft Enterprise
> Manager. I tried everything I know to start SQL - but
> cannot. Can someone help please?
> Mary.
>
|||Saleem,
I just got back today and tried your suggestion. Saleem,
it worked like a champ. I want to thank you for your
expert advise. Have a good one.
Mary.
>--Original Message--
>Mary,
>Try re-installing MDAC 2.7 SP1 and try it again. Let me
know if it still[vbcol=seagreen]
>doesn't work
>HTH
>Thank you,
>Saleem@.sqlnt.com
>"Mary Lou" wrote:
decided[vbcol=seagreen]
the[vbcol=seagreen]
installation[vbcol=seagreen]
get a
>.
>
machine. I currently have a personal edition and decided
to install a second instance. It failed at MDAC
installation. When I look at the setup log, it says the
installation failed.
My dilema is that I cannot start the previous installation
I had before. When I activate Enterprise Manager, I get a
Snap-in failed to initialize : Microsoft Enterprise
Manager. I tried everything I know to start SQL - but
cannot. Can someone help please?
Mary.
Mary,
Try re-installing MDAC 2.7 SP1 and try it again. Let me know if it still
doesn't work
HTH
Thank you,
Saleem@.sqlnt.com
"Mary Lou" wrote:
> I installed another instance of SQL Server onto my
> machine. I currently have a personal edition and decided
> to install a second instance. It failed at MDAC
> installation. When I look at the setup log, it says the
> installation failed.
> My dilema is that I cannot start the previous installation
> I had before. When I activate Enterprise Manager, I get a
> Snap-in failed to initialize : Microsoft Enterprise
> Manager. I tried everything I know to start SQL - but
> cannot. Can someone help please?
> Mary.
>
|||Saleem,
I just got back today and tried your suggestion. Saleem,
it worked like a champ. I want to thank you for your
expert advise. Have a good one.
Mary.
>--Original Message--
>Mary,
>Try re-installing MDAC 2.7 SP1 and try it again. Let me
know if it still[vbcol=seagreen]
>doesn't work
>HTH
>Thank you,
>Saleem@.sqlnt.com
>"Mary Lou" wrote:
decided[vbcol=seagreen]
the[vbcol=seagreen]
installation[vbcol=seagreen]
get a
>.
>
Wednesday, March 7, 2012
New Installation of SQL Server 2000
Hi,
I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not support on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New SQL Server DBA
Newbie wrote:
> Hi,
> I installed sql server 2000 sp2 standard edition on Windows 2003, when
> installing, it said "This version is not support on this os", but I
> was told to continue installing the software and that I could install
> the latest security patches to bring it up to date. Will that work?
> Do I need to do anything else? SQL Server 2000 is up and running on
> the box. When running the statement " select @.@.version" it informed
> me that I was at 8.00.194 patch level. How can I tell if SQL Server
> 2000 is 32 or 64 bit? I was trying to download the lasted patch and
> it asked for that info. Thanks.-- New SQL Server DBA
You didn't install SQL 2000 SP2. You installed SQL 2000 RTM (v194). The
installation program at the point SQL 2000 RTM was released didn't know
about Win2K3 and is giving you the error.
Install SP3a on the server and you should be ready to go.
David Gugick
Imceda Software
www.imceda.com
I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not support on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New SQL Server DBA
Newbie wrote:
> Hi,
> I installed sql server 2000 sp2 standard edition on Windows 2003, when
> installing, it said "This version is not support on this os", but I
> was told to continue installing the software and that I could install
> the latest security patches to bring it up to date. Will that work?
> Do I need to do anything else? SQL Server 2000 is up and running on
> the box. When running the statement " select @.@.version" it informed
> me that I was at 8.00.194 patch level. How can I tell if SQL Server
> 2000 is 32 or 64 bit? I was trying to download the lasted patch and
> it asked for that info. Thanks.-- New SQL Server DBA
You didn't install SQL 2000 SP2. You installed SQL 2000 RTM (v194). The
installation program at the point SQL 2000 RTM was released didn't know
about Win2K3 and is giving you the error.
Install SP3a on the server and you should be ready to go.
David Gugick
Imceda Software
www.imceda.com
New Installation of SQL Server 2000
Hi,
I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not support on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New SQL Server DBANewbie wrote:
> Hi,
> I installed sql server 2000 sp2 standard edition on Windows 2003, when
> installing, it said "This version is not support on this os", but I
> was told to continue installing the software and that I could install
> the latest security patches to bring it up to date. Will that work?
> Do I need to do anything else? SQL Server 2000 is up and running on
> the box. When running the statement " select @.@.version" it informed
> me that I was at 8.00.194 patch level. How can I tell if SQL Server
> 2000 is 32 or 64 bit? I was trying to download the lasted patch and
> it asked for that info. Thanks.-- New SQL Server DBA
You didn't install SQL 2000 SP2. You installed SQL 2000 RTM (v194). The
installation program at the point SQL 2000 RTM was released didn't know
about Win2K3 and is giving you the error.
Install SP3a on the server and you should be ready to go.
David Gugick
Imceda Software
www.imceda.com
I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not support on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New SQL Server DBANewbie wrote:
> Hi,
> I installed sql server 2000 sp2 standard edition on Windows 2003, when
> installing, it said "This version is not support on this os", but I
> was told to continue installing the software and that I could install
> the latest security patches to bring it up to date. Will that work?
> Do I need to do anything else? SQL Server 2000 is up and running on
> the box. When running the statement " select @.@.version" it informed
> me that I was at 8.00.194 patch level. How can I tell if SQL Server
> 2000 is 32 or 64 bit? I was trying to download the lasted patch and
> it asked for that info. Thanks.-- New SQL Server DBA
You didn't install SQL 2000 SP2. You installed SQL 2000 RTM (v194). The
installation program at the point SQL 2000 RTM was released didn't know
about Win2K3 and is giving you the error.
Install SP3a on the server and you should be ready to go.
David Gugick
Imceda Software
www.imceda.com
New Installation of Sql Server 2000
Hello Guru's, I need your help!
I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not supported on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New to SQL ServerUnless you paid over $20,000 for SQL Server, it is probably 32 bit. I think the 64 bit version of SQL server states in @.@.version that it is 64 bit, so if you do not see anything, you very likely have 32 bit.
You need SQL Server SP3 to run on Windows 2003 with no problems. Just download the patch, run it, and you should be all set.|||Thank You Very Much!!! :)
I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not supported on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New to SQL ServerUnless you paid over $20,000 for SQL Server, it is probably 32 bit. I think the 64 bit version of SQL server states in @.@.version that it is 64 bit, so if you do not see anything, you very likely have 32 bit.
You need SQL Server SP3 to run on Windows 2003 with no problems. Just download the patch, run it, and you should be all set.|||Thank You Very Much!!! :)
New Installation of SQL Server 2000
Hi,
I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not support on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New SQL Server DBANewbie wrote:
> Hi,
> I installed sql server 2000 sp2 standard edition on Windows 2003, when
> installing, it said "This version is not support on this os", but I
> was told to continue installing the software and that I could install
> the latest security patches to bring it up to date. Will that work?
> Do I need to do anything else? SQL Server 2000 is up and running on
> the box. When running the statement " select @.@.version" it informed
> me that I was at 8.00.194 patch level. How can I tell if SQL Server
> 2000 is 32 or 64 bit? I was trying to download the lasted patch and
> it asked for that info. Thanks.-- New SQL Server DBA
You didn't install SQL 2000 SP2. You installed SQL 2000 RTM (v194). The
installation program at the point SQL 2000 RTM was released didn't know
about Win2K3 and is giving you the error.
Install SP3a on the server and you should be ready to go.
David Gugick
Imceda Software
www.imceda.com
I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not support on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New SQL Server DBANewbie wrote:
> Hi,
> I installed sql server 2000 sp2 standard edition on Windows 2003, when
> installing, it said "This version is not support on this os", but I
> was told to continue installing the software and that I could install
> the latest security patches to bring it up to date. Will that work?
> Do I need to do anything else? SQL Server 2000 is up and running on
> the box. When running the statement " select @.@.version" it informed
> me that I was at 8.00.194 patch level. How can I tell if SQL Server
> 2000 is 32 or 64 bit? I was trying to download the lasted patch and
> it asked for that info. Thanks.-- New SQL Server DBA
You didn't install SQL 2000 SP2. You installed SQL 2000 RTM (v194). The
installation program at the point SQL 2000 RTM was released didn't know
about Win2K3 and is giving you the error.
Install SP3a on the server and you should be ready to go.
David Gugick
Imceda Software
www.imceda.com
New Install - Log Says Eval Expired, But It's Not an Eval
I have installed the standard edition of SQL2005 w Reporting Services on my XP Pro desktop. SQL2005 works fine, but SSRS will not. In the log, I see the message that the evaluation copy has expired--but the install is not an eval copy. I have tried uninstalling SQL Server a couple of times, but no change. Anyone know why this is happening?
What is the errors you are getting with trying to work with RS?
The message you see in the log file does not apply if you are installing any version except the Evaluation version.
|||Another log displays the message "object not set to instance of an object".Monday, February 20, 2012
New data source connection failure
Hi,
Windows 2003 Server Std. Edition - SQL Server 200 Std. Edition
I'm able to create a new data source in the ODBC panel on the SQL
server which points to a db on the same SQL server but not creating
that same new data source in the SQL Server Enterprise Manager or
Analysis Manager. I tried creating a new cube, a new DTS and so on but
I won't get past the new data source failure.
Error: [DBNETLIB][ConnectionOpen(Connect()).] SQL Server does not
exist or access is denied.
I tried using local admin account, sa account which both belong to the
sysadmin serve role.
Thank you.
Steve"Steve" <steve@.500mg.be> wrote in message
news:6b781b0f.0410300430.775b6306@.posting.google.com...
> Windows 2003 Server Std. Edition - SQL Server 200 Std. Edition
> I'm able to create a new data source in the ODBC panel on the SQL
> server which points to a db on the same SQL server but not creating
> that same new data source in the SQL Server Enterprise Manager or
> Analysis Manager. I tried creating a new cube, a new DTS and so on but
> I won't get past the new data source failure.
> Error: [DBNETLIB][ConnectionOpen(Connect()).] SQL Server does not
> exist or access is denied.
> I tried using local admin account, sa account which both belong to the
> sysadmin serve role.
It sounds like your SQL Server 2000 is running in "windows only"
authentication mode, which means the 'sa' account would not be recognized.
Try either a windows account (preferred technique) local admin should work
if you have not changed the basic security install, or change the
authentication mode to "sql server and windows", stop and restart SQL
Server.
Steve
Windows 2003 Server Std. Edition - SQL Server 200 Std. Edition
I'm able to create a new data source in the ODBC panel on the SQL
server which points to a db on the same SQL server but not creating
that same new data source in the SQL Server Enterprise Manager or
Analysis Manager. I tried creating a new cube, a new DTS and so on but
I won't get past the new data source failure.
Error: [DBNETLIB][ConnectionOpen(Connect()).] SQL Server does not
exist or access is denied.
I tried using local admin account, sa account which both belong to the
sysadmin serve role.
Thank you.
Steve"Steve" <steve@.500mg.be> wrote in message
news:6b781b0f.0410300430.775b6306@.posting.google.com...
> Windows 2003 Server Std. Edition - SQL Server 200 Std. Edition
> I'm able to create a new data source in the ODBC panel on the SQL
> server which points to a db on the same SQL server but not creating
> that same new data source in the SQL Server Enterprise Manager or
> Analysis Manager. I tried creating a new cube, a new DTS and so on but
> I won't get past the new data source failure.
> Error: [DBNETLIB][ConnectionOpen(Connect()).] SQL Server does not
> exist or access is denied.
> I tried using local admin account, sa account which both belong to the
> sysadmin serve role.
It sounds like your SQL Server 2000 is running in "windows only"
authentication mode, which means the 'sa' account would not be recognized.
Try either a windows account (preferred technique) local admin should work
if you have not changed the basic security install, or change the
authentication mode to "sql server and windows", stop and restart SQL
Server.
Steve
New Data Connection Problem in VS.NET 2005
I have all of the prerequisites installed:
- SQL Server 2005 Compact Edition
- Visual Studio 2005 SP1 (Standard Edition)
- SQL Server Management Studio Express SP2
When trying to add a new Compact Edition SQL DB data connection from within Visual Studio ("SQL Mobile", "SQL Compact...", etc.), nothing is available for it. I have Access, ODBC, SQL Server, SQL DB File, Oracle, and Other. Even when selecting other, there are no Compact/Mobile types available.
Please Help...I've been going crazy trying to get this option.
Thank you
Anybody? Anybody at all?|||I guess you'll have to settle for me.
I too have had problems installing the lastest SP of Visual Studio (VS) which includes the latest SQL Server Compact Edition (SQLCe) binaries. The problem is that you must make sure that if you've installed any CTPs they must be scrubbed off first. So, assuming you've done that or never installed the beta CTPs (which were used to implement SQL Server Everywhere Edition), you need to first install VS 2005 SP1 from http://msdn2.microsoft.com/en-us/vstudio/bb265237.aspx. Next, you might also need to install the SQLCe MSI to get the bit installed in the GAC. These bits can be found here http://www.microsoft.com/sql/editions/compact/downloads.mspx. As shown in my EBook "Hitchhiker's Guide to SQL Server 2005 Compact Edition", you can also download the SDK but you should now see the SQL Server Compact Edition as one of the choices when creating a Data Connection.
hth
|||APipeDreamI am having the same problem - did you get anywhere with it ?
|||
No, that's the order I used already, and I don't have any CTPs installed. I also have the SDK installed.
So am I.
I uninstalled/re-installed all componenets still no luck.
I found a solution:
I re-installed the following off the original install DVD - sqlmobile30devtoolsenu.msi, then installed the update SSCE31VSTools-ENU.exe which can be downloaded from Microsoft.
|||Gotta create a DDEX Provider?
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1477140&SiteID=1
|||I found a solution:
I re-installed the following off the original install DVD - sqlmobile30devtoolsenu.msi, then installed the update SSCE31VSTools-ENU.exe which can be downloaded from Microsoft.
|||Thanks This worked:
I re-installed the following off the original install DVD - sqlmobile30devtoolsenu.msi, then installed the update SSCE31VSTools-ENU.exe which can be downloaded from Microsoft.
New Data Connection Problem in VS.NET 2005
I have all of the prerequisites installed:
- SQL Server 2005 Compact Edition
- Visual Studio 2005 SP1 (Standard Edition)
- SQL Server Management Studio Express SP2
When trying to add a new Compact Edition SQL DB data connection from within Visual Studio ("SQL Mobile", "SQL Compact...", etc.), nothing is available for it. I have Access, ODBC, SQL Server, SQL DB File, Oracle, and Other. Even when selecting other, there are no Compact/Mobile types available.
Please Help...I've been going crazy trying to get this option.
Thank you
Anybody? Anybody at all?|||I guess you'll have to settle for me.
I too have had problems installing the lastest SP of Visual Studio (VS) which includes the latest SQL Server Compact Edition (SQLCe) binaries. The problem is that you must make sure that if you've installed any CTPs they must be scrubbed off first. So, assuming you've done that or never installed the beta CTPs (which were used to implement SQL Server Everywhere Edition), you need to first install VS 2005 SP1 from http://msdn2.microsoft.com/en-us/vstudio/bb265237.aspx. Next, you might also need to install the SQLCe MSI to get the bit installed in the GAC. These bits can be found here http://www.microsoft.com/sql/editions/compact/downloads.mspx. As shown in my EBook "Hitchhiker's Guide to SQL Server 2005 Compact Edition", you can also download the SDK but you should now see the SQL Server Compact Edition as one of the choices when creating a Data Connection.
hth
|||APipeDreamI am having the same problem - did you get anywhere with it ?
|||
No, that's the order I used already, and I don't have any CTPs installed. I also have the SDK installed.
So am I.
I uninstalled/re-installed all componenets still no luck.
I found a solution:
I re-installed the following off the original install DVD - sqlmobile30devtoolsenu.msi, then installed the update SSCE31VSTools-ENU.exe which can be downloaded from Microsoft.
|||Gotta create a DDEX Provider?
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1477140&SiteID=1
|||I found a solution:
I re-installed the following off the original install DVD - sqlmobile30devtoolsenu.msi, then installed the update SSCE31VSTools-ENU.exe which can be downloaded from Microsoft.
|||Thanks This worked:
I re-installed the following off the original install DVD - sqlmobile30devtoolsenu.msi, then installed the update SSCE31VSTools-ENU.exe which can be downloaded from Microsoft.
Subscribe to:
Posts (Atom)