table hosed: windows

Showing posts with label windows. Show all posts

Wednesday, March 28, 2012

Is There a Quick Way to Get a Total Match Count (estimate is OK) of a SQL FullText Query?

Hi,
I am using the June CTP release of SQL Server 2005 on Windows Sever 2003.
Is there a quick way to get a total natch count (estimate is OK)
of a SQL FullText query? I am working with about 10 million r
ows of simple character data.
The following SQL simply returns too slow due to disk IO on the disk
with the relational table when the number of hits is large (say half
millions)
select count(*) from CONTAINSTABLE(MyTableName, FTColumnName, '
"QueryPhrase" ')
Thanks,
Wenbin Zhang
Wenbin Zhang,
Since you're using SQL Server 2005, the best way to get this type of
statistical info is from the word list in the FT Catalog via the CIDump.exe
utility (see related thread subject: cidump documentation?) and import the
output back into a SQL Server table.
If you need to use a T-SQL to determine the word count of a SQL FTS query,
instead of just using a count(*), it is faster to use a stored proc, for
example:
create proc FTS_t1 (@.SearchWord varchar(7800))
as
select c1 from t1 where contains(c2, @.SearchWord)
go
create proc FTSCount_t1 (@.SearchWord varchar(7800))
as
set nocount on
create table #FTPrimaryKey(t1_UPK int)
insert into #FTPrimaryKey exec FTS_t1 @.SearchWord
select count(*) from #FTPrimaryKey
set nocount off
go
-- example of use:
exec FTSCount_t1 '"computer"'
Hope that helps!
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Wenbin Zhang" <zhang_wenbin@.hotmail.com> wrote in message
news:%23arzmzVoFHA.3696@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I am using the June CTP release of SQL Server 2005 on Windows Sever 2003.
> Is there a quick way to get a total natch count (estimate is OK)
> of a SQL FullText query? I am working with about 10 million r
> ows of simple character data.
> The following SQL simply returns too slow due to disk IO on the disk
> with the relational table when the number of hits is large (say half
> millions)
> select count(*) from CONTAINSTABLE(MyTableName, FTColumnName, '
> "QueryPhrase" ')
> Thanks,
> Wenbin Zhang
>

Monday, March 26, 2012

Is there a Cluster command line I can run which will stop my "SQL Agent Service"?

Gurus,
Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
Cluster command line I can run which will stop my "SQL Agent Service"?
Spin
Hi
How about NET STOP?
John
"Spin" <Spin@.invalid.com> wrote in message
news:656t5iF2eq3dbU1@.mid.individual.net...
> Gurus,
> Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
> Cluster command line I can run which will stop my "SQL Agent Service"?
> --
> Spin
>
|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:e2yjJedkIHA.5368@.TK2MSFTNGP04.phx.gbl...
> Hi
> How about NET STOP?
No can do John. NET STOP stops the service outside of the Cluster
environment. What will happen is the Windows Cluster service will detect
the service down then automatically restart it! What I need is a Cluster
service command line tool which gracefully stops the service per "knowledge"
if you will, of the Cluster service.
|||For the default instance:
cluster.exe /cluster:<cluster name> resource "SQL Server Agent" /offline
For a named instance (assuming that the instance name is SQL2):
cluster.exe /cluster:<cluster name> resource "SQL Server Agent (SQL2)"
/offline
Linchi
"Spin" wrote:

> Gurus,
> Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
> Cluster command line I can run which will stop my "SQL Agent Service"?
> --
> Spin
>
>
|||Thanks! I'll shout back on Monday if this works...
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:C9EF5727-A88B-4261-B445-266B2C45990C@.microsoft.com...[vbcol=seagreen]
> For the default instance:
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent" /offline
> For a named instance (assuming that the instance name is SQL2):
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent (SQL2)"
> /offline
> Linchi
> "Spin" wrote:
|||"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:C9EF5727-A88B-4261-B445-266B2C45990C@.microsoft.com...
> For the default instance:
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent" /offline
> For a named instance (assuming that the instance name is SQL2):
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent (SQL2)"
> /offline
> Linchi
Worked!!!!! You are a Gentleman and a Scholar!
Spin

Is there a Cluster command line I can run which will stop my "SQL Agent Service"?

Gurus,
Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
Cluster command line I can run which will stop my "SQL Agent Service"?
--
SpinHi
How about NET STOP?
John
"Spin" <Spin@.invalid.com> wrote in message
news:656t5iF2eq3dbU1@.mid.individual.net...
> Gurus,
> Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
> Cluster command line I can run which will stop my "SQL Agent Service"?
> --
> Spin
>|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:e2yjJedkIHA.5368@.TK2MSFTNGP04.phx.gbl...
> Hi
> How about NET STOP?
No can do John. NET STOP stops the service outside of the Cluster
environment. What will happen is the Windows Cluster service will detect
the service down then automatically restart it! What I need is a Cluster
service command line tool which gracefully stops the service per "knowledge"
if you will, of the Cluster service.|||For the default instance:
cluster.exe /cluster:<cluster name> resource "SQL Server Agent" /offline
For a named instance (assuming that the instance name is SQL2):
cluster.exe /cluster:<cluster name> resource "SQL Server Agent (SQL2)"
/offline
Linchi
"Spin" wrote:
> Gurus,
> Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
> Cluster command line I can run which will stop my "SQL Agent Service"?
> --
> Spin
>
>|||Thanks! I'll shout back on Monday if this works...
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:C9EF5727-A88B-4261-B445-266B2C45990C@.microsoft.com...
> For the default instance:
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent" /offline
> For a named instance (assuming that the instance name is SQL2):
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent (SQL2)"
> /offline
> Linchi
> "Spin" wrote:
>> Gurus,
>> Running SQL Server 2005 SP2 on a Windows Server 2003 Cluster. Is there a
>> Cluster command line I can run which will stop my "SQL Agent Service"?
>> --
>> Spin
>>|||"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:C9EF5727-A88B-4261-B445-266B2C45990C@.microsoft.com...
> For the default instance:
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent" /offline
> For a named instance (assuming that the instance name is SQL2):
> cluster.exe /cluster:<cluster name> resource "SQL Server Agent (SQL2)"
> /offline
> Linchi
Worked!!!!! You are a Gentleman and a Scholar!
--
Spin

Wednesday, March 21, 2012

Is the Certificate based authentication the only way ?

1.On an virtual server two virtual machines of Windows 2003+sql server 2005 developer edition named VM1 and VM2

2.The VMs are not on a domain.

3.endpoint uses windows authentication

I get the following error

Msg 1418, Level 16, State 1, Line 1
The server network address "TCP://x.x.x.x:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.

and the log file contains the following

07/26/2007 19:21:22,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. An OS call failed: (8009030e) 0x8009030e(No credentials are available in the security package). State 65.'. [CLIENT: x.x.x.x]
07/26/2007 19:21:19,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. An OS call failed: (8009030e) 0x8009030e(No credentials are available in the security package). State 65.'. [CLIENT: x.x.x.x]
07/26/2007 19:21:17,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. An OS call failed: (8009030e) 0x8009030e(No credentials are available in the security package). State 65.'. [CLIENT: x.x.x.x]
07/26/2007 19:21:14,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. An OS call failed: (8009030e) 0x8009030e(No credentials are available in the security package). State 65.'. [CLIENT: x.x.x.x]
07/26/2007 19:21:12,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. An OS call failed: (8009030e) 0x8009030e(No credentials are available in the security package). State 65.'. [CLIENT: x.x.x.x]
07/26/2007 19:21:10,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. An OS call failed: (8009030e) 0x8009030e(No credentials are available in the security package). State 65.'. [CLIENT: x.x.x.x]
07/26/2007 19:21:09,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. An OS call failed: (8009030e) 0x8009030e(No credentials are available in the security package). State 65.'. [CLIENT: x.x.x.x]
07/26/2007 19:21:08,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. An OS call failed: (8009030e) 0x8009030e(No credentials are available in the security package). State 65.'. [CLIENT: x.x.x.x]
07/26/2007 19:21:06,spid25s,Unknown,Database mirroring connection error 5 'Connection handshake failed. An OS call failed: (8009030e) 0x8009030e(No credentials are available in the security package). State 65.' for 'TCP://x.x.x.x:5022'.
07/26/2007 19:21:06,spid25s,Unknown,Error: 1474<c/> Severity: 16<c/> State: 1.
07/26/2007 19:21:06,Logon,Unknown,Database Mirroring login attempt failed with error: 'Connection handshake failed. An OS call failed: (8009030e) 0x8009030e(No credentials are available in the security package). State 65.'. [CLIENT: x.x.x.x]

Is there anyway i can do mirroring without certificates,

guys any pointers?

i think the partners namely principal and mirror server shud have either standard or enterprise edition to configure mirroring..........but the error seems to be different........just check the ports using the command netstat -ano whether the port you specify is used somewhere........also try to give the fully qualified server name.........

|||

1. Developer edition supports

2.The specified port is not being used

3.Since the macine is not on a domain i cannot give the fully qualified path alternatively i have used ip.

|||

I don't know if this will make you feel better or not but let me tell you that I as well was looking into setting up mirroring with all sorts of tricks not to use certificate authentication.

But trust me, for 2 computers not in the same domain this is the best way. It saves you a lot of trouble with permissions and all sorts of *** errors.

Do it using transact sql commands following microsoft example and it will work! I got mine up and running ever since.

|||

I had the same error even after bringing the servers under a single domain.

The following is the change I made

Changed the Authentication type from Kerbrose to NTLM.

It all works fine when servers are under same domain.

Need to check when the servers are not under a Domain.

|||partners need to be either std or enterprise edition...refer,
http://msdn2.microsoft.com/en-us/library/ms366349.aspx

Monday, March 19, 2012

is sqlserver 2000 compatible with windows 2003 ?

Hi !

when installing sqlserver 2000 on a Windows 2003 server it explicitly
tells "server not compatible with Windows 2003" during install, but it
can carry on.
After we applied serfice pack 3a then the db server seems to run
normally, but does it risk to behave randomly afterwards ?
Is sqlserver 2000 standard edition compatible with Windows 2003 server
?
Or does it exist a specific sqlserver edition for Win2003 ?

thanks !
Patrice"Patrox" <patrice .castet @.in- fusio. NOOO.SPAAAAM.com> wrote in message
news:a8c9g0dk9utjs0iraab973ag5p1obpuunm@.4ax.com...
> Hi !
> when installing sqlserver 2000 on a Windows 2003 server it explicitly
> tells "server not compatible with Windows 2003" during install, but it
> can carry on.
> After we applied serfice pack 3a then the db server seems to run
> normally, but does it risk to behave randomly afterwards ?
> Is sqlserver 2000 standard edition compatible with Windows 2003 server
> ?
> Or does it exist a specific sqlserver edition for Win2003 ?
> thanks !
> Patrice
You may find these articles interesting.
http://www.winnetmag.com/Article/Ar...0428/40428.html
http://support.microsoft.com/defaul...kb;en-us;329329

The important point is [from MSKB article]:
"To work around this behavior, install SQL Server 2000 SP3 or later
immediately after you install SQL Server 2000."

HTH,

Rowland.|||On Mon, 26 Jul 2004 09:24:10 +0200, Patrox <patrice .castet @.in-
fusio. NOOO.SPAAAAM.com> wrote:

>Hi !
>when installing sqlserver 2000 on a Windows 2003 server it explicitly
>tells "server not compatible with Windows 2003" during install, but it
>can carry on.
>After we applied serfice pack 3a then the db server seems to run
>normally, but does it risk to behave randomly afterwards ?
>Is sqlserver 2000 standard edition compatible with Windows 2003 server
>?
>Or does it exist a specific sqlserver edition for Win2003 ?
>thanks !
>Patrice
I have SQL 2k Enterprise running on Windows 2003. I've not had any
trouble with it, and I assume the standard version would work as well.
I don't remember getting an error message when installing, though I
may just not remember it.

Is SQL Server Windows Authentication mode more secure than SQL Server "Mixed Mode" mode?

Gurus,
Is SQL Server Windows Authentication mode more secure than SQL Server "Mixed
Mode" mode? Someone told me it was b/c SA is disabled and there Windows
Authentication mode provides a good AD mapping to groups which is good for
administration.
--
SpinI guess there is some validity in that line of reasoning. But if it really
comes to that difference, I'd argue that you may have a bigger problem. Point
is that you can make the mixed mode secure (e.g. with strong password and so
on).
Linchi
"Spin" wrote:
> Gurus,
> Is SQL Server Windows Authentication mode more secure than SQL Server "Mixed
> Mode" mode? Someone told me it was b/c SA is disabled and there Windows
> Authentication mode provides a good AD mapping to groups which is good for
> administration.
> --
> Spin
>

Is SQL Server Windows Authentication mode more secure than SQL Server "Mixed Mode" mode?

Gurus,
Is SQL Server Windows Authentication mode more secure than SQL Server "Mixed
Mode" mode? Someone told me it was b/c SA is disabled and there Windows
Authentication mode provides a good AD mapping to groups which is good for
administration.
Spin
I guess there is some validity in that line of reasoning. But if it really
comes to that difference, I'd argue that you may have a bigger problem. Point
is that you can make the mixed mode secure (e.g. with strong password and so
on).
Linchi
"Spin" wrote:

> Gurus,
> Is SQL Server Windows Authentication mode more secure than SQL Server "Mixed
> Mode" mode? Someone told me it was b/c SA is disabled and there Windows
> Authentication mode provides a good AD mapping to groups which is good for
> administration.
> --
> Spin
>

Monday, March 12, 2012

Is SQL Server Service Manager still existing on SQL Express Edition?

Hi there. I am new to the SQL Express. I just finished installing the SQL Express 2005 with Advanced Services on a Windows XP SP2 computer. The first thing I noticed was the service manager (used to be on the taskbar) was being removed on the Express Edition. How do I get this feature back if it's even possible? I know you can find out the server status from the Configuration Manager but it's handy if the status is showned on the taskbar after logging in.

Any help will be greatly appreciated. Thank you.

There is no Service Manager in any SKU of SQL Server 2005. There are some folks out there that have written their own however.

is sql server 2005 a standalone install? Or do you have to install windows server

I have never installed sql server before and I didnt know if I just take the sql server 2005 standard edition media and boot off it and do a fresh install that way or do I have to install Windows server

SQL Server is "just" a database*. You need an underlying operating system in place before you attempt to install it. For SQL Server 2005, supported operating systems are Windows 2000, Windows XP, and Windows Server 2003. Not all versions of SQL Server 2005 are supported on all these operating systems, but I believe the standard edition of SQL is.

Paul

*Well, a database and tools and report server and... But it's not an operating system.

|||thanks, that exacty what i needed to hear.

Friday, March 9, 2012

is sql 7.0 scheduled to be retired

In e-Week (Dec 15, 2003 pg 8) an article mentioned that Windows 98, sql
server 7.0 and a number of versions of office 2000 are scheduled to be
retired by Dec 23 as part of the agreement with Sun over the Java lawsuit.
Can anyone point me to a press release or list of products that are
scheduled to be retired as part of this agreement?> In e-Week (Dec 15, 2003 pg 8) an article mentioned that Windows 98, sql
> server 7.0 and a number of versions of office 2000 are scheduled to be
> retired by Dec 23 as part of the agreement with Sun over the Java lawsuit.
I believe there are certain products that will no longer be available, e.g.
to download from the MSDN Subscriber Downloads site. But that does not mean
the product is "retired" depending on how you define "retired"; it will
still follow its product life cycle. For example, according to
http://support.microsoft.com/default.aspx?scid=fh;[ln];LifeSrvr
SQL Server 7.0 will "die," in different senses, on 12/31/2005, and
12/31/2007.
Here is a snippet from an announcement to MSDN subscribers, which highlights
the other products which will no longer be available directly:
> Due to a settlement agreement reached in January 2001, the following
> products are being phased out and will no longer available to customers
> through MSDN Subscriber Downloads or other channels at Microsoft. These
> products will be removed from MSDN Subscriber Downloads as of December
15th,
> 2003.
> Office XP Developer
> Visio 2000
> BackOffice Server 2000
> Office 2000 Developer
> Office 2000 Tools
> Office 2000 Multilingual
> Office 2000 Premium SR-1
> Office 2000 Service Pack 2
> Outlook 2000
> Project 2000
> SQL Server 7
> SQL Server 7 Service Pack 3
> Embedded Visual Tools 3.0
> Visual Studio 6 MSDE
> IE 5.5
> MapPoint 2002
> Visual Studio 6.0 SP3 and SP5
> Windows 98
> Windows 98 Y2K
> Windows 98 Resource Kit
> Windows 98 SP1 (all win98 except SE)
> Windows NT 4.0
> ISA Server 2000
> Visual Basic for (Alpha Systems)
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/

Is SQL 2005 memory limitation <= OS memory limitation?

If I install SQL 2005 Standard on Windows 2003 Standard, is SQL limited to 4 gigs of physical RAM?

I'm planning a new system that will run SQL 2005 Standard edition on a Windows 2003 Standard platform. The spec calls for 8 GB of RAM. My experience would lead me to suspect I need to install Windows 2003 Enterprise to take advantage of all the installed memory.

You can′t get around the OS limitation.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||vielen dank. Seems obvious, but needed to ask.

Is SQL 2005 failover cluster supported on Windows 2008 clusters?

Hi,
I'm trying to install SQL 2005 on a Windows 2008 cluster. I just want
to know if this is supported, and if there's any special procedures
required for the same.
Thanks
M Rosenblum
Since Windows 2008 is not a released product, there is no "supported"
configuration. If there is any information, it will likely be in the
Windows 2008 readme file.
Feel free to experiment and post your results.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Usentr" <usentr@.gmail.com> wrote in message
news:1194464048.828727.215070@.e9g2000prf.googlegro ups.com...
> Hi,
> I'm trying to install SQL 2005 on a Windows 2008 cluster. I just want
> to know if this is supported, and if there's any special procedures
> required for the same.
> Thanks
> M Rosenblum
>

Is SQL 2000 clustering cr*p??

Howdy,

I have had questions from management about whether SQL 2000 clustering on windows 2000 is any good.

We are looking at spending *quite* a bit of money to implement it, but I want a "from the trenches" opinion of what its like , from the people that actually use it & look after it.

e.g.

DOES IT WORK LIKE IT SHOULD????
Is it reliable?
Is it resource hungry?
Can I trust it to do what its supposed to do?

All repsonses very welcome. No response too small.

Thanks for your help.

Cheers,

SG.Originally posted by sqlguy7777
All repsonses very welcome. No response too small.

SELECT LEN('What are you going to use it for?')|||I support a SQL 2000 cluster, and I'm quite happy with it.

Before spending a bunch of money on a cluster, the first question to ask yourself is what type of disasters are you expecting it to protect you from?

Clustering is primarily protection from hardware and operating system failure. And with RAID disks, you're probably already protected from most disk failures. Depending on your server, you may also be protected from single failures of netowrk cards and processors (though with some performance degredation until you resolve the problem)

Opinions on the stability of Windows are all over the map. You're milage may vary.

Whether or not clustering will protect your applicaiton is a murkier question. Since there will only be one copy of your databases, you will *not* be protected from DB corruption unless you implement further protections beyond basic clustering. Whether or not and subsidary services you write will be protected depends on their implementation.

If you have any specific questions, shoot.|||I have been watching 3 SQL 2000 clusters for around 2 years, now. Only advice I have for you is to put the quorum on its own physical device. I have had one of my clusters fail over when the transaction log got hit hard one day. After a day on the phone with MS, they pointed me to one sentence in one article in one section of technet, and promptly washed their hands. I am not sure if you can move a quorum after it has been created.

Oh, and one other thing. may you never face a quorum corruption problem. Quorum disks can still go bad.|||Originally posted by MCrowley
I have been watching 3 SQL 2000 clusters for around 2 years, now. Only advice I have for you is to put the quorum on its own physical device. I have had one of my clusters fail over when the transaction log got hit hard one day. After a day on the phone with MS, they pointed me to one sentence in one article in one section of technet, and promptly washed their hands. I am not sure if you can move a quorum after it has been created.

Oh, and one other thing. may you never face a quorum corruption problem. Quorum disks can still go bad.

One thing they don't tell you (at least not that I could ever find) is to be sure to turn off write caching on your quorum drive. We had many uncommanded failovers until we did this. Although I can't claim to know for a fact that this is the cause, it seems reasonable that the node owning the quorum writes some data to it, then signals the other node via the heartbeat network that the other node can acquire the quorum. Only problem is, the controller hasn't really put the data on disk yet, so the other node either can't read the quorum quick enough (the controller won't let it have it) or it doesn't see what it's expecting to see. Either way it then forces a failover. Whether or not this scenario is is what is really going on or not, as soon as we turned off write caching on the quorum drive, our uncommanded failovers ceased.|||Howdy,

Thanks everyone so far for your thoughts.

Brett - its mainly for supporting multiple databases ( direct access from desktop ) and some mission critical apps ( access via web system ) .

We wanted to split the cluster ( and mirror quorum drive using SAN ) across 2 computer rooms such that should one computer room die ( as has happened in the past ) the cluster will keep running.

What physical architecture do you run and what problems ( if any ) have you had with the cluster and why? Is it worth the money?

I'm interested if we are making a rod for our own backs, but we need resiliance for our systems.
Log shipping is out of the question by the way..

Thanks,

SG.|||Keep in mind there is only ONE copy of each DB. You won't get a copy of each DB in each computer room. The databases go on shared DASD, which is pretty much going to be in one room or the other. In our case, our DASD (a SAN-attached IBM FAStT 500 storage controller) has redundant power supplies on separate power circuits, you might be able to power your own DASD similarly from each room. But clustering does not give you two mirrored copies of your DB, a la one on each node.

Originally posted by sqlguy7777
Howdy,

Thanks everyone so far for your thoughts.

Brett - its mainly for supporting multiple databases ( direct access from desktop ) and some mission critical apps ( access via web system ) .

We wanted to split the cluster ( and mirror quorum drive using SAN ) across 2 computer rooms such that should one computer room die ( as has happened in the past ) the cluster will keep running.

What physical architecture do you run and what problems ( if any ) have you had with the cluster and why? Is it worth the money?

I'm interested if we are making a rod for our own backs, but we need resiliance for our systems.
Log shipping is out of the question by the way..

Thanks,

SG.|||I'd keep a warm standby...how long can you be out...or can't you?

Are you dealing with trades?|||Howdy,

We are running 24x7 apps that need to be up.

I thought ( possibly naively ) that we could have a server cluster but also pysically split the SAN so half of it is in one computer room , the other half in the other computer room, and each part of the SAN was an exact mirror of the other ( using hardware mirroring ).

Then, if we lost one computer room, the cluster would just flick over to the part of the SAN and a server in the other room.

Sounds simple in theory.....is it possible??

Thanks for oyur help so far

SG.|||The trick is going to be finding a disk controller that will allow you to do this. You'll need a pair of such controllers, one in each room, that will either communicate with each other in lock-step, or share managing a set of RAID arrays that are build in RAID 10 with one set in one room and the mirror pair in the other.

Some hardware genius is going to have to locate that for you. I'm not sure it exists in the Wintel world, but it might.

What's the failure mode whereby you lose an entire computer room?

Originally posted by sqlguy7777
Howdy,

We are running 24x7 apps that need to be up.

I thought ( possibly naively ) that we could have a server cluster but also pysically split the SAN so half of it is in one computer room , the other half in the other computer room, and each part of the SAN was an exact mirror of the other ( using hardware mirroring ).

Then, if we lost one computer room, the cluster would just flick over to the part of the SAN and a server in the other room.

Sounds simple in theory.....is it possible??

Thanks for oyur help so far

SG.|||Howdy,

Well, we seem to push boundaries on most things so...*sigh*

Q. WHat is Failure Mode called whereby we lose entire computer room ?

A. rapidly locate nearest place that serves alcohol. Stay there AT LEAST 2 days or until they find you.Deny all knowledge...

I guess the concept is borne from the fact our computer room has COMPLETELY been taken off the air in the past.

For 3 hours.

Ouch......

Cheers,

SG.|||If you are making plans for losing a computer room you may as well make plans for losing the building... the extra cost involved probably wouldn't be very significant considering the value that it would add.

I work for a few banks and they all have offsite failover systems.|||Howdy

Sadly, no offsite capabilty ( hey, nuts I know but I'm just the hired help...) so we have to assume one computer room gets nailed and the other one will take over.....

Like I mentioned, as usual...pushing the boundaries......

Have you seen any SANs where we could use hardware mirroring to replicate all data ( including quorum ) ?

Cheers,

SG.|||I know the banks that I have worked for have hot-hot swap over so if one room is lost they don't lose anything, the applications don't even pause as far as the users are concerned,...

I have no idea how it is done though, I just write the code and let the network guys and the system admins take care of all that. ;)|||Howdy

Any chance of finding out how they do it please?

Cheers,

SG

Is SQL 2000 better than 7?

We are using SQL 7 and Forte application and Win NT. I
have migrated DB to SQL 2000 and new Windows 2000 server.
Our DB is big, 150 G. Testing on new 2000 server, I see
that many of our procedures are running slower. One
procedure is like not running. Taking all resources and
hanging. I can ont even see the exec plan. I have tried
set plan still not working. This particular procedure is
using multiple unions and one of them using self join.
I have other procedures they are not that compecated but
the are slow too. I am having hard time convincing my boss
that SQL 2000 is better than 7. We really don't see any.
On top of that some procedure are not working at all.
Please send me your expert opinion.Update statistics with FULLSCAN on all indexes. Also, using the Profiler,
check for lock escalation events. If you see a lot, then you may have to
tune some queries.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Aziz Karim" <anonymous@.discussions.microsoft.com> wrote in message
news:145d01c499b4$34e51d50$a301280a@.phx.gbl...
We are using SQL 7 and Forte application and Win NT. I
have migrated DB to SQL 2000 and new Windows 2000 server.
Our DB is big, 150 G. Testing on new 2000 server, I see
that many of our procedures are running slower. One
procedure is like not running. Taking all resources and
hanging. I can ont even see the exec plan. I have tried
set plan still not working. This particular procedure is
using multiple unions and one of them using self join.
I have other procedures they are not that compecated but
the are slow too. I am having hard time convincing my boss
that SQL 2000 is better than 7. We really don't see any.
On top of that some procedure are not working at all.
Please send me your expert opinion.|||Thank you for your reply.
Tom, I tried again now with FULLSCAN. Same thing. I don't
think I will be able to use Profiler. I can not see the
exec paln since this query never finish. It is using a
table with 186 mil rows. With SQL server 7 no problem.
>--Original Message--
>Update statistics with FULLSCAN on all indexes. Also,
using the Profiler,
>check for lock escalation events. If you see a lot, then
you may have to
>tune some queries.
>--
>Tom
>----
--
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Columnist, SQL Server Professional
>Toronto, ON Canada
>www.pinnaclepublishing.com/sql
>
>"Aziz Karim" <anonymous@.discussions.microsoft.com> wrote
in message
>news:145d01c499b4$34e51d50$a301280a@.phx.gbl...
>We are using SQL 7 and Forte application and Win NT. I
>have migrated DB to SQL 2000 and new Windows 2000 server.
>Our DB is big, 150 G. Testing on new 2000 server, I see
>that many of our procedures are running slower. One
>procedure is like not running. Taking all resources and
>hanging. I can ont even see the exec plan. I have tried
>set plan still not working. This particular procedure is
>using multiple unions and one of them using self join.
>I have other procedures they are not that compecated but
>the are slow too. I am having hard time convincing my boss
>that SQL 2000 is better than 7. We really don't see any.
>On top of that some procedure are not working at all.
>Please send me your expert opinion.
>.
>|||You can trace the lock escalation event, even if the statement does not
complete. Also, you can trace the SQL:BatchStarting event. That way, you
can see which statement is slow.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Aziz" <anonymous@.discussions.microsoft.com> wrote in message
news:18a701c499d3$e91e9020$a401280a@.phx.gbl...
Thank you for your reply.
Tom, I tried again now with FULLSCAN. Same thing. I don't
think I will be able to use Profiler. I can not see the
exec paln since this query never finish. It is using a
table with 186 mil rows. With SQL server 7 no problem.
>--Original Message--
>Update statistics with FULLSCAN on all indexes. Also,
using the Profiler,
>check for lock escalation events. If you see a lot, then
you may have to
>tune some queries.
>--
>Tom
>----
--
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Columnist, SQL Server Professional
>Toronto, ON Canada
>www.pinnaclepublishing.com/sql
>
>"Aziz Karim" <anonymous@.discussions.microsoft.com> wrote
in message
>news:145d01c499b4$34e51d50$a301280a@.phx.gbl...
>We are using SQL 7 and Forte application and Win NT. I
>have migrated DB to SQL 2000 and new Windows 2000 server.
>Our DB is big, 150 G. Testing on new 2000 server, I see
>that many of our procedures are running slower. One
>procedure is like not running. Taking all resources and
>hanging. I can ont even see the exec plan. I have tried
>set plan still not working. This particular procedure is
>using multiple unions and one of them using self join.
>I have other procedures they are not that compecated but
>the are slow too. I am having hard time convincing my boss
>that SQL 2000 is better than 7. We really don't see any.
>On top of that some procedure are not working at all.
>Please send me your expert opinion.
>.
>|||Tom Moreau wrote:
> You can trace the lock escalation event, even if the statement does
> not complete. Also, you can trace the SQL:BatchStarting event. That
> way, you can see which statement is slow.
>
You can also add SQL:StmtStarting and SP:StmtStarting to nail it down
even further. You can also run an estimated execution plan from Query
Analyzer and see if anything stands out without executing the query.
--
David G.|||I know which statement is slow. I think SQL 2000 using
different path than 7 for this query. Do I have to fine
tune all of these slow query?
I am trying to find a general solution to solve all
problems.
Aziz
>--Original Message--
>You can trace the lock escalation event, even if the
statement does not
>complete. Also, you can trace the SQL:BatchStarting
event. That way, you
>can see which statement is slow.
>--
>Tom
>----
--
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Columnist, SQL Server Professional
>Toronto, ON Canada
>www.pinnaclepublishing.com/sql
>
>"Aziz" <anonymous@.discussions.microsoft.com> wrote in
message
>news:18a701c499d3$e91e9020$a401280a@.phx.gbl...
>Thank you for your reply.
>Tom, I tried again now with FULLSCAN. Same thing. I don't
>think I will be able to use Profiler. I can not see the
>exec paln since this query never finish. It is using a
>table with 186 mil rows. With SQL server 7 no problem.
>>--Original Message--
>>Update statistics with FULLSCAN on all indexes. Also,
>using the Profiler,
>>check for lock escalation events. If you see a lot, then
>you may have to
>>tune some queries.
>>--
>>Tom
>>----
-
>--
>>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>>SQL Server MVP
>>Columnist, SQL Server Professional
>>Toronto, ON Canada
>>www.pinnaclepublishing.com/sql
>>
>>"Aziz Karim" <anonymous@.discussions.microsoft.com> wrote
>in message
>>news:145d01c499b4$34e51d50$a301280a@.phx.gbl...
>>We are using SQL 7 and Forte application and Win NT. I
>>have migrated DB to SQL 2000 and new Windows 2000 server.
>>Our DB is big, 150 G. Testing on new 2000 server, I see
>>that many of our procedures are running slower. One
>>procedure is like not running. Taking all resources and
>>hanging. I can ont even see the exec plan. I have tried
>>set plan still not working. This particular procedure is
>>using multiple unions and one of them using self join.
>>I have other procedures they are not that compecated but
>>the are slow too. I am having hard time convincing my
boss
>>that SQL 2000 is better than 7. We really don't see any.
>>On top of that some procedure are not working at all.
>>Please send me your expert opinion.
>>.
>.
>|||As with anything in software development, there is no magic bullet. It is
possible that the specific query is degraded when parallelism is used. If
so, try OPTION (MAXDOP 1).
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
.
<anonymous@.discussions.microsoft.com> wrote in message
news:187501c499ed$e5100df0$a301280a@.phx.gbl...
I know which statement is slow. I think SQL 2000 using
different path than 7 for this query. Do I have to fine
tune all of these slow query?
I am trying to find a general solution to solve all
problems.
Aziz
>--Original Message--
>You can trace the lock escalation event, even if the
statement does not
>complete. Also, you can trace the SQL:BatchStarting
event. That way, you
>can see which statement is slow.
>--
>Tom
>----
--
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Columnist, SQL Server Professional
>Toronto, ON Canada
>www.pinnaclepublishing.com/sql
>
>"Aziz" <anonymous@.discussions.microsoft.com> wrote in
message
>news:18a701c499d3$e91e9020$a401280a@.phx.gbl...
>Thank you for your reply.
>Tom, I tried again now with FULLSCAN. Same thing. I don't
>think I will be able to use Profiler. I can not see the
>exec paln since this query never finish. It is using a
>table with 186 mil rows. With SQL server 7 no problem.
>>--Original Message--
>>Update statistics with FULLSCAN on all indexes. Also,
>using the Profiler,
>>check for lock escalation events. If you see a lot, then
>you may have to
>>tune some queries.
>>--
>>Tom
>>----
-
>--
>>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>>SQL Server MVP
>>Columnist, SQL Server Professional
>>Toronto, ON Canada
>>www.pinnaclepublishing.com/sql
>>
>>"Aziz Karim" <anonymous@.discussions.microsoft.com> wrote
>in message
>>news:145d01c499b4$34e51d50$a301280a@.phx.gbl...
>>We are using SQL 7 and Forte application and Win NT. I
>>have migrated DB to SQL 2000 and new Windows 2000 server.
>>Our DB is big, 150 G. Testing on new 2000 server, I see
>>that many of our procedures are running slower. One
>>procedure is like not running. Taking all resources and
>>hanging. I can ont even see the exec plan. I have tried
>>set plan still not working. This particular procedure is
>>using multiple unions and one of them using self join.
>>I have other procedures they are not that compecated but
>>the are slow too. I am having hard time convincing my
boss
>>that SQL 2000 is better than 7. We really don't see any.
>>On top of that some procedure are not working at all.
>>Please send me your expert opinion.
>>.
>.
>|||I appreciate your help Tom.
I used OPTION (MAXDOP1) but it is runnig for 30 min. In
SQl 7 takes only 8 min.
I see that my CPU is not that busy for this OPTION.
Also I found in MS website that sometimes this option may
not work. There is a bug.
>--Original Message--
>As with anything in software development, there is no
magic bullet. It is
>possible that the specific query is degraded when
parallelism is used. If
>so, try OPTION (MAXDOP 1).
>--
> Tom
>----
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Columnist, SQL Server Professional
>Toronto, ON Canada
>www.pinnaclepublishing.com
>..
><anonymous@.discussions.microsoft.com> wrote in message
>news:187501c499ed$e5100df0$a301280a@.phx.gbl...
>I know which statement is slow. I think SQL 2000 using
>different path than 7 for this query. Do I have to fine
>tune all of these slow query?
>I am trying to find a general solution to solve all
>problems.
>Aziz
>>--Original Message--
>>You can trace the lock escalation event, even if the
>statement does not
>>complete. Also, you can trace the SQL:BatchStarting
>event. That way, you
>>can see which statement is slow.
>>--
>>Tom
>>----
-
>--
>>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>>SQL Server MVP
>>Columnist, SQL Server Professional
>>Toronto, ON Canada
>>www.pinnaclepublishing.com/sql
>>
>>"Aziz" <anonymous@.discussions.microsoft.com> wrote in
>message
>>news:18a701c499d3$e91e9020$a401280a@.phx.gbl...
>>Thank you for your reply.
>>Tom, I tried again now with FULLSCAN. Same thing. I don't
>>think I will be able to use Profiler. I can not see the
>>exec paln since this query never finish. It is using a
>>table with 186 mil rows. With SQL server 7 no problem.
>>--Original Message--
>>Update statistics with FULLSCAN on all indexes. Also,
>>using the Profiler,
>>check for lock escalation events. If you see a lot,
then
>>you may have to
>>tune some queries.
>>--
>>Tom
>>---
-
>-
>>--
>>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>>SQL Server MVP
>>Columnist, SQL Server Professional
>>Toronto, ON Canada
>>www.pinnaclepublishing.com/sql
>>
>>"Aziz Karim" <anonymous@.discussions.microsoft.com> wrote
>>in message
>>news:145d01c499b4$34e51d50$a301280a@.phx.gbl...
>>We are using SQL 7 and Forte application and Win NT. I
>>have migrated DB to SQL 2000 and new Windows 2000
server.
>>Our DB is big, 150 G. Testing on new 2000 server, I see
>>that many of our procedures are running slower. One
>>procedure is like not running. Taking all resources and
>>hanging. I can ont even see the exec plan. I have tried
>>set plan still not working. This particular procedure is
>>using multiple unions and one of them using self join.
>>I have other procedures they are not that compecated but
>>the are slow too. I am having hard time convincing my
>boss
>>that SQL 2000 is better than 7. We really don't see any.
>>On top of that some procedure are not working at all.
>>Please send me your expert opinion.
>>.
>>
>>.
>.
>|||I have also tried SET FORCEPLAN ON
Not helping either.
>--Original Message--
>As with anything in software development, there is no
magic bullet. It is
>possible that the specific query is degraded when
parallelism is used. If
>so, try OPTION (MAXDOP 1).
>--
> Tom
>----
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Columnist, SQL Server Professional
>Toronto, ON Canada
>www.pinnaclepublishing.com
>..
><anonymous@.discussions.microsoft.com> wrote in message
>news:187501c499ed$e5100df0$a301280a@.phx.gbl...
>I know which statement is slow. I think SQL 2000 using
>different path than 7 for this query. Do I have to fine
>tune all of these slow query?
>I am trying to find a general solution to solve all
>problems.
>Aziz
>>--Original Message--
>>You can trace the lock escalation event, even if the
>statement does not
>>complete. Also, you can trace the SQL:BatchStarting
>event. That way, you
>>can see which statement is slow.
>>--
>>Tom
>>----
-
>--
>>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>>SQL Server MVP
>>Columnist, SQL Server Professional
>>Toronto, ON Canada
>>www.pinnaclepublishing.com/sql
>>
>>"Aziz" <anonymous@.discussions.microsoft.com> wrote in
>message
>>news:18a701c499d3$e91e9020$a401280a@.phx.gbl...
>>Thank you for your reply.
>>Tom, I tried again now with FULLSCAN. Same thing. I don't
>>think I will be able to use Profiler. I can not see the
>>exec paln since this query never finish. It is using a
>>table with 186 mil rows. With SQL server 7 no problem.
>>--Original Message--
>>Update statistics with FULLSCAN on all indexes. Also,
>>using the Profiler,
>>check for lock escalation events. If you see a lot,
then
>>you may have to
>>tune some queries.
>>--
>>Tom
>>---
-
>-
>>--
>>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>>SQL Server MVP
>>Columnist, SQL Server Professional
>>Toronto, ON Canada
>>www.pinnaclepublishing.com/sql
>>
>>"Aziz Karim" <anonymous@.discussions.microsoft.com> wrote
>>in message
>>news:145d01c499b4$34e51d50$a301280a@.phx.gbl...
>>We are using SQL 7 and Forte application and Win NT. I
>>have migrated DB to SQL 2000 and new Windows 2000
server.
>>Our DB is big, 150 G. Testing on new 2000 server, I see
>>that many of our procedures are running slower. One
>>procedure is like not running. Taking all resources and
>>hanging. I can ont even see the exec plan. I have tried
>>set plan still not working. This particular procedure is
>>using multiple unions and one of them using self join.
>>I have other procedures they are not that compecated but
>>the are slow too. I am having hard time convincing my
>boss
>>that SQL 2000 is better than 7. We really don't see any.
>>On top of that some procedure are not working at all.
>>Please send me your expert opinion.
>>.
>>
>>.
>.
>|||What does the plan tell you?
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
<anonymous@.discussions.microsoft.com> wrote in message
news:1f5c01c49a6e$70780390$a301280a@.phx.gbl...
I have also tried SET FORCEPLAN ON
Not helping either.
>--Original Message--
>As with anything in software development, there is no
magic bullet. It is
>possible that the specific query is degraded when
parallelism is used. If
>so, try OPTION (MAXDOP 1).
>--
> Tom
>----
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Columnist, SQL Server Professional
>Toronto, ON Canada
>www.pinnaclepublishing.com
>..
><anonymous@.discussions.microsoft.com> wrote in message
>news:187501c499ed$e5100df0$a301280a@.phx.gbl...
>I know which statement is slow. I think SQL 2000 using
>different path than 7 for this query. Do I have to fine
>tune all of these slow query?
>I am trying to find a general solution to solve all
>problems.
>Aziz
>>--Original Message--
>>You can trace the lock escalation event, even if the
>statement does not
>>complete. Also, you can trace the SQL:BatchStarting
>event. That way, you
>>can see which statement is slow.
>>--
>>Tom
>>----
-
>--
>>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>>SQL Server MVP
>>Columnist, SQL Server Professional
>>Toronto, ON Canada
>>www.pinnaclepublishing.com/sql
>>
>>"Aziz" <anonymous@.discussions.microsoft.com> wrote in
>message
>>news:18a701c499d3$e91e9020$a401280a@.phx.gbl...
>>Thank you for your reply.
>>Tom, I tried again now with FULLSCAN. Same thing. I don't
>>think I will be able to use Profiler. I can not see the
>>exec paln since this query never finish. It is using a
>>table with 186 mil rows. With SQL server 7 no problem.
>>--Original Message--
>>Update statistics with FULLSCAN on all indexes. Also,
>>using the Profiler,
>>check for lock escalation events. If you see a lot,
then
>>you may have to
>>tune some queries.
>>--
>>Tom
>>---
-
>-
>>--
>>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>>SQL Server MVP
>>Columnist, SQL Server Professional
>>Toronto, ON Canada
>>www.pinnaclepublishing.com/sql
>>
>>"Aziz Karim" <anonymous@.discussions.microsoft.com> wrote
>>in message
>>news:145d01c499b4$34e51d50$a301280a@.phx.gbl...
>>We are using SQL 7 and Forte application and Win NT. I
>>have migrated DB to SQL 2000 and new Windows 2000
server.
>>Our DB is big, 150 G. Testing on new 2000 server, I see
>>that many of our procedures are running slower. One
>>procedure is like not running. Taking all resources and
>>hanging. I can ont even see the exec plan. I have tried
>>set plan still not working. This particular procedure is
>>using multiple unions and one of them using self join.
>>I have other procedures they are not that compecated but
>>the are slow too. I am having hard time convincing my
>boss
>>that SQL 2000 is better than 7. We really don't see any.
>>On top of that some procedure are not working at all.
>>Please send me your expert opinion.
>>.
>>
>>.
>.
>

Is SQL 2000 32 bit supported

Hello All,

I need to know if SQL 2000 32 bit is supported on a Windows 2003 64 bit on a x86 processor server. The server is clustered.

I wasn't aware you can install 64bit OS on an x86 machine, that just doesn't sound right.

Regardless, SQL 2000 (32-bit) cannot be installed on 64-bit OS. However SQL 2005 (32-bit) is allowed to be installed on 64-bit OS. Someone can correct me if I'm wrong.

|||

SQL 2000 (32-bit) cannot be installed on a 64-bit machine, but SQL 2000 64-bit can. With SQL 2005, both 32-bit and 64-bit can be installed on a 64-bit machine.

Thanks,
Sam Lester (MSFT)

Is server downgrade possible?

Hello,
my question is simple, i guess, if anyone can help me solve this problem:
I just installed Windows 2003 SBS Premium R2 but i have a software using SQL Server 2000 and not the one included in this version, 2005 wich is not compatible with. How can i downgrade, where cand i get the older server if the downgrade is possible and what else can i do before i shoot myself? Is there any license issue that will not allow me the downgrade?
Thank You!!!
SBS Premium R2 comes with 2005, but prior releases came with 2000. So, I would try to uninstall 2005 and reinstall 2000 with your install disks for the prior release.

Alternatively, you can install an MSDE instance on the same server and have it host your SQL 2000 database.

As I understand, however, if the install process for R2 upgraded the database itself, then you can't downgrade the database. Rather, you'd have to restore the most recent backup of the 2000 database.
|||Well, i don't have an older SQL 2000 database backup (also don't have a prior SBS 2003 server release) because we never used SQL before, version 2005 is uninstalled already but i don't know where from to download/get the SQL 2000 server as long as "Microsoft's ways" are a big mistery to me... if someone can drop a link for the SQL 2000 server would be great, just any version of the SQL 2000 that will work/install fine on our version of Windows, our software can't use the SQL 2005 included in SBS Premium 2003 R2, that's why i'm in trouble, nobody told me that before buying this license...
Many Thanks
|||

Don't you love it when they omit the details!

Here's a link to MSDE 2000 download...

http://www.microsoft.com/downloads/details.aspx?FamilyID=413744D1-A0BC-479F-BAFA-E4B278EB9147&displaylang=en

MSDE is the equivalent of SQL Server 2000 Engine, but other features are limited or not supported in the free version. For instance, performance is "throttled" after a certain number of users (about 16?) connect. If you don't know if those features are required by your database / application, I guess it's worth a try anyway. You can manage a SQL 2000 instance with SSMS that comes with SQL 2005.

Good luck...

Del

Is server downgrade possible?

Hello,
my question is simple, i guess, if anyone can help me solve this problem:
I just installed Windows 2003 SBS Premium R2 but i have a software using SQL Server 2000 and not the one included in this version, 2005 wich is not compatible with. How can i downgrade, where cand i get the older server if the downgrade is possible and what else can i do before i shoot myself? Is there any license issue that will not allow me the downgrade?
Thank You!!!SBS Premium R2 comes with 2005, but prior releases came with 2000. So, I would try to uninstall 2005 and reinstall 2000 with your install disks for the prior release.

Alternatively, you can install an MSDE instance on the same server and have it host your SQL 2000 database.

As I understand, however, if the install process for R2 upgraded the database itself, then you can't downgrade the database. Rather, you'd have to restore the most recent backup of the 2000 database.|||Well, i don't have an older SQL 2000 database backup (also don't have a prior SBS 2003 server release) because we never used SQL before, version 2005 is uninstalled already but i don't know where from to download/get the SQL 2000 server as long as "Microsoft's ways" are a big mistery to me... if someone can drop a link for the SQL 2000 server would be great, just any version of the SQL 2000 that will work/install fine on our version of Windows, our software can't use the SQL 2005 included in SBS Premium 2003 R2, that's why i'm in trouble, nobody told me that before buying this license...
Many Thanks|||

Don't you love it when they omit the details!

Here's a link to MSDE 2000 download...

http://www.microsoft.com/downloads/details.aspx?FamilyID=413744D1-A0BC-479F-BAFA-E4B278EB9147&displaylang=en

Good luck...

Del

Wednesday, March 7, 2012

Is Reporting Services Suppot to take the RDL Report Objects in Windows Form

i have place the textboxes in RDL report in Reporting Services and set there name. i want to access those text boxes from the Windows Form.

For Example

In Windows Form

Dim obj as RDLReport

Obj.TextBox1.Text="Ali How are you"

.Can i do that.?

No. You can set the properties of the text box to be an expression, but you cannot programmatically write to the text box like that.|||To do something like this you should bind the text in the textbox to a parameter value, and then pass that parameter to your viewer control.

Monday, February 20, 2012

Is NTBACKUP breaking SQL Server 2005 differential backup chain..again?

Hi All,
We recently upgraded a box running Windows Server 2003 SP1 with SQL Server
2005 SP1 to Windows Server 2003 SP2 and SQL Server SP2.
For some time we have had the following backup regime for some SQL Server
full recovery model databases that are present on this server:
1) SQL Server Full backup on a Sunday night at around midnight
2) SQL Server Transaction log backups every three hours from 03:00
until 18:00
3) SQL Server Differential backups at 21:00 every day except Sunday
night.
4) NTBACKUP at 22:00 every night to do a differential backup of the
server using option /SNAP:on (Use Volume Shadow Copy) but with the directory
containing SQL Server database files excluded.
5) Note the output TRN files and BAK files from points 1 to 4 above are
mirrored off to another server by a 3rd party application, not by using
NTBACKUP.
All has worked fine for many months until our upgrade of the server to SP2
of SQL Server and SP2 of Windows Server 2003.
Immediately after that upgrade we would get the Full backup at point 1
completing as planned, the transaction log backups at point 2 complete on
the Monday, then the differential SQL backup on Monday night works fine as
well followed by the NT Backup at point 4. The cycle works fine on the
Tuesday up to the repeat of the SQL Server differential backup at point 3
which fails for every database with an error message not unlike this
example:
[QUOTE]
Executing the query "BACKUP DATABASE [dbTPL] TO DISK = N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak'
WITH DIFFERENTIAL , NOFORMAT, NOINIT, NAME = N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD, STATS = 10" failed
with the following error: "Cannot perform a differential backup for database
"dbTPL", because a current database backup does not exist. Perform a full
database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL
option. BACKUP DATABASE is terminating abnormally.". Possible failure
reasons: Problems with the query, "ResultSet" property not set correctly,
parameters not set correctly, or connection not established correctly.
[END QUOTE]
As if NTBackup has broken the link to the original full backup.
There used to be a problem with the Volume Shadow Copy Service whereby
NTBACKUP would not manage a backup of SQL Server Full recovery model
databases. As in this article here: http://support.microsoft.com/kb/903643
I noticed in the event log since our upgrade to SP2 of Windows Server 2003
and SQL Server 2005 we get errors around the time NTBACKUP runs that are
like this one:
[QUOTE]
Event Type: Error
Event Source: SQLVDI
Event Category: None
Event ID: 1
Date: 29/03/2007
Time: 07:03:47
User: N/A
Computer: SERVERA
Description:
SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
ErrorCode=(288)Attempt to release mutex not owned by caller.. Process=1968.
Thread=3564. Client. Instance=. VD=.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
[END QUOTE]
The SQL Server maintenance plans at points 1 through to 3 above are not hand
crafted scripts, just output from the Maintenance plan wizard. Furthermore
they have been deleted and recreated since updating to SP2 in case that was
the cause but the problem remains.
The only way around this problem has been to amend the NTBACKUP command at
point 4 above and use /SNAP:off so that it doesn't use the Volume Shadow
Copy service. I can only draw the conclusion that the Shadow Copy Service or
NTBackup has something to do with this? Has anybody else encountered a
similar problem?
I have been researching this for days but due to the relative brief period
since the release of Service Pack 2 for Windows Server 2003 there isn't
really too much about on the web regarding this. In fact I hadn't even
though of it being the NTBACKUP if it hadn't been for the thread I found
here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
Any tips / ideas much appreciated.
Kind RegardsCan you configure NTBACKUP to not grab the SQL Server database files? Just thinking out loud...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
> Hi All,
>
> We recently upgraded a box running Windows Server 2003 SP1 with SQL Server 2005 SP1 to Windows
> Server 2003 SP2 and SQL Server SP2.
>
> For some time we have had the following backup regime for some SQL Server full recovery model
> databases that are present on this server:
>
> 1) SQL Server Full backup on a Sunday night at around midnight
> 2) SQL Server Transaction log backups every three hours from 03:00 until 18:00
> 3) SQL Server Differential backups at 21:00 every day except Sunday night.
> 4) NTBACKUP at 22:00 every night to do a differential backup of the server using option
> /SNAP:on (Use Volume Shadow Copy) but with the directory containing SQL Server database files
> excluded.
> 5) Note the output TRN files and BAK files from points 1 to 4 above are mirrored off to
> another server by a 3rd party application, not by using NTBACKUP.
>
> All has worked fine for many months until our upgrade of the server to SP2 of SQL Server and SP2
> of Windows Server 2003.
>
> Immediately after that upgrade we would get the Full backup at point 1 completing as planned, the
> transaction log backups at point 2 complete on the Monday, then the differential SQL backup on
> Monday night works fine as well followed by the NT Backup at point 4. The cycle works fine on the
> Tuesday up to the repeat of the SQL Server differential backup at point 3 which fails for every
> database with an error message not unlike this example:
>
> [QUOTE]
> Executing the query "BACKUP DATABASE [dbTPL] TO DISK => N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak' WITH DIFFERENTIAL
> , NOFORMAT, NOINIT, NAME = N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD, STATS = 10"
> failed with the following error: "Cannot perform a differential backup for database "dbTPL",
> because a current database backup does not exist. Perform a full database backup by reissuing
> BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. BACKUP DATABASE is terminating
> abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set
> correctly, parameters not set correctly, or connection not established correctly.
> [END QUOTE]
>
> As if NTBackup has broken the link to the original full backup.
>
> There used to be a problem with the Volume Shadow Copy Service whereby NTBACKUP would not manage a
> backup of SQL Server Full recovery model databases. As in this article here:
> http://support.microsoft.com/kb/903643
>
> I noticed in the event log since our upgrade to SP2 of Windows Server 2003 and SQL Server 2005 we
> get errors around the time NTBACKUP runs that are like this one:
>
> [QUOTE]
> Event Type: Error
> Event Source: SQLVDI
> Event Category: None
> Event ID: 1
> Date: 29/03/2007
> Time: 07:03:47
> User: N/A
> Computer: SERVERA
> Description:
> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release mutex
> not owned by caller.. Process=1968. Thread=3564. Client. Instance=. VD=.
>
> For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
> [END QUOTE]
>
> The SQL Server maintenance plans at points 1 through to 3 above are not hand crafted scripts, just
> output from the Maintenance plan wizard. Furthermore they have been deleted and recreated since
> updating to SP2 in case that was the cause but the problem remains.
>
> The only way around this problem has been to amend the NTBACKUP command at point 4 above and use
> /SNAP:off so that it doesn't use the Volume Shadow Copy service. I can only draw the conclusion
> that the Shadow Copy Service or NTBackup has something to do with this? Has anybody else
> encountered a similar problem?
>
> I have been researching this for days but due to the relative brief period since the release of
> Service Pack 2 for Windows Server 2003 there isn't really too much about on the web regarding
> this. In fact I hadn't even though of it being the NTBACKUP if it hadn't been for the thread I
> found here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>
> Any tips / ideas much appreciated.
>
> Kind Regards
>
>
>|||Hi Tibor,
Some of the databases are quite large and backing them up fully using
NTBACKUP with snap:on option is not really an option. The idea is to leave
the SQL databases' backups outside of the control of NTBACKUP. This used to
work though until application of the Service Packs and now NTBACKUP seems to
be breaking that Differential chain. Although I hasten to add, that is the
only possible cause I have been able to identify thus far however I accept
there could be other causes. Luckily this server doesn't have a basket load
of other applications / services that could have any indirect effect on this
problem.
Kind Regards
Nick
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
> Can you configure NTBACKUP to not grab the SQL Server database files? Just
> thinking out loud...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>> Hi All,
>>
>> We recently upgraded a box running Windows Server 2003 SP1 with SQL
>> Server 2005 SP1 to Windows Server 2003 SP2 and SQL Server SP2.
>>
>> For some time we have had the following backup regime for some SQL Server
>> full recovery model databases that are present on this server:
>>
>> 1) SQL Server Full backup on a Sunday night at around midnight
>> 2) SQL Server Transaction log backups every three hours from 03:00
>> until 18:00
>> 3) SQL Server Differential backups at 21:00 every day except Sunday
>> night.
>> 4) NTBACKUP at 22:00 every night to do a differential backup of the
>> server using option /SNAP:on (Use Volume Shadow Copy) but with the
>> directory containing SQL Server database files excluded.
>> 5) Note the output TRN files and BAK files from points 1 to 4 above
>> are mirrored off to another server by a 3rd party application, not by
>> using NTBACKUP.
>>
>> All has worked fine for many months until our upgrade of the server to
>> SP2 of SQL Server and SP2 of Windows Server 2003.
>>
>> Immediately after that upgrade we would get the Full backup at point 1
>> completing as planned, the transaction log backups at point 2 complete on
>> the Monday, then the differential SQL backup on Monday night works fine
>> as well followed by the NT Backup at point 4. The cycle works fine on the
>> Tuesday up to the repeat of the SQL Server differential backup at point 3
>> which fails for every database with an error message not unlike this
>> example:
>>
>> [QUOTE]
>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak'
>> WITH DIFFERENTIAL , NOFORMAT, NOINIT, NAME =>> N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD, STATS = 10"
>> failed with the following error: "Cannot perform a differential backup
>> for database "dbTPL", because a current database backup does not exist.
>> Perform a full database backup by reissuing BACKUP DATABASE, omitting the
>> WITH DIFFERENTIAL option. BACKUP DATABASE is terminating abnormally.".
>> Possible failure reasons: Problems with the query, "ResultSet" property
>> not set correctly, parameters not set correctly, or connection not
>> established correctly.
>> [END QUOTE]
>>
>> As if NTBackup has broken the link to the original full backup.
>>
>> There used to be a problem with the Volume Shadow Copy Service whereby
>> NTBACKUP would not manage a backup of SQL Server Full recovery model
>> databases. As in this article here:
>> http://support.microsoft.com/kb/903643
>>
>> I noticed in the event log since our upgrade to SP2 of Windows Server
>> 2003 and SQL Server 2005 we get errors around the time NTBACKUP runs that
>> are like this one:
>>
>> [QUOTE]
>> Event Type: Error
>> Event Source: SQLVDI
>> Event Category: None
>> Event ID: 1
>> Date: 29/03/2007
>> Time: 07:03:47
>> User: N/A
>> Computer: SERVERA
>> Description:
>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
>> ErrorCode=(288)Attempt to release mutex not owned by caller..
>> Process=1968. Thread=3564. Client. Instance=. VD=.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> [END QUOTE]
>>
>> The SQL Server maintenance plans at points 1 through to 3 above are not
>> hand crafted scripts, just output from the Maintenance plan wizard.
>> Furthermore they have been deleted and recreated since updating to SP2 in
>> case that was the cause but the problem remains.
>>
>> The only way around this problem has been to amend the NTBACKUP command
>> at point 4 above and use /SNAP:off so that it doesn't use the Volume
>> Shadow Copy service. I can only draw the conclusion that the Shadow Copy
>> Service or NTBackup has something to do with this? Has anybody else
>> encountered a similar problem?
>>
>> I have been researching this for days but due to the relative brief
>> period since the release of Service Pack 2 for Windows Server 2003 there
>> isn't really too much about on the web regarding this. In fact I hadn't
>> even though of it being the NTBACKUP if it hadn't been for the thread I
>> found here:
>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>
>> Any tips / ideas much appreciated.
>>
>> Kind Regards
>>
>>
>>
>|||I see. SQL Server get confused even if NTBACKUP excludes the database files. Can you configure
NTBACKUP to not interface with SQL Server? It seems from the eventlog entry you posted that SQL
Server got some VDI call from NTBACKUP. This is probably the one that broke the backup chain.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
news:ec$Hn8ecHHA.3484@.TK2MSFTNGP04.phx.gbl...
> Hi Tibor,
> Some of the databases are quite large and backing them up fully using NTBACKUP with snap:on option
> is not really an option. The idea is to leave the SQL databases' backups outside of the control of
> NTBACKUP. This used to work though until application of the Service Packs and now NTBACKUP seems
> to be breaking that Differential chain. Although I hasten to add, that is the only possible cause
> I have been able to identify thus far however I accept there could be other causes. Luckily this
> server doesn't have a basket load of other applications / services that could have any indirect
> effect on this problem.
> Kind Regards
> Nick
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
>> Can you configure NTBACKUP to not grab the SQL Server database files? Just thinking out loud...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>> Hi All,
>>
>> We recently upgraded a box running Windows Server 2003 SP1 with SQL Server 2005 SP1 to Windows
>> Server 2003 SP2 and SQL Server SP2.
>>
>> For some time we have had the following backup regime for some SQL Server full recovery model
>> databases that are present on this server:
>>
>> 1) SQL Server Full backup on a Sunday night at around midnight
>> 2) SQL Server Transaction log backups every three hours from 03:00 until 18:00
>> 3) SQL Server Differential backups at 21:00 every day except Sunday night.
>> 4) NTBACKUP at 22:00 every night to do a differential backup of the server using option
>> /SNAP:on (Use Volume Shadow Copy) but with the directory containing SQL Server database files
>> excluded.
>> 5) Note the output TRN files and BAK files from points 1 to 4 above are mirrored off to
>> another server by a 3rd party application, not by using NTBACKUP.
>>
>> All has worked fine for many months until our upgrade of the server to SP2 of SQL Server and SP2
>> of Windows Server 2003.
>>
>> Immediately after that upgrade we would get the Full backup at point 1 completing as planned,
>> the transaction log backups at point 2 complete on the Monday, then the differential SQL backup
>> on Monday night works fine as well followed by the NT Backup at point 4. The cycle works fine on
>> the Tuesday up to the repeat of the SQL Server differential backup at point 3 which fails for
>> every database with an error message not unlike this example:
>>
>> [QUOTE]
>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak' WITH
>> DIFFERENTIAL , NOFORMAT, NOINIT, NAME = N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD,
>> STATS = 10" failed with the following error: "Cannot perform a differential backup for database
>> "dbTPL", because a current database backup does not exist. Perform a full database backup by
>> reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. BACKUP DATABASE is terminating
>> abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set
>> correctly, parameters not set correctly, or connection not established correctly.
>> [END QUOTE]
>>
>> As if NTBackup has broken the link to the original full backup.
>>
>> There used to be a problem with the Volume Shadow Copy Service whereby NTBACKUP would not manage
>> a backup of SQL Server Full recovery model databases. As in this article here:
>> http://support.microsoft.com/kb/903643
>>
>> I noticed in the event log since our upgrade to SP2 of Windows Server 2003 and SQL Server 2005
>> we get errors around the time NTBACKUP runs that are like this one:
>>
>> [QUOTE]
>> Event Type: Error
>> Event Source: SQLVDI
>> Event Category: None
>> Event ID: 1
>> Date: 29/03/2007
>> Time: 07:03:47
>> User: N/A
>> Computer: SERVERA
>> Description:
>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release
>> mutex not owned by caller.. Process=1968. Thread=3564. Client. Instance=. VD=.
>>
>> For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
>> [END QUOTE]
>>
>> The SQL Server maintenance plans at points 1 through to 3 above are not hand crafted scripts,
>> just output from the Maintenance plan wizard. Furthermore they have been deleted and recreated
>> since updating to SP2 in case that was the cause but the problem remains.
>>
>> The only way around this problem has been to amend the NTBACKUP command at point 4 above and use
>> /SNAP:off so that it doesn't use the Volume Shadow Copy service. I can only draw the conclusion
>> that the Shadow Copy Service or NTBackup has something to do with this? Has anybody else
>> encountered a similar problem?
>>
>> I have been researching this for days but due to the relative brief period since the release of
>> Service Pack 2 for Windows Server 2003 there isn't really too much about on the web regarding
>> this. In fact I hadn't even though of it being the NTBACKUP if it hadn't been for the thread I
>> found here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>
>> Any tips / ideas much appreciated.
>>
>> Kind Regards
>>
>>
>>
>>
>|||Hi Tibor,
Unfortunately now you cannot. The only way to prevent this is to turn off
the command line SNAP option of NTBACKUP with /snap:off however this defeats
the object since there are other files (Non-SQL Server) on the drive that I
do want to have backed up even though they maybe in use.
Regards
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Od23CWhcHHA.2316@.TK2MSFTNGP04.phx.gbl...
>I see. SQL Server get confused even if NTBACKUP excludes the database
>files. Can you configure NTBACKUP to not interface with SQL Server? It
>seems from the eventlog entry you posted that SQL Server got some VDI call
>from NTBACKUP. This is probably the one that broke the backup chain.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
> news:ec$Hn8ecHHA.3484@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Some of the databases are quite large and backing them up fully using
>> NTBACKUP with snap:on option is not really an option. The idea is to
>> leave the SQL databases' backups outside of the control of NTBACKUP. This
>> used to work though until application of the Service Packs and now
>> NTBACKUP seems to be breaking that Differential chain. Although I hasten
>> to add, that is the only possible cause I have been able to identify thus
>> far however I accept there could be other causes. Luckily this server
>> doesn't have a basket load of other applications / services that could
>> have any indirect effect on this problem.
>> Kind Regards
>> Nick
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
>> Can you configure NTBACKUP to not grab the SQL Server database files?
>> Just thinking out loud...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>> Hi All,
>>
>> We recently upgraded a box running Windows Server 2003 SP1 with SQL
>> Server 2005 SP1 to Windows Server 2003 SP2 and SQL Server SP2.
>>
>> For some time we have had the following backup regime for some SQL
>> Server full recovery model databases that are present on this server:
>>
>> 1) SQL Server Full backup on a Sunday night at around midnight
>> 2) SQL Server Transaction log backups every three hours from 03:00
>> until 18:00
>> 3) SQL Server Differential backups at 21:00 every day except
>> Sunday night.
>> 4) NTBACKUP at 22:00 every night to do a differential backup of
>> the server using option /SNAP:on (Use Volume Shadow Copy) but with the
>> directory containing SQL Server database files excluded.
>> 5) Note the output TRN files and BAK files from points 1 to 4
>> above are mirrored off to another server by a 3rd party application,
>> not by using NTBACKUP.
>>
>> All has worked fine for many months until our upgrade of the server to
>> SP2 of SQL Server and SP2 of Windows Server 2003.
>>
>> Immediately after that upgrade we would get the Full backup at point 1
>> completing as planned, the transaction log backups at point 2 complete
>> on the Monday, then the differential SQL backup on Monday night works
>> fine as well followed by the NT Backup at point 4. The cycle works fine
>> on the Tuesday up to the repeat of the SQL Server differential backup
>> at point 3 which fails for every database with an error message not
>> unlike this example:
>>
>> [QUOTE]
>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak'
>> WITH DIFFERENTIAL , NOFORMAT, NOINIT, NAME =>> N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD, STATS = 10"
>> failed with the following error: "Cannot perform a differential backup
>> for database "dbTPL", because a current database backup does not exist.
>> Perform a full database backup by reissuing BACKUP DATABASE, omitting
>> the WITH DIFFERENTIAL option. BACKUP DATABASE is terminating
>> abnormally.". Possible failure reasons: Problems with the query,
>> "ResultSet" property not set correctly, parameters not set correctly,
>> or connection not established correctly.
>> [END QUOTE]
>>
>> As if NTBackup has broken the link to the original full backup.
>>
>> There used to be a problem with the Volume Shadow Copy Service whereby
>> NTBACKUP would not manage a backup of SQL Server Full recovery model
>> databases. As in this article here:
>> http://support.microsoft.com/kb/903643
>>
>> I noticed in the event log since our upgrade to SP2 of Windows Server
>> 2003 and SQL Server 2005 we get errors around the time NTBACKUP runs
>> that are like this one:
>>
>> [QUOTE]
>> Event Type: Error
>> Event Source: SQLVDI
>> Event Category: None
>> Event ID: 1
>> Date: 29/03/2007
>> Time: 07:03:47
>> User: N/A
>> Computer: SERVERA
>> Description:
>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
>> ErrorCode=(288)Attempt to release mutex not owned by caller..
>> Process=1968. Thread=3564. Client. Instance=. VD=.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> [END QUOTE]
>>
>> The SQL Server maintenance plans at points 1 through to 3 above are not
>> hand crafted scripts, just output from the Maintenance plan wizard.
>> Furthermore they have been deleted and recreated since updating to SP2
>> in case that was the cause but the problem remains.
>>
>> The only way around this problem has been to amend the NTBACKUP command
>> at point 4 above and use /SNAP:off so that it doesn't use the Volume
>> Shadow Copy service. I can only draw the conclusion that the Shadow
>> Copy Service or NTBackup has something to do with this? Has anybody
>> else encountered a similar problem?
>>
>> I have been researching this for days but due to the relative brief
>> period since the release of Service Pack 2 for Windows Server 2003
>> there isn't really too much about on the web regarding this. In fact I
>> hadn't even though of it being the NTBACKUP if it hadn't been for the
>> thread I found here:
>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>
>> Any tips / ideas much appreciated.
>>
>> Kind Regards
>>
>>
>>
>>
>>
>|||> Unfortunately now you cannot.
That sounds horrible to me, to be honest. I'd talk to the guys who wrote this software...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
news:eP70LihcHHA.1244@.TK2MSFTNGP04.phx.gbl...
> Hi Tibor,
> Unfortunately now you cannot. The only way to prevent this is to turn off the command line SNAP
> option of NTBACKUP with /snap:off however this defeats the object since there are other files
> (Non-SQL Server) on the drive that I do want to have backed up even though they maybe in use.
> Regards
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:Od23CWhcHHA.2316@.TK2MSFTNGP04.phx.gbl...
>>I see. SQL Server get confused even if NTBACKUP excludes the database files. Can you configure
>>NTBACKUP to not interface with SQL Server? It seems from the eventlog entry you posted that SQL
>>Server got some VDI call from NTBACKUP. This is probably the one that broke the backup chain.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:ec$Hn8ecHHA.3484@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Some of the databases are quite large and backing them up fully using NTBACKUP with snap:on
>> option is not really an option. The idea is to leave the SQL databases' backups outside of the
>> control of NTBACKUP. This used to work though until application of the Service Packs and now
>> NTBACKUP seems to be breaking that Differential chain. Although I hasten to add, that is the
>> only possible cause I have been able to identify thus far however I accept there could be other
>> causes. Luckily this server doesn't have a basket load of other applications / services that
>> could have any indirect effect on this problem.
>> Kind Regards
>> Nick
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
>> Can you configure NTBACKUP to not grab the SQL Server database files? Just thinking out loud...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>> Hi All,
>>
>> We recently upgraded a box running Windows Server 2003 SP1 with SQL Server 2005 SP1 to Windows
>> Server 2003 SP2 and SQL Server SP2.
>>
>> For some time we have had the following backup regime for some SQL Server full recovery model
>> databases that are present on this server:
>>
>> 1) SQL Server Full backup on a Sunday night at around midnight
>> 2) SQL Server Transaction log backups every three hours from 03:00 until 18:00
>> 3) SQL Server Differential backups at 21:00 every day except Sunday night.
>> 4) NTBACKUP at 22:00 every night to do a differential backup of the server using option
>> /SNAP:on (Use Volume Shadow Copy) but with the directory containing SQL Server database files
>> excluded.
>> 5) Note the output TRN files and BAK files from points 1 to 4 above are mirrored off to
>> another server by a 3rd party application, not by using NTBACKUP.
>>
>> All has worked fine for many months until our upgrade of the server to SP2 of SQL Server and
>> SP2 of Windows Server 2003.
>>
>> Immediately after that upgrade we would get the Full backup at point 1 completing as planned,
>> the transaction log backups at point 2 complete on the Monday, then the differential SQL
>> backup on Monday night works fine as well followed by the NT Backup at point 4. The cycle
>> works fine on the Tuesday up to the repeat of the SQL Server differential backup at point 3
>> which fails for every database with an error message not unlike this example:
>>
>> [QUOTE]
>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak' WITH
>> DIFFERENTIAL , NOFORMAT, NOINIT, NAME = N'dbTPL_backup_20070327200004', SKIP, REWIND,
>> NOUNLOAD, STATS = 10" failed with the following error: "Cannot perform a differential backup
>> for database "dbTPL", because a current database backup does not exist. Perform a full
>> database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. BACKUP
>> DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query,
>> "ResultSet" property not set correctly, parameters not set correctly, or connection not
>> established correctly.
>> [END QUOTE]
>>
>> As if NTBackup has broken the link to the original full backup.
>>
>> There used to be a problem with the Volume Shadow Copy Service whereby NTBACKUP would not
>> manage a backup of SQL Server Full recovery model databases. As in this article here:
>> http://support.microsoft.com/kb/903643
>>
>> I noticed in the event log since our upgrade to SP2 of Windows Server 2003 and SQL Server 2005
>> we get errors around the time NTBACKUP runs that are like this one:
>>
>> [QUOTE]
>> Event Type: Error
>> Event Source: SQLVDI
>> Event Category: None
>> Event ID: 1
>> Date: 29/03/2007
>> Time: 07:03:47
>> User: N/A
>> Computer: SERVERA
>> Description:
>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release
>> mutex not owned by caller.. Process=1968. Thread=3564. Client. Instance=. VD=.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> [END QUOTE]
>>
>> The SQL Server maintenance plans at points 1 through to 3 above are not hand crafted scripts,
>> just output from the Maintenance plan wizard. Furthermore they have been deleted and recreated
>> since updating to SP2 in case that was the cause but the problem remains.
>>
>> The only way around this problem has been to amend the NTBACKUP command at point 4 above and
>> use /SNAP:off so that it doesn't use the Volume Shadow Copy service. I can only draw the
>> conclusion that the Shadow Copy Service or NTBackup has something to do with this? Has anybody
>> else encountered a similar problem?
>>
>> I have been researching this for days but due to the relative brief period since the release
>> of Service Pack 2 for Windows Server 2003 there isn't really too much about on the web
>> regarding this. In fact I hadn't even though of it being the NTBACKUP if it hadn't been for
>> the thread I found here:
>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>
>> Any tips / ideas much appreciated.
>>
>> Kind Regards
>>
>>
>>
>>
>>
>>
>|||NTBACKUP is Microsoft. It's the default backup software in the operating
system. I don't think talking to them is going to get me anywhere.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uXTpylhcHHA.2068@.TK2MSFTNGP06.phx.gbl...
>> Unfortunately now you cannot.
> That sounds horrible to me, to be honest. I'd talk to the guys who wrote
> this software...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
> news:eP70LihcHHA.1244@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Unfortunately now you cannot. The only way to prevent this is to turn off
>> the command line SNAP option of NTBACKUP with /snap:off however this
>> defeats the object since there are other files (Non-SQL Server) on the
>> drive that I do want to have backed up even though they maybe in use.
>> Regards
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:Od23CWhcHHA.2316@.TK2MSFTNGP04.phx.gbl...
>>I see. SQL Server get confused even if NTBACKUP excludes the database
>>files. Can you configure NTBACKUP to not interface with SQL Server? It
>>seems from the eventlog entry you posted that SQL Server got some VDI
>>call from NTBACKUP. This is probably the one that broke the backup chain.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:ec$Hn8ecHHA.3484@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Some of the databases are quite large and backing them up fully using
>> NTBACKUP with snap:on option is not really an option. The idea is to
>> leave the SQL databases' backups outside of the control of NTBACKUP.
>> This used to work though until application of the Service Packs and now
>> NTBACKUP seems to be breaking that Differential chain. Although I
>> hasten to add, that is the only possible cause I have been able to
>> identify thus far however I accept there could be other causes. Luckily
>> this server doesn't have a basket load of other applications / services
>> that could have any indirect effect on this problem.
>> Kind Regards
>> Nick
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
>> wrote in message news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
>> Can you configure NTBACKUP to not grab the SQL Server database files?
>> Just thinking out loud...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>> Hi All,
>>
>> We recently upgraded a box running Windows Server 2003 SP1 with SQL
>> Server 2005 SP1 to Windows Server 2003 SP2 and SQL Server SP2.
>>
>> For some time we have had the following backup regime for some SQL
>> Server full recovery model databases that are present on this server:
>>
>> 1) SQL Server Full backup on a Sunday night at around midnight
>> 2) SQL Server Transaction log backups every three hours from
>> 03:00 until 18:00
>> 3) SQL Server Differential backups at 21:00 every day except
>> Sunday night.
>> 4) NTBACKUP at 22:00 every night to do a differential backup of
>> the server using option /SNAP:on (Use Volume Shadow Copy) but with
>> the directory containing SQL Server database files excluded.
>> 5) Note the output TRN files and BAK files from points 1 to 4
>> above are mirrored off to another server by a 3rd party application,
>> not by using NTBACKUP.
>>
>> All has worked fine for many months until our upgrade of the server
>> to SP2 of SQL Server and SP2 of Windows Server 2003.
>>
>> Immediately after that upgrade we would get the Full backup at point
>> 1 completing as planned, the transaction log backups at point 2
>> complete on the Monday, then the differential SQL backup on Monday
>> night works fine as well followed by the NT Backup at point 4. The
>> cycle works fine on the Tuesday up to the repeat of the SQL Server
>> differential backup at point 3 which fails for every database with an
>> error message not unlike this example:
>>
>> [QUOTE]
>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak'
>> WITH DIFFERENTIAL , NOFORMAT, NOINIT, NAME =>> N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD, STATS = 10"
>> failed with the following error: "Cannot perform a differential
>> backup for database "dbTPL", because a current database backup does
>> not exist. Perform a full database backup by reissuing BACKUP
>> DATABASE, omitting the WITH DIFFERENTIAL option. BACKUP DATABASE is
>> terminating abnormally.". Possible failure reasons: Problems with the
>> query, "ResultSet" property not set correctly, parameters not set
>> correctly, or connection not established correctly.
>> [END QUOTE]
>>
>> As if NTBackup has broken the link to the original full backup.
>>
>> There used to be a problem with the Volume Shadow Copy Service
>> whereby NTBACKUP would not manage a backup of SQL Server Full
>> recovery model databases. As in this article here:
>> http://support.microsoft.com/kb/903643
>>
>> I noticed in the event log since our upgrade to SP2 of Windows Server
>> 2003 and SQL Server 2005 we get errors around the time NTBACKUP runs
>> that are like this one:
>>
>> [QUOTE]
>> Event Type: Error
>> Event Source: SQLVDI
>> Event Category: None
>> Event ID: 1
>> Date: 29/03/2007
>> Time: 07:03:47
>> User: N/A
>> Computer: SERVERA
>> Description:
>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
>> ErrorCode=(288)Attempt to release mutex not owned by caller..
>> Process=1968. Thread=3564. Client. Instance=. VD=.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> [END QUOTE]
>>
>> The SQL Server maintenance plans at points 1 through to 3 above are
>> not hand crafted scripts, just output from the Maintenance plan
>> wizard. Furthermore they have been deleted and recreated since
>> updating to SP2 in case that was the cause but the problem remains.
>>
>> The only way around this problem has been to amend the NTBACKUP
>> command at point 4 above and use /SNAP:off so that it doesn't use the
>> Volume Shadow Copy service. I can only draw the conclusion that the
>> Shadow Copy Service or NTBackup has something to do with this? Has
>> anybody else encountered a similar problem?
>>
>> I have been researching this for days but due to the relative brief
>> period since the release of Service Pack 2 for Windows Server 2003
>> there isn't really too much about on the web regarding this. In fact
>> I hadn't even though of it being the NTBACKUP if it hadn't been for
>> the thread I found here:
>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>
>> Any tips / ideas much appreciated.
>>
>> Kind Regards
>>
>>
>>
>>
>>
>>
>>
>|||> NTBACKUP is Microsoft.
I know. I was just suggestion that this should be configurable in this app. Perhaps ask in a Windows
forum? To the best of my knowledge, there's no way to say to SQL Server to ignore this backup VDI
message.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
news:OOVKXyhcHHA.984@.TK2MSFTNGP04.phx.gbl...
> NTBACKUP is Microsoft. It's the default backup software in the operating system. I don't think
> talking to them is going to get me anywhere.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:uXTpylhcHHA.2068@.TK2MSFTNGP06.phx.gbl...
>> Unfortunately now you cannot.
>> That sounds horrible to me, to be honest. I'd talk to the guys who wrote this software...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:eP70LihcHHA.1244@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Unfortunately now you cannot. The only way to prevent this is to turn off the command line SNAP
>> option of NTBACKUP with /snap:off however this defeats the object since there are other files
>> (Non-SQL Server) on the drive that I do want to have backed up even though they maybe in use.
>> Regards
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:Od23CWhcHHA.2316@.TK2MSFTNGP04.phx.gbl...
>>I see. SQL Server get confused even if NTBACKUP excludes the database files. Can you configure
>>NTBACKUP to not interface with SQL Server? It seems from the eventlog entry you posted that SQL
>>Server got some VDI call from NTBACKUP. This is probably the one that broke the backup chain.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:ec$Hn8ecHHA.3484@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Some of the databases are quite large and backing them up fully using NTBACKUP with snap:on
>> option is not really an option. The idea is to leave the SQL databases' backups outside of the
>> control of NTBACKUP. This used to work though until application of the Service Packs and now
>> NTBACKUP seems to be breaking that Differential chain. Although I hasten to add, that is the
>> only possible cause I have been able to identify thus far however I accept there could be
>> other causes. Luckily this server doesn't have a basket load of other applications / services
>> that could have any indirect effect on this problem.
>> Kind Regards
>> Nick
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
>> Can you configure NTBACKUP to not grab the SQL Server database files? Just thinking out
>> loud...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>>> Hi All,
>>>
>>>
>>>
>>> We recently upgraded a box running Windows Server 2003 SP1 with SQL Server 2005 SP1 to
>>> Windows Server 2003 SP2 and SQL Server SP2.
>>>
>>>
>>>
>>> For some time we have had the following backup regime for some SQL Server full recovery
>>> model databases that are present on this server:
>>>
>>>
>>>
>>> 1) SQL Server Full backup on a Sunday night at around midnight
>>>
>>> 2) SQL Server Transaction log backups every three hours from 03:00 until 18:00
>>>
>>> 3) SQL Server Differential backups at 21:00 every day except Sunday night.
>>>
>>> 4) NTBACKUP at 22:00 every night to do a differential backup of the server using option
>>> /SNAP:on (Use Volume Shadow Copy) but with the directory containing SQL Server database
>>> files excluded.
>>>
>>> 5) Note the output TRN files and BAK files from points 1 to 4 above are mirrored off to
>>> another server by a 3rd party application, not by using NTBACKUP.
>>>
>>>
>>>
>>> All has worked fine for many months until our upgrade of the server to SP2 of SQL Server and
>>> SP2 of Windows Server 2003.
>>>
>>>
>>>
>>> Immediately after that upgrade we would get the Full backup at point 1 completing as
>>> planned, the transaction log backups at point 2 complete on the Monday, then the
>>> differential SQL backup on Monday night works fine as well followed by the NT Backup at
>>> point 4. The cycle works fine on the Tuesday up to the repeat of the SQL Server differential
>>> backup at point 3 which fails for every database with an error message not unlike this
>>> example:
>>>
>>>
>>>
>>> [QUOTE]
>>>
>>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak' WITH
>>> DIFFERENTIAL , NOFORMAT, NOINIT, NAME = N'dbTPL_backup_20070327200004', SKIP, REWIND,
>>> NOUNLOAD, STATS = 10" failed with the following error: "Cannot perform a differential backup
>>> for database "dbTPL", because a current database backup does not exist. Perform a full
>>> database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. BACKUP
>>> DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query,
>>> "ResultSet" property not set correctly, parameters not set correctly, or connection not
>>> established correctly.
>>>
>>> [END QUOTE]
>>>
>>>
>>>
>>> As if NTBackup has broken the link to the original full backup.
>>>
>>>
>>>
>>> There used to be a problem with the Volume Shadow Copy Service whereby NTBACKUP would not
>>> manage a backup of SQL Server Full recovery model databases. As in this article here:
>>> http://support.microsoft.com/kb/903643
>>>
>>>
>>>
>>> I noticed in the event log since our upgrade to SP2 of Windows Server 2003 and SQL Server
>>> 2005 we get errors around the time NTBACKUP runs that are like this one:
>>>
>>>
>>>
>>> [QUOTE]
>>>
>>> Event Type: Error
>>>
>>> Event Source: SQLVDI
>>>
>>> Event Category: None
>>>
>>> Event ID: 1
>>>
>>> Date: 29/03/2007
>>>
>>> Time: 07:03:47
>>>
>>> User: N/A
>>>
>>> Computer: SERVERA
>>>
>>> Description:
>>>
>>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release
>>> mutex not owned by caller.. Process=1968. Thread=3564. Client. Instance=. VD=.
>>>
>>>
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>>
>>> [END QUOTE]
>>>
>>>
>>>
>>> The SQL Server maintenance plans at points 1 through to 3 above are not hand crafted
>>> scripts, just output from the Maintenance plan wizard. Furthermore they have been deleted
>>> and recreated since updating to SP2 in case that was the cause but the problem remains.
>>>
>>>
>>>
>>> The only way around this problem has been to amend the NTBACKUP command at point 4 above and
>>> use /SNAP:off so that it doesn't use the Volume Shadow Copy service. I can only draw the
>>> conclusion that the Shadow Copy Service or NTBackup has something to do with this? Has
>>> anybody else encountered a similar problem?
>>>
>>>
>>>
>>> I have been researching this for days but due to the relative brief period since the release
>>> of Service Pack 2 for Windows Server 2003 there isn't really too much about on the web
>>> regarding this. In fact I hadn't even though of it being the NTBACKUP if it hadn't been for
>>> the thread I found here:
>>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>>
>>>
>>>
>>> Any tips / ideas much appreciated.
>>>
>>>
>>>
>>> Kind Regards
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||Come to think of it, perhaps stopping the SQL Server VSS service... But I don't know what side
effects that would have. I'd check with MS first.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
news:OOVKXyhcHHA.984@.TK2MSFTNGP04.phx.gbl...
> NTBACKUP is Microsoft. It's the default backup software in the operating system. I don't think
> talking to them is going to get me anywhere.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:uXTpylhcHHA.2068@.TK2MSFTNGP06.phx.gbl...
>> Unfortunately now you cannot.
>> That sounds horrible to me, to be honest. I'd talk to the guys who wrote this software...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:eP70LihcHHA.1244@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Unfortunately now you cannot. The only way to prevent this is to turn off the command line SNAP
>> option of NTBACKUP with /snap:off however this defeats the object since there are other files
>> (Non-SQL Server) on the drive that I do want to have backed up even though they maybe in use.
>> Regards
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:Od23CWhcHHA.2316@.TK2MSFTNGP04.phx.gbl...
>>I see. SQL Server get confused even if NTBACKUP excludes the database files. Can you configure
>>NTBACKUP to not interface with SQL Server? It seems from the eventlog entry you posted that SQL
>>Server got some VDI call from NTBACKUP. This is probably the one that broke the backup chain.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:ec$Hn8ecHHA.3484@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Some of the databases are quite large and backing them up fully using NTBACKUP with snap:on
>> option is not really an option. The idea is to leave the SQL databases' backups outside of the
>> control of NTBACKUP. This used to work though until application of the Service Packs and now
>> NTBACKUP seems to be breaking that Differential chain. Although I hasten to add, that is the
>> only possible cause I have been able to identify thus far however I accept there could be
>> other causes. Luckily this server doesn't have a basket load of other applications / services
>> that could have any indirect effect on this problem.
>> Kind Regards
>> Nick
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
>> Can you configure NTBACKUP to not grab the SQL Server database files? Just thinking out
>> loud...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>>> Hi All,
>>>
>>>
>>>
>>> We recently upgraded a box running Windows Server 2003 SP1 with SQL Server 2005 SP1 to
>>> Windows Server 2003 SP2 and SQL Server SP2.
>>>
>>>
>>>
>>> For some time we have had the following backup regime for some SQL Server full recovery
>>> model databases that are present on this server:
>>>
>>>
>>>
>>> 1) SQL Server Full backup on a Sunday night at around midnight
>>>
>>> 2) SQL Server Transaction log backups every three hours from 03:00 until 18:00
>>>
>>> 3) SQL Server Differential backups at 21:00 every day except Sunday night.
>>>
>>> 4) NTBACKUP at 22:00 every night to do a differential backup of the server using option
>>> /SNAP:on (Use Volume Shadow Copy) but with the directory containing SQL Server database
>>> files excluded.
>>>
>>> 5) Note the output TRN files and BAK files from points 1 to 4 above are mirrored off to
>>> another server by a 3rd party application, not by using NTBACKUP.
>>>
>>>
>>>
>>> All has worked fine for many months until our upgrade of the server to SP2 of SQL Server and
>>> SP2 of Windows Server 2003.
>>>
>>>
>>>
>>> Immediately after that upgrade we would get the Full backup at point 1 completing as
>>> planned, the transaction log backups at point 2 complete on the Monday, then the
>>> differential SQL backup on Monday night works fine as well followed by the NT Backup at
>>> point 4. The cycle works fine on the Tuesday up to the repeat of the SQL Server differential
>>> backup at point 3 which fails for every database with an error message not unlike this
>>> example:
>>>
>>>
>>>
>>> [QUOTE]
>>>
>>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak' WITH
>>> DIFFERENTIAL , NOFORMAT, NOINIT, NAME = N'dbTPL_backup_20070327200004', SKIP, REWIND,
>>> NOUNLOAD, STATS = 10" failed with the following error: "Cannot perform a differential backup
>>> for database "dbTPL", because a current database backup does not exist. Perform a full
>>> database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. BACKUP
>>> DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query,
>>> "ResultSet" property not set correctly, parameters not set correctly, or connection not
>>> established correctly.
>>>
>>> [END QUOTE]
>>>
>>>
>>>
>>> As if NTBackup has broken the link to the original full backup.
>>>
>>>
>>>
>>> There used to be a problem with the Volume Shadow Copy Service whereby NTBACKUP would not
>>> manage a backup of SQL Server Full recovery model databases. As in this article here:
>>> http://support.microsoft.com/kb/903643
>>>
>>>
>>>
>>> I noticed in the event log since our upgrade to SP2 of Windows Server 2003 and SQL Server
>>> 2005 we get errors around the time NTBACKUP runs that are like this one:
>>>
>>>
>>>
>>> [QUOTE]
>>>
>>> Event Type: Error
>>>
>>> Event Source: SQLVDI
>>>
>>> Event Category: None
>>>
>>> Event ID: 1
>>>
>>> Date: 29/03/2007
>>>
>>> Time: 07:03:47
>>>
>>> User: N/A
>>>
>>> Computer: SERVERA
>>>
>>> Description:
>>>
>>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release
>>> mutex not owned by caller.. Process=1968. Thread=3564. Client. Instance=. VD=.
>>>
>>>
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>>
>>> [END QUOTE]
>>>
>>>
>>>
>>> The SQL Server maintenance plans at points 1 through to 3 above are not hand crafted
>>> scripts, just output from the Maintenance plan wizard. Furthermore they have been deleted
>>> and recreated since updating to SP2 in case that was the cause but the problem remains.
>>>
>>>
>>>
>>> The only way around this problem has been to amend the NTBACKUP command at point 4 above and
>>> use /SNAP:off so that it doesn't use the Volume Shadow Copy service. I can only draw the
>>> conclusion that the Shadow Copy Service or NTBackup has something to do with this? Has
>>> anybody else encountered a similar problem?
>>>
>>>
>>>
>>> I have been researching this for days but due to the relative brief period since the release
>>> of Service Pack 2 for Windows Server 2003 there isn't really too much about on the web
>>> regarding this. In fact I hadn't even though of it being the NTBACKUP if it hadn't been for
>>> the thread I found here:
>>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>>
>>>
>>>
>>> Any tips / ideas much appreciated.
>>>
>>>
>>>
>>> Kind Regards
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||Btw again. I found some words on this in BOL 2005, searching for VSS, like:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/0f299867-f499-4c2a-ad6f-b2ef1869381d.htm
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
news:OOVKXyhcHHA.984@.TK2MSFTNGP04.phx.gbl...
> NTBACKUP is Microsoft. It's the default backup software in the operating system. I don't think
> talking to them is going to get me anywhere.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:uXTpylhcHHA.2068@.TK2MSFTNGP06.phx.gbl...
>> Unfortunately now you cannot.
>> That sounds horrible to me, to be honest. I'd talk to the guys who wrote this software...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:eP70LihcHHA.1244@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Unfortunately now you cannot. The only way to prevent this is to turn off the command line SNAP
>> option of NTBACKUP with /snap:off however this defeats the object since there are other files
>> (Non-SQL Server) on the drive that I do want to have backed up even though they maybe in use.
>> Regards
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:Od23CWhcHHA.2316@.TK2MSFTNGP04.phx.gbl...
>>I see. SQL Server get confused even if NTBACKUP excludes the database files. Can you configure
>>NTBACKUP to not interface with SQL Server? It seems from the eventlog entry you posted that SQL
>>Server got some VDI call from NTBACKUP. This is probably the one that broke the backup chain.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:ec$Hn8ecHHA.3484@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Some of the databases are quite large and backing them up fully using NTBACKUP with snap:on
>> option is not really an option. The idea is to leave the SQL databases' backups outside of the
>> control of NTBACKUP. This used to work though until application of the Service Packs and now
>> NTBACKUP seems to be breaking that Differential chain. Although I hasten to add, that is the
>> only possible cause I have been able to identify thus far however I accept there could be
>> other causes. Luckily this server doesn't have a basket load of other applications / services
>> that could have any indirect effect on this problem.
>> Kind Regards
>> Nick
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
>> Can you configure NTBACKUP to not grab the SQL Server database files? Just thinking out
>> loud...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>>> Hi All,
>>>
>>>
>>>
>>> We recently upgraded a box running Windows Server 2003 SP1 with SQL Server 2005 SP1 to
>>> Windows Server 2003 SP2 and SQL Server SP2.
>>>
>>>
>>>
>>> For some time we have had the following backup regime for some SQL Server full recovery
>>> model databases that are present on this server:
>>>
>>>
>>>
>>> 1) SQL Server Full backup on a Sunday night at around midnight
>>>
>>> 2) SQL Server Transaction log backups every three hours from 03:00 until 18:00
>>>
>>> 3) SQL Server Differential backups at 21:00 every day except Sunday night.
>>>
>>> 4) NTBACKUP at 22:00 every night to do a differential backup of the server using option
>>> /SNAP:on (Use Volume Shadow Copy) but with the directory containing SQL Server database
>>> files excluded.
>>>
>>> 5) Note the output TRN files and BAK files from points 1 to 4 above are mirrored off to
>>> another server by a 3rd party application, not by using NTBACKUP.
>>>
>>>
>>>
>>> All has worked fine for many months until our upgrade of the server to SP2 of SQL Server and
>>> SP2 of Windows Server 2003.
>>>
>>>
>>>
>>> Immediately after that upgrade we would get the Full backup at point 1 completing as
>>> planned, the transaction log backups at point 2 complete on the Monday, then the
>>> differential SQL backup on Monday night works fine as well followed by the NT Backup at
>>> point 4. The cycle works fine on the Tuesday up to the repeat of the SQL Server differential
>>> backup at point 3 which fails for every database with an error message not unlike this
>>> example:
>>>
>>>
>>>
>>> [QUOTE]
>>>
>>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak' WITH
>>> DIFFERENTIAL , NOFORMAT, NOINIT, NAME = N'dbTPL_backup_20070327200004', SKIP, REWIND,
>>> NOUNLOAD, STATS = 10" failed with the following error: "Cannot perform a differential backup
>>> for database "dbTPL", because a current database backup does not exist. Perform a full
>>> database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option. BACKUP
>>> DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query,
>>> "ResultSet" property not set correctly, parameters not set correctly, or connection not
>>> established correctly.
>>>
>>> [END QUOTE]
>>>
>>>
>>>
>>> As if NTBackup has broken the link to the original full backup.
>>>
>>>
>>>
>>> There used to be a problem with the Volume Shadow Copy Service whereby NTBACKUP would not
>>> manage a backup of SQL Server Full recovery model databases. As in this article here:
>>> http://support.microsoft.com/kb/903643
>>>
>>>
>>>
>>> I noticed in the event log since our upgrade to SP2 of Windows Server 2003 and SQL Server
>>> 2005 we get errors around the time NTBACKUP runs that are like this one:
>>>
>>>
>>>
>>> [QUOTE]
>>>
>>> Event Type: Error
>>>
>>> Event Source: SQLVDI
>>>
>>> Event Category: None
>>>
>>> Event ID: 1
>>>
>>> Date: 29/03/2007
>>>
>>> Time: 07:03:47
>>>
>>> User: N/A
>>>
>>> Computer: SERVERA
>>>
>>> Description:
>>>
>>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release
>>> mutex not owned by caller.. Process=1968. Thread=3564. Client. Instance=. VD=.
>>>
>>>
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>>
>>> [END QUOTE]
>>>
>>>
>>>
>>> The SQL Server maintenance plans at points 1 through to 3 above are not hand crafted
>>> scripts, just output from the Maintenance plan wizard. Furthermore they have been deleted
>>> and recreated since updating to SP2 in case that was the cause but the problem remains.
>>>
>>>
>>>
>>> The only way around this problem has been to amend the NTBACKUP command at point 4 above and
>>> use /SNAP:off so that it doesn't use the Volume Shadow Copy service. I can only draw the
>>> conclusion that the Shadow Copy Service or NTBackup has something to do with this? Has
>>> anybody else encountered a similar problem?
>>>
>>>
>>>
>>> I have been researching this for days but due to the relative brief period since the release
>>> of Service Pack 2 for Windows Server 2003 there isn't really too much about on the web
>>> regarding this. In fact I hadn't even though of it being the NTBACKUP if it hadn't been for
>>> the thread I found here:
>>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>>
>>>
>>>
>>> Any tips / ideas much appreciated.
>>>
>>>
>>>
>>> Kind Regards
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||Hi
Take a look at
http://support.microsoft.com/kb/903643
"NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
> Hi All,
>
> We recently upgraded a box running Windows Server 2003 SP1 with SQL Server
> 2005 SP1 to Windows Server 2003 SP2 and SQL Server SP2.
>
> For some time we have had the following backup regime for some SQL Server
> full recovery model databases that are present on this server:
>
> 1) SQL Server Full backup on a Sunday night at around midnight
> 2) SQL Server Transaction log backups every three hours from 03:00
> until 18:00
> 3) SQL Server Differential backups at 21:00 every day except Sunday
> night.
> 4) NTBACKUP at 22:00 every night to do a differential backup of the
> server using option /SNAP:on (Use Volume Shadow Copy) but with the
> directory containing SQL Server database files excluded.
> 5) Note the output TRN files and BAK files from points 1 to 4 above
> are mirrored off to another server by a 3rd party application, not by
> using NTBACKUP.
>
> All has worked fine for many months until our upgrade of the server to SP2
> of SQL Server and SP2 of Windows Server 2003.
>
> Immediately after that upgrade we would get the Full backup at point 1
> completing as planned, the transaction log backups at point 2 complete on
> the Monday, then the differential SQL backup on Monday night works fine as
> well followed by the NT Backup at point 4. The cycle works fine on the
> Tuesday up to the repeat of the SQL Server differential backup at point 3
> which fails for every database with an error message not unlike this
> example:
>
> [QUOTE]
> Executing the query "BACKUP DATABASE [dbTPL] TO DISK => N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak'
> WITH DIFFERENTIAL , NOFORMAT, NOINIT, NAME => N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD, STATS = 10"
> failed with the following error: "Cannot perform a differential backup for
> database "dbTPL", because a current database backup does not exist.
> Perform a full database backup by reissuing BACKUP DATABASE, omitting the
> WITH DIFFERENTIAL option. BACKUP DATABASE is terminating abnormally.".
> Possible failure reasons: Problems with the query, "ResultSet" property
> not set correctly, parameters not set correctly, or connection not
> established correctly.
> [END QUOTE]
>
> As if NTBackup has broken the link to the original full backup.
>
> There used to be a problem with the Volume Shadow Copy Service whereby
> NTBACKUP would not manage a backup of SQL Server Full recovery model
> databases. As in this article here: http://support.microsoft.com/kb/903643
>
> I noticed in the event log since our upgrade to SP2 of Windows Server 2003
> and SQL Server 2005 we get errors around the time NTBACKUP runs that are
> like this one:
>
> [QUOTE]
> Event Type: Error
> Event Source: SQLVDI
> Event Category: None
> Event ID: 1
> Date: 29/03/2007
> Time: 07:03:47
> User: N/A
> Computer: SERVERA
> Description:
> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
> ErrorCode=(288)Attempt to release mutex not owned by caller..
> Process=1968. Thread=3564. Client. Instance=. VD=.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> [END QUOTE]
>
> The SQL Server maintenance plans at points 1 through to 3 above are not
> hand crafted scripts, just output from the Maintenance plan wizard.
> Furthermore they have been deleted and recreated since updating to SP2 in
> case that was the cause but the problem remains.
>
> The only way around this problem has been to amend the NTBACKUP command at
> point 4 above and use /SNAP:off so that it doesn't use the Volume Shadow
> Copy service. I can only draw the conclusion that the Shadow Copy Service
> or NTBackup has something to do with this? Has anybody else encountered a
> similar problem?
>
> I have been researching this for days but due to the relative brief period
> since the release of Service Pack 2 for Windows Server 2003 there isn't
> really too much about on the web regarding this. In fact I hadn't even
> though of it being the NTBACKUP if it hadn't been for the thread I found
> here:
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>
> Any tips / ideas much appreciated.
>
> Kind Regards
>
>
>|||Hi all of u, unluckly i am also facing this problem since last month :(.
very horrible thisng this is. I have all of senerio that is dececribed in
this thread I got out from some of articles that that it is due toinserting
LSN number by ntBackup utility in sql server database msdb (from where we can
get all of LSN number).
Wheneever our diff backup job attempt to take backup then its found latest
LSN number (because it takes backup since last full backup, ntbackup writes
LSN for full backup and file over which backup was take unreachable due to
its ntbackup file structure :( ) and al last diff fail because it could not
get last backup.
its prooof is this that u just took full backup and just run diff job u
could get success.
SNAP :OFF option never works even i start/off its serveice too.
"Uri Dimant" wrote:
> Hi
> Take a look at
> http://support.microsoft.com/kb/903643
>
> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
> > Hi All,
> >
> >
> >
> > We recently upgraded a box running Windows Server 2003 SP1 with SQL Server
> > 2005 SP1 to Windows Server 2003 SP2 and SQL Server SP2.
> >
> >
> >
> > For some time we have had the following backup regime for some SQL Server
> > full recovery model databases that are present on this server:
> >
> >
> >
> > 1) SQL Server Full backup on a Sunday night at around midnight
> >
> > 2) SQL Server Transaction log backups every three hours from 03:00
> > until 18:00
> >
> > 3) SQL Server Differential backups at 21:00 every day except Sunday
> > night.
> >
> > 4) NTBACKUP at 22:00 every night to do a differential backup of the
> > server using option /SNAP:on (Use Volume Shadow Copy) but with the
> > directory containing SQL Server database files excluded.
> >
> > 5) Note the output TRN files and BAK files from points 1 to 4 above
> > are mirrored off to another server by a 3rd party application, not by
> > using NTBACKUP.
> >
> >
> >
> > All has worked fine for many months until our upgrade of the server to SP2
> > of SQL Server and SP2 of Windows Server 2003.
> >
> >
> >
> > Immediately after that upgrade we would get the Full backup at point 1
> > completing as planned, the transaction log backups at point 2 complete on
> > the Monday, then the differential SQL backup on Monday night works fine as
> > well followed by the NT Backup at point 4. The cycle works fine on the
> > Tuesday up to the repeat of the SQL Server differential backup at point 3
> > which fails for every database with an error message not unlike this
> > example:
> >
> >
> >
> > [QUOTE]
> >
> > Executing the query "BACKUP DATABASE [dbTPL] TO DISK => > N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak'
> > WITH DIFFERENTIAL , NOFORMAT, NOINIT, NAME => > N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD, STATS = 10"
> > failed with the following error: "Cannot perform a differential backup for
> > database "dbTPL", because a current database backup does not exist.
> > Perform a full database backup by reissuing BACKUP DATABASE, omitting the
> > WITH DIFFERENTIAL option. BACKUP DATABASE is terminating abnormally.".
> > Possible failure reasons: Problems with the query, "ResultSet" property
> > not set correctly, parameters not set correctly, or connection not
> > established correctly.
> >
> > [END QUOTE]
> >
> >
> >
> > As if NTBackup has broken the link to the original full backup.
> >
> >
> >
> > There used to be a problem with the Volume Shadow Copy Service whereby
> > NTBACKUP would not manage a backup of SQL Server Full recovery model
> > databases. As in this article here: http://support.microsoft.com/kb/903643
> >
> >
> >
> > I noticed in the event log since our upgrade to SP2 of Windows Server 2003
> > and SQL Server 2005 we get errors around the time NTBACKUP runs that are
> > like this one:
> >
> >
> >
> > [QUOTE]
> >
> > Event Type: Error
> >
> > Event Source: SQLVDI
> >
> > Event Category: None
> >
> > Event ID: 1
> >
> > Date: 29/03/2007
> >
> > Time: 07:03:47
> >
> > User: N/A
> >
> > Computer: SERVERA
> >
> > Description:
> >
> > SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
> > ErrorCode=(288)Attempt to release mutex not owned by caller..
> > Process=1968. Thread=3564. Client. Instance=. VD=.
> >
> >
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> > [END QUOTE]
> >
> >
> >
> > The SQL Server maintenance plans at points 1 through to 3 above are not
> > hand crafted scripts, just output from the Maintenance plan wizard.
> > Furthermore they have been deleted and recreated since updating to SP2 in
> > case that was the cause but the problem remains.
> >
> >
> >
> > The only way around this problem has been to amend the NTBACKUP command at
> > point 4 above and use /SNAP:off so that it doesn't use the Volume Shadow
> > Copy service. I can only draw the conclusion that the Shadow Copy Service
> > or NTBackup has something to do with this? Has anybody else encountered a
> > similar problem?
> >
> >
> >
> > I have been researching this for days but due to the relative brief period
> > since the release of Service Pack 2 for Windows Server 2003 there isn't
> > really too much about on the web regarding this. In fact I hadn't even
> > though of it being the NTBACKUP if it hadn't been for the thread I found
> > here:
> > http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
> >
> >
> >
> > Any tips / ideas much appreciated.
> >
> >
> >
> > Kind Regards
> >
> >
> >
> >
> >
> >
>
>|||Found the solution and many thanks to those that contributed to this thread.
I thought I should post my findings back here for anybody else. The first
weird thing was that I found contributions to this thread on other sites
that weren't in my download of the newsgroup from msnews. Ho hum. Anyway,
back to the findings.
I couldn't understand why all of a sudden I was getting broken differential
chains when NT BACKUP was run using volume shadow copy service after
upgrading the servers to SP2 of SQL Server 2005 and SP2 of Windows Server
2003. As in this KB http://support.microsoft.com/kb/903643. I hadn't had
this problem until this upgrade.
Here's the reason:
The "Readme for Microsoft SQL Server 2005 Service Pack 2" at
http://download.microsoft.com/download/2/b/5/2b5e5d37-9b17-423d-bc8f-b11ecd4195b4/ReadmeSQL2005SP2.htm
states:
[Quote]
3.2.6 SQL Server 2005 SP2 Changes the SQL Writer Service Default Startup
Type and Default State
Note the following changes to the SQL Writer service default startup type
and default state:
The SQL Writer service startup type is changed from Manual to Automatic.
The SQL Writer service default state is changed from Stopped to Started.
[END QUOTE]
So I changed it back to manual and stopped the service. This of course
behaved as expected, the VSS didn't try to lock my Full recovery model
databases and break the differential chain. I can still allow /volsnap:on
option with my NTBACKUP commands to backup all the other "open" files on the
volume without breaking the database differential chain.
The thing that started me looking into this was this line in the BOL article
that Tibor mentioned.
[QUOTE]
This SQL Writer Service is automatically installed but not enabled by
default. It must be explicitly enabled to run on the server machine and must
be running at the time that the Volume Shadow Copy Service (VSS) application
requests a backup or restore. Use the Microsoft Windows Services applet to
configure the service. The SQL Writer Service installs on all operating
systems but is only needed on server systems. For Microsoft Windows XP, use
the MSDE Writer.
[END QUOTE]
Hope the above helps somebody else out and once again, thanks to those that
contributed.
Regards
Nick
"NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
news:OOVKXyhcHHA.984@.TK2MSFTNGP04.phx.gbl...
> NTBACKUP is Microsoft. It's the default backup software in the operating
> system. I don't think talking to them is going to get me anywhere.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:uXTpylhcHHA.2068@.TK2MSFTNGP06.phx.gbl...
>> Unfortunately now you cannot.
>> That sounds horrible to me, to be honest. I'd talk to the guys who wrote
>> this software...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:eP70LihcHHA.1244@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Unfortunately now you cannot. The only way to prevent this is to turn
>> off the command line SNAP option of NTBACKUP with /snap:off however this
>> defeats the object since there are other files (Non-SQL Server) on the
>> drive that I do want to have backed up even though they maybe in use.
>> Regards
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:Od23CWhcHHA.2316@.TK2MSFTNGP04.phx.gbl...
>>I see. SQL Server get confused even if NTBACKUP excludes the database
>>files. Can you configure NTBACKUP to not interface with SQL Server? It
>>seems from the eventlog entry you posted that SQL Server got some VDI
>>call from NTBACKUP. This is probably the one that broke the backup
>>chain.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:ec$Hn8ecHHA.3484@.TK2MSFTNGP04.phx.gbl...
>> Hi Tibor,
>> Some of the databases are quite large and backing them up fully using
>> NTBACKUP with snap:on option is not really an option. The idea is to
>> leave the SQL databases' backups outside of the control of NTBACKUP.
>> This used to work though until application of the Service Packs and
>> now NTBACKUP seems to be breaking that Differential chain. Although I
>> hasten to add, that is the only possible cause I have been able to
>> identify thus far however I accept there could be other causes.
>> Luckily this server doesn't have a basket load of other applications /
>> services that could have any indirect effect on this problem.
>> Kind Regards
>> Nick
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
>> wrote in message news:%239h7jwecHHA.4352@.TK2MSFTNGP03.phx.gbl...
>> Can you configure NTBACKUP to not grab the SQL Server database files?
>> Just thinking out loud...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "NGD66" <ngd66no-spam@.hotmailno-spam.co.uk> wrote in message
>> news:uR0BrQecHHA.1312@.TK2MSFTNGP06.phx.gbl...
>>> Hi All,
>>>
>>>
>>>
>>> We recently upgraded a box running Windows Server 2003 SP1 with SQL
>>> Server 2005 SP1 to Windows Server 2003 SP2 and SQL Server SP2.
>>>
>>>
>>>
>>> For some time we have had the following backup regime for some SQL
>>> Server full recovery model databases that are present on this
>>> server:
>>>
>>>
>>>
>>> 1) SQL Server Full backup on a Sunday night at around midnight
>>>
>>> 2) SQL Server Transaction log backups every three hours from
>>> 03:00 until 18:00
>>>
>>> 3) SQL Server Differential backups at 21:00 every day except
>>> Sunday night.
>>>
>>> 4) NTBACKUP at 22:00 every night to do a differential backup of
>>> the server using option /SNAP:on (Use Volume Shadow Copy) but with
>>> the directory containing SQL Server database files excluded.
>>>
>>> 5) Note the output TRN files and BAK files from points 1 to 4
>>> above are mirrored off to another server by a 3rd party application,
>>> not by using NTBACKUP.
>>>
>>>
>>>
>>> All has worked fine for many months until our upgrade of the server
>>> to SP2 of SQL Server and SP2 of Windows Server 2003.
>>>
>>>
>>>
>>> Immediately after that upgrade we would get the Full backup at point
>>> 1 completing as planned, the transaction log backups at point 2
>>> complete on the Monday, then the differential SQL backup on Monday
>>> night works fine as well followed by the NT Backup at point 4. The
>>> cycle works fine on the Tuesday up to the repeat of the SQL Server
>>> differential backup at point 3 which fails for every database with
>>> an error message not unlike this example:
>>>
>>>
>>>
>>> [QUOTE]
>>>
>>> Executing the query "BACKUP DATABASE [dbTPL] TO DISK =>>> N'D:\\NoBackup\\SQLBackup\\UserDBs\\Diff\\dbTPL\\dbTPL_backup_200703272000.bak'
>>> WITH DIFFERENTIAL , NOFORMAT, NOINIT, NAME =>>> N'dbTPL_backup_20070327200004', SKIP, REWIND, NOUNLOAD, STATS = 10"
>>> failed with the following error: "Cannot perform a differential
>>> backup for database "dbTPL", because a current database backup does
>>> not exist. Perform a full database backup by reissuing BACKUP
>>> DATABASE, omitting the WITH DIFFERENTIAL option. BACKUP DATABASE is
>>> terminating abnormally.". Possible failure reasons: Problems with
>>> the query, "ResultSet" property not set correctly, parameters not
>>> set correctly, or connection not established correctly.
>>>
>>> [END QUOTE]
>>>
>>>
>>>
>>> As if NTBackup has broken the link to the original full backup.
>>>
>>>
>>>
>>> There used to be a problem with the Volume Shadow Copy Service
>>> whereby NTBACKUP would not manage a backup of SQL Server Full
>>> recovery model databases. As in this article here:
>>> http://support.microsoft.com/kb/903643
>>>
>>>
>>>
>>> I noticed in the event log since our upgrade to SP2 of Windows
>>> Server 2003 and SQL Server 2005 we get errors around the time
>>> NTBACKUP runs that are like this one:
>>>
>>>
>>>
>>> [QUOTE]
>>>
>>> Event Type: Error
>>>
>>> Event Source: SQLVDI
>>>
>>> Event Category: None
>>>
>>> Event ID: 1
>>>
>>> Date: 29/03/2007
>>>
>>> Time: 07:03:47
>>>
>>> User: N/A
>>>
>>> Computer: SERVERA
>>>
>>> Description:
>>>
>>> SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
>>> ErrorCode=(288)Attempt to release mutex not owned by caller..
>>> Process=1968. Thread=3564. Client. Instance=. VD=.
>>>
>>>
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>>
>>> [END QUOTE]
>>>
>>>
>>>
>>> The SQL Server maintenance plans at points 1 through to 3 above are
>>> not hand crafted scripts, just output from the Maintenance plan
>>> wizard. Furthermore they have been deleted and recreated since
>>> updating to SP2 in case that was the cause but the problem remains.
>>>
>>>
>>>
>>> The only way around this problem has been to amend the NTBACKUP
>>> command at point 4 above and use /SNAP:off so that it doesn't use
>>> the Volume Shadow Copy service. I can only draw the conclusion that
>>> the Shadow Copy Service or NTBackup has something to do with this?
>>> Has anybody else encountered a similar problem?
>>>
>>>
>>>
>>> I have been researching this for days but due to the relative brief
>>> period since the release of Service Pack 2 for Windows Server 2003
>>> there isn't really too much about on the web regarding this. In fact
>>> I hadn't even though of it being the NTBACKUP if it hadn't been for
>>> the thread I found here:
>>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1293496&SiteID=1
>>>
>>>
>>>
>>> Any tips / ideas much appreciated.
>>>
>>>
>>>
>>> Kind Regards
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>

Wednesday, March 28, 2012

Is There a Quick Way to Get a Total Match Count (estimate is OK) of a SQL FullText Query?

Monday, March 26, 2012

Is there a Cluster command line I can run which will stop my "SQL Agent Service"?

Is there a Cluster command line I can run which will stop my "SQL Agent Service"?

Wednesday, March 21, 2012

Is the Certificate based authentication the only way ?

Monday, March 19, 2012

is sqlserver 2000 compatible with windows 2003 ?

Is SQL Server Windows Authentication mode more secure than SQL Server "Mixed Mode" mode?

Is SQL Server Windows Authentication mode more secure than SQL Server "Mixed Mode" mode?

Monday, March 12, 2012

Is SQL Server Service Manager still existing on SQL Express Edition?

is sql server 2005 a standalone install? Or do you have to install windows server

Friday, March 9, 2012

is sql 7.0 scheduled to be retired

Is SQL 2005 memory limitation <= OS memory limitation?

Is SQL 2005 failover cluster supported on Windows 2008 clusters?

Is SQL 2000 clustering cr*p??

Is SQL 2000 better than 7?

Is SQL 2000 better than 7?

Is SQL 2000 32 bit supported

Is server downgrade possible?

Is server downgrade possible?

Wednesday, March 7, 2012

Is Reporting Services Suppot to take the RDL Report Objects in Windows Form

Monday, February 20, 2012

Is NTBACKUP breaking SQL Server 2005 differential backup chain..again?

table hosed

Blog Archive

About Me