great trek def

Corrections

What was the Great Trek?

The Great Trek was a perilous exodus of pioneers into the heart of South Africa, looking for a place to call home.

When the British took control of Cape Town and the Cape Colony in the early 1800s, tensions grew between the new colonizers of British stock, and the old colonizers, the Boers, descendants of the original Dutch settlers. From 1835, the Boers would lead numerous expeditions out of the Cape Colony, traversing towards the interior of South Africa. Escaping British rule would come with a host of deadly challenges, and the Boers, seeking their own lands, would find themselves in direct conflict with the people who resided in the interior, most notably the Ndebele and the Zulu.

The “Great Trek” is a story of resentment, displacement, murder, war, and hope, and it forms one of the bloodiest chapters of South Africa’s notoriously violent history.

Origins of the Great Trek

great trek gouache paper james edwin mcconnell

The Cape was first colonized by the Dutch , when they landed there in 1652, and Cape Town quickly grew into a vital refueling station between Europe and the East Indies. The colony prospered and grew, with Dutch settlers taking up both urban and rural posts. In 1795, Britain invaded and took control of the Cape Colony, as it was Dutch possession, and Holland was under the control of the French Revolutionary government . After the war, the colony was handed back to Holland (the Batavian Republic) which in 1806, fell under French rule again. The British responded by annexing the Cape completely.

Under British rule, the colony underwent major administrative changes. The language of administration became English, and liberal changes were made which designated non-white servants as citizens. Britain, at the time, was adamantly anti-slavery, and was enacting laws to end it.

Get the latest articles delivered to your inbox

Please check your inbox to activate your subscription.

Tensions grew between the British and the Boers (farmers). In 1815, a Boer was arrested for assaulting one of his servants. Many other Boers rose up in rebellion in solidarity, culminating in five being hanged for insurrection. In 1834, legislation passed that all slaves were to be freed. The vast majority of Boer farmers owned slaves, and although they were offered compensation, travel to Britain was required to receive it which was impossible for many. Eventually, the Boers had had enough of British rule and decided to leave the Cape Colony in search of self-governance and new lands to farm. The Great Trek was about to begin.

The Trek Begins

Not all Afrikaners endorsed the Great Trek. In fact, only a fifth of the Cape’s Dutch-speaking people decided to take part. Most of the urbanized Dutch were actually content with British rule. Nevertheless, many Boers decided to leave. Thousands of Boers loaded up their wagons and proceeded to venture into the interior and towards peril.

The first wave of voortrekkers (pioneers) met with disaster. After setting out in September 1835, they crossed the Vaal River in January, 1836, and decided to split up, following differences between their leaders. Hans van Rensburg led a party of 49 settlers who trekked north into what is now Mozambique. His party was slain by an impi (force of warriors) of Soshangane. For van Rensburg and his party, the Great Trek was over. Only two children survived who were saved by a Zulu warrior. The other party of settlers, led by Louis Tregardt, settled near Delagoa Bay in southern Mozambique, where most of them perished from fever.

A third group led by Hendrik Potgieter, consisting of about 200 people, also ran into serious trouble. In August 1836, a Matabele patrol attacked Potgieter’s group, killing six men, two women, and six children. King Mzilikazi of the Matabele in what is now Zimbabwe decided to attack the Voortrekkers again, this time sending out an impi of 5,000 men. Local bushmen warned the Voortrekkers of the impi , and Potgieter had two days to prepare. He decided to prepare for battle, although doing so would leave all the Voortrekker’s cattle vulnerable.

The Voortrekkers arranged the wagons into a laager (defensive circle) and placed thorn branches underneath the wagons and in the gaps. Another defensive square of four wagons was placed inside the laager and covered with animal skins. Here, the women and children would be safe from spears thrown into the camp. The defenders numbered just 33 men and seven boys, each armed with two muzzle-loader rifles. They were outnumbered 150 to one.

As the battle commenced, the Voortrekkers rode out on horseback to harry the impi . This proved largely ineffective, and they withdrew to the laager. The attack on the laager only lasted for about half an hour, in which time, two Voortrekkers lost their lives, and about 400 Matabele warriors were killed or wounded. The Matabele were far more interested in taking the cattle and eventually made off with 50,000 sheep and goats and 5,000 cattle. Despite surviving through the day, the Battle of Vegkop was not a happy victory for the Voortrekkers. Three months later, with the help of the Tswana people, a Voortrekker-led raid managed to take back 6,500 cattle, which included some of the cattle plundered at Vegkop.

The following months saw revenge attacks led by the Voortrekkers. About 15 Matabele settlements were destroyed, and 1,000 warriors lost their lives. The Matabele abandoned the region. The Great Trek would continue with several other parties pioneering the way into the South African hinterland.

The Battle of Blood River

In February 1838, the Voortrekkers led by Piet Retief met with absolute disaster. Retief and his delegation were invited to the Zulu King Dingane ’s kraal (village) to negotiate a land treaty; however, Dingane betrayed the Voortrekkers. He had them all taken out to a hill outside the village and clubbed to death. Piet Retief was killed last so that he could watch his delegation being killed. In total, about 100 were murdered, and their bodies were left for the vultures and other scavengers.

Following this betrayal, King Dingane directed further attacks on unsuspecting Voortrekker settlements. This included the Weenen Massacre, in which 534 men, women, and children were slaughtered. This number includes KhoiKhoi and Basuto tribe members who accompanied them. Against a hostile Zulu nation, the Great Trek was doomed to fail.

The Voortrekkers decided to lead a punitive expedition, and under the guidance of Andries Pretorius, 464 men, along with 200 servants and two small cannons, prepared to engage the Zulu. After several weeks of trekking, Pretorius set up his laager along the Ncome River, purposefully avoiding geographic traps that would have led to a disaster in battle. His site offered protection on two sides by the Ncome River to the rear and a deep ditch on the left flank. The approach was treeless and offered no protection from any advancing attackers. On the morning of December 16, the Voortrekkers were greeted by the sight of six regiments of Zulu impis , numbering approximately 20,000 men.

For two hours, the Zulus attacked the laager in four waves, and each time they were repulsed with great casualties. The Voortrekkers used grapeshot in their muskets and their two cannons in order to maximize damage to the Zulus. After two hours, Pretorius ordered his men to ride out and attempt to break up the Zulu formations. The Zulus held for a while, but high casualties eventually forced them to scatter. With their army breaking, the Voortrekkers chased down and killed the fleeing Zulus for three hours. By the end of the battle, 3,000 Zulu lay dead (although historians dispute this number). By contrast, the Voortrekkers suffered only three injuries, including Andries Pretorius taking an assegai (Zulu spear) to the hand.

December 16 has been observed as a public holiday in the Boer Republics and South Africa ever since. It was known as The Day of the Covenant, The Day of the Vow, or Dingane’s Day. In 1995, after the fall of apartheid , the day was rebranded as “Day of Reconciliation.” Today the site on the west side of the Ncome River is home to the Blood River Monument and Museum Complex, while on the east side of the river stands the Ncome River Monument and Museum Complex dedicated to the Zulu people. The former has gone through many variations, with the latest version of the monument being 64 wagons cast in bronze. When it was unveiled in 1998, The then Minister of Home Affairs and Zulu tribal leader, Mangosuthu Buthelezi , apologized on behalf of the Zulu people for the murder of Piet Retief and his party during the Great Trek, while he also stressed the suffering of Zulus during apartheid.

The Zulu defeat added to further divisions in the Zulu Kingdom, which was plunged into a civil war between Dingane and his brother Mpande. Mpande, supported by the Voortrekkers, won the civil war in January 1840. This led to a significant decrease in threats to the Voortrekkers. Andries Pretorius and his Voortrekkers were able to recover Piet Retief’s body, along with his retinue, and give them burials. On Retief’s body was found the original treaty offering the trekkers land, and Pretorius was able to successfully negotiate with the Zulu over the establishment of a territory for the Voortrekkers. The Republic of Natalia was established in 1839, south of the Zulu Kingdom. However, the new republic was short-lived and was annexed by the British in 1843.

Nevertheless, the Great Trek could continue, and thus the waves of Voortrekkers continued. In the 1850s, two substantial Boer republics were established: The Republic of the Transvaal and the Republic of the Orange Free State . These republics would later come into conflict with the expanding British Empire.

The Great Trek as a Cultural Symbol

In the 1940s, Afrikaner nationalists used the Great Trek as a symbol to unite the Afrikaans people and promote cultural unity among them. This move was primarily responsible for the National Party winning the 1948 election and, later on, imposing apartheid on the country.

South Africa is a highly diverse country, and while the Great Trek remains a symbol of Afrikaner culture and history, it is also seen as an important part of South African history with lessons to learn from for all South Africans.

6 Crazy Facts about Cape Town

By Greg Beyer BA History & Linguistics, Journalism Diploma Greg specializes in African History. He holds a BA in History & Linguistics and a Journalism Diploma from the University of Cape Town. A former English teacher, he now excels in academic writing and pursues his passion for art through drawing and painting in his free time.

Frequently Read Together

British History: The Formation of Great Britain and the United Kingdom

The French Revolution in 5 Iconic Paintings

Mandela & the 1995 Rugby World Cup: A Match that Redefined a Nation

Subscriber Services
For Authors
Publications
Archaeology
Art & Architecture
Bilingual dictionaries
Classical studies
Encyclopedias
English Dictionaries and Thesauri
Language reference
Linguistics
Media studies
Medicine and health
Names studies
Performing arts
Science and technology
Social sciences
Society and culture
Overview Pages
Subject Reference
English Dictionaries
Bilingual Dictionaries

Quick Reference

The movement northwards in the 1830s by Boers to escape from British administration in the Cape Colony. From 1835 onwards parties of Voortrekkers reached Natal, where in 1837 Zulu resistance provoked them to kill some 3,000 Zulus at the Battle of Blood River in revenge for the death of their leader, Piet Retief. Natal became a British colony in 1843 and migration continued northwards into the Orange River country and the Transvaal.

From: Great Trek, the in A Dictionary of World History »

Subjects: History

Definition of trek

(Entry 1 of 2)

intransitive verb

Definition of trek (Entry 2 of 2)

peregrinate
peregrination

Examples of trek in a Sentence

These examples are programmatically compiled from various online sources to illustrate current usage of the word 'trek.' Any opinions expressed in the examples do not represent those of Merriam-Webster or its editors. Send us feedback about these examples.

Word History

Afrikaans, from Dutch trecken to pull, haul, migrate; akin to Old High German trechan to pull

Afrikaans, from Dutch treck pull, haul, from trecken

1835, in the meaning defined at sense 2

1849, in the meaning defined at sense 2

Dictionary Entries Near trek

Treitz's muscle

Cite this Entry

“Trek.” Merriam-Webster.com Dictionary , Merriam-Webster, https://www.merriam-webster.com/dictionary/trek. Accessed 26 Apr. 2024.

Kids Definition

Kids definition of trek.

Kids Definition of trek (Entry 2 of 2)

from Afrikaans trek, "to travel by ox wagon," from Dutch trecken "to haul, pull"

More from Merriam-Webster on trek

Nglish: Translation of trek for Spanish Speakers

Britannica English: Translation of trek for Arabic Speakers

Subscribe to America's largest dictionary and get thousands more definitions and advanced search—ad free!

Play Quordle: Guess all four words in a limited number of tries. Each of your guesses must be a real 5-letter word.

Can you solve 4 words at once?

Word of the day.

See Definitions and Examples »

Get Word of the Day daily email!

Popular in Grammar & Usage

More commonly misspelled words, commonly misspelled words, how to use em dashes (—), en dashes (–) , and hyphens (-), absent letters that are heard anyway, how to use accents and diacritical marks, popular in wordplay, 9 superb owl words, 'gaslighting,' 'woke,' 'democracy,' and other top lookups, 10 words for lesser-known games and sports, your favorite band is in the dictionary, etymologies for every day of the week, games & quizzes.

Play Blossom: Solve today's spelling word game by finding as many words as you can using just 7 letters. Longer words score more points.

Exploratory treks to Natal

Conflict with the matebele, conflict with the zulu, centenary celebrations, further reading.

The Great Trek led directly to the founding of several autonomous Boer republics , namely the South African Republic (also known simply as the Transvaal ), the Orange Free State , and the Natalia Republic . [5] It also led to conflicts that resulted in the displacement of the Northern Ndebele people , [6] and conflicts with the Zulu people that contributed to the decline and eventual collapse of the Zulu Kingdom . [3]

Before the arrival of Europeans, the Cape of Good Hope area was populated by Khoisan tribes [7] The first Europeans settled in the Cape area under the auspices of the Dutch East India Company (also known by its Dutch initials VOC ), which established a victualling station there in 1652 to provide its outward bound fleets with fresh provisions and a harbour of refuge during the long sea journey from Europe to Asia. [8] In a few short decades, the Cape had become home to a large population of "vrijlieden" , also denoted as "vrijburgers" (free citizens), former Company employees who remained in Dutch territories overseas after completing their contracts. [9] Since the primary purpose of the Cape settlement at the time was to stock provisions for passing Dutch ships, the VOC offered grants of farmland to its employees under the condition they would cultivate grain for the Company warehouses, and released them from their contracts to save on their wages. [8] Vrijburgers were granted tax-exempt status for 12 years and loaned all the necessary seeds and farming implements they requested. [10] They were married Dutch citizens, considered "of good character" by the Company, and had to commit to spending at least 20 years on the African continent. [8] Reflecting the multi-national character of the VOC's workforce, some German soldiers and sailors were also considered for vrijburger status as well, [8] and in 1688 the Dutch government sponsored the resettlement of over a hundred French Huguenot refugees at the Cape. [11] As a result, by 1691 over a quarter of the colony's European population was not ethnically Dutch. [12] Nevertheless, there was a degree of cultural assimilation through intermarriage, and the almost universal adoption of the Dutch language. [13] Cleavages were likelier to occur along social and economic lines; broadly speaking, the Cape colonists were delineated into Boers , poor farmers who settled directly on the frontier, and the more affluent, predominantly urbanised Cape Dutch . [14]

Following the Flanders Campaign and the Batavian Revolution in Amsterdam , France assisted in the establishment of a pro-French client state, the Batavian Republic , on Dutch soil. [2] This opened the Cape to French warships. [3] To protect her own prosperous maritime shipping routes, Great Britain occupied the fledgling colony by force until 1803. [2] From 1806 to 1814, the Cape was governed as a British military dependency, whose sole importance to the Royal Navy was its strategic relation to Indian maritime traffic. [2] The British formally assumed permanent administrative control around 1815, as a result of the Treaty of Paris . [2]

At the onset of the British rule, the Cape Colony encompassed 100,000 square miles (260,000 km 2 ) and was populated by about 26,720 people of European descent, a relative majority of whom were of Dutch origin. [2] [12] Just over a quarter were of German ancestry and about one-sixth were descended from French Huguenots, [12] although most had ceased speaking French since about 1750. [13] There were also 30,000 African and Asian slaves owned by the settlers, and about 17,000 indigenous Khoisan . Relations between the settlers – especially the Boers – and the new administration quickly soured. [5] The British authorities were adamantly opposed to the Boers' ownership of slaves and what was perceived as their unduly harsh treatment of the indigenous peoples. [5]

The British government insisted that the Cape finance its own affairs through self-taxation, an approach which was alien to both the Boers and the Dutch merchants in Cape Town. [3] In 1815, the controversial arrest of a white farmer for allegedly assaulting one of his servants resulted in the abortive Slachter's Nek Rebellion . The British retaliated by hanging at least five Boers for insurrection. [2] In 1828, the Cape governor declared that all native inhabitants but slaves were to have the rights of "citizens", in respect of security and property ownership, on parity with the settlers. This had the effect of further alienating the colony's white population. [2] [15] Boer resentment of successive British administrators continued to grow throughout the late 1820s and early 1830s, especially with the official imposition of the English language. [6] This replaced Dutch with English as the language used in the Cape's judicial and political systems, putting the Boers at a disadvantage, as most spoke little or no English. [2] [15]

Britain's alienation of the Boers was particularly amplified by the decision to abolish slavery in all its colonies in 1834. [2] [3] All 35,000 slaves registered with the Cape governor were to be freed and given rights on par with other citizens, although in most cases their masters could retain them as apprentices until 1838. [15] [16] Many Boers, especially those involved with grain and wine production, were dependent on slave labour; for example, 94% of all white farmers in the vicinity of Stellenbosch owned slaves at the time, and the size of their slave holdings correlated greatly to their production output. [16] Compensation was offered by the British government, but payment had to be received in London , and few Boers possessed the funds to make the trip. [3]

Bridling at what they considered an unwarranted intrusion into their way of life, some in the Boer community considered selling their farms and venturing deep into South Africa's unmapped interior to preempt further disputes and live completely independent from British rule. [3] Others, especially trekboers , a class of Boers who pursued semi-nomadic pastoral activities, were frustrated by the apparent unwillingness or inability of the British government to extend the borders of the Cape Colony eastward and provide them with access to more prime pasture and economic opportunities. They resolved to trek beyond the colony's borders on their own. [6]

Although it did nothing to impede the Great Trek, Great Britain viewed the movement with pronounced trepidation. [14] The British government initially suggested that conflict in the far interior of Southern Africa between the migrating Boers and the Bantu peoples they encountered would require an expensive military intervention. [14] However, authorities at the Cape also judged that the human and material cost of pursuing the settlers and attempting to re-impose an unpopular system of governance on those who had deliberately spurned it was not worth the immediate risk. [14] Some officials were concerned for the tribes the Boers were certain to encounter, and whether these tribes would be enslaved or otherwise reduced to a state of penury . [17]

The Great Trek was not universally popular among the settlers either. Around 12,000 of them took part in the migration, about a fifth of the colony's Dutch-speaking white population at the time. [3] [1] The Dutch Reformed Church , to which most of the Boers belonged, explicitly refused to endorse the Great Trek. [3] Despite their hostility towards the British, there were Boers who chose to remain in the Cape of their own accord. [5]

For its part, the distinct Cape Dutch community had accepted British rule; many of its members even considered themselves loyal British subjects with a special affection for English culture. [18] The Cape Dutch were also much more heavily urbanised and therefore less likely to be susceptible to the same rural grievances and considerations as those held by the Boers. [14]

In January 1832, Andrew Smith (an Englishman) and William Berg (a Boer farmer) scouted Natal as a potential colony. On their return to the Cape, Smith waxed very enthusiastic, and the impact of discussions Berg had with the Boers proved crucial. Berg portrayed Natal as a land of exceptional farming quality, well watered, and nearly devoid of inhabitants.

In June 1834, the Boer leaders of Uitenhage and Grahamstown discussed a Kommissietrek ('Commission Trek') to visit Natal and to assess its potential as a new homeland for the Cape Boers who were disenchanted with British rule at the Cape. Petrus Lafras Uys was chosen as trek leader. In early August 1834, Jan Gerritze Bantjes set off with some travellers headed for Grahamstown 220 kilometres (140 mi) away, a three-week journey from Graaff-Reinet . Sometime around late August 1834 Jan Bantjes arrived in Grahamstown, contacted Uys and made his introductions.

In June 1834 at Graaff-Reinet, Jan Gerritze Bantjes heard about the exploratory trek to Port Natal and, encouraged by his father Bernard Louis Bantjes, sent word to Uys of his interest in participating. Bantjes wanted to help re-establish Dutch independence over the Boers and to get away from British law at the Cape. Bantjes was already well known in the area as an educated young man fluent both in spoken and written Dutch and in English. Because of these skills, Uys invited Bantjes to join him. Bantjes's writing skills would prove invaluable in recording events as the journey unfolded.

On 8 September 1834, the Kommissietrek of 40 men and one woman, as well as a retinue of coloured servants, set off from Grahamstown for Natal with 14 wagons. Moving through the Eastern Cape , they were welcomed by the Xhosa who were in dispute with the neighbouring Zulu King Dingane ka Senzangakhona , and they passed unharmed into Natal. They travelled more or less the same route that Smith and Berg had taken two years earlier.

The trek avoided the coastal route, keeping to the flatter inland terrain. The Kommissietrek approached Port Natal from East Griqualand and Ixopo , crossing the upper regions of the Mtamvuna and Umkomazi rivers. Travel was slow due to the rugged terrain, and since it was the summer, the rainy season had swollen many of the rivers to their maximum. Progress required days of scouting to locate the most suitable tracks to negotiate. Eventually, after weeks of extraordinary toil, the small party arrived at Port Natal, crossing the Congela River and weaving their way through the coastal forest into the bay area. They had travelled a distance of about 650 kilometres (400 mi) from Grahamstown. This trip would have taken about 5 to 6 months with their slow moving wagons. The Drakensberg route via Kerkenberg into Natal had not yet been discovered.

They arrived at the sweltering hot bay of Port Natal in February 1835, exhausted after their long journey. There, the trek was soon welcomed with open arms by the few British hunters and ivory traders there such as James Collis, including Reverend Allen Francis Gardiner , an ex-commander of the Royal Navy ship Clinker , who had decided to start a mission station there. After congenial exchanges between the Boers and British sides, the party joined them and invited Dick King to become their guide.

The Boers set up their laager ('wagon fort') camp in the area of the present-day Greyville Racecourse in Durban , chosen because it had suitable grazing for the oxen and horses and was far from the foraging hippos in the bay. Several small streams running off the Berea ridge provided fresh water. Alexander Biggar was also at the bay as a professional elephant-hunter and provided the trekkers with information regarding conditions at Port Natal. Bantjes made notes suggested by Uys, which later formed the basis of his more comprehensive report on the positive aspects of Natal. Bantjes also made rough maps of the bay - although this journal is now missing - showing the potential for a harbour which could supply the Boers in their new homeland.

At Port Natal, Uys sent Dick King, who could speak Zulu, to uMgungundlovu to investigate with King Dingane the possibility of granting them land. When Dick King returned to Port Natal some weeks later, he reported that King Dingane insisted they visit him in person. Johannes Uys , brother of Piet Uys, and a number of comrades with a few wagons travelled toward King Dingane's capital at uMgungundlovu, and after making a laager camp at the mouth of the Mvoti River , they proceeded on horseback, but were halted by a flooded Tugela River and forced to return to the laager .

The Kommissietrek left Port Natal for Grahamstown with a stash of ivory in early June 1835, following more or less the same route back to the Cape, and arrived at Grahamstown in October 1835. On Piet Uys's recommendation, Bantjes set to work on the first draft of the Natalialand Report. Meetings and talks took place in the main church to much approval, and the first sparks of Trek Fever began to take hold. From all the information accumulated at Port Natal, Bantjes drew up the final report on "Natalia or Natal Land" that acted as the catalyst which inspired the Boers at the Cape to set in motion the Great Trek.

The first wave of Voortrekkers lasted from 1835 to 1840, during which an estimated 6,000 people (roughly 20% of the Cape Colony's total population or 10% of the white population in the 1830s) trekked. [17]

The first two parties of Voortrekkers left in September 1835, led by Louis Tregardt and Hans van Rensburg . These two parties crossed the Vaal river at Robert's Drift in January 1836, but in April 1836 the two parties split up, just 110 kilometres (70 mi) from the Zoutpansberg mountains, following differences between Tregardt and van Rensburg. [19]

A party led by Hendrik Potgieter trekked out of the Tarka area in either late 1835 or early 1836, and in September 1836 a party led by Gerrit Maritz began their trek from Graaff-Reinet. There was no clear consensus amongst the trekkers on where they were going to settle, but they all had the goal of settling near an outlet to the sea. [17] : 162, 163

In late July 1836 van Rensburg's entire party of 49, except two children who were saved by a Zulu warrior, were massacred at Inhambane by an impi (a force of warriors) of Manukosi . [20] Those of Tregardt's party that had set up around Soutpansberg moved on to colonise Delagoa Bay , with most of the party, including Tregardt, perishing from fever. [17] : 163

In August 1836, despite pre-existing peace agreements with local black leaders, a Ndebele (Matebele) patrol attacked the Liebenberg family part of Potgieter's party, killing six men, two women and six children. It is thought that their primary aim was to plunder the Voortrekkers' cattle. On 20 October 1836, Potgieter's party was attacked by an army of 4,600 Ndebele warriors at the Battle of Vegkop . Thirty-five armed trekkers repulsed the Ndebele assault on their laager with the loss of two men and almost all the trekkers' cattle. Potgieter, Uys and Maritz mounted two punitive commando raids. The first resulted in the sacking of the Ndebele colony at Mosega , the death of 400 Ndebele, and the taking of 7,000 cattle. The second commando forced Mzilikazi and his followers to flee to what is now modern day Zimbabwe . [17] : 163

By spring 1837, five to six large Voortrekker colonies had been established between the Vaal and Orange Rivers with a total population of around 2,000 trekkers.

In October 1837 Retief met with Zulu King Dingane to negotiate a treaty for land in what is now Kwa-Zulu Natal . King Dingane, suspicious and untrusting because of previous Voortrekker influxes from across the Drakensberg, had Retief and seventy of his followers killed . [17] : 164

Various interpretations of what transpired exist, as only the missionary Francis Owen 's written eye-witness account survived. [21] Retief's written request for land contained veiled threats by referring to the Voortrekker's defeat of indigenous groups encountered along their journey. The Voortrekker demand for a written contract guaranteeing private property ownership was incompatible with the contemporaneous Zulu oral culture which prescribed that a chief could only temporarily dispense land as it was communally owned. [22]

Most versions agree that the following happened: King Dingane's authority extended over some of the land in which the Boers wanted to settle. As prerequisite to granting the Voortrekker request, he demanded that the Voortrekkers return some cattle stolen by Sekonyela , a rival chief. After the Boers retrieved the cattle, King Dingane invited Retief to his residence at uMgungundlovu to finalise the treaty, having either planned the massacre in advance, or deciding to do so after Retief and his men arrived.

King Dingane's reputed instruction to his warriors, " Bulalani abathakathi! " (Zulu for "kill the wizards") may indicate that he considered the Boers to wield evil supernatural powers. After killing Retief's delegation, a Zulu army of 7,000 impis were sent out and immediately attacked Voortrekker encampments in the Drakensberg foothills at what later was called Blaauwkrans and Weenen , leading to the Weenen massacre in which 532 people were killed, including 282 Voortrekkers, of whom 185 were children, and 250 Khoikhoi and Basuto accompanying them. [23] In contrast to earlier conflicts with the Xhosa on the eastern Cape frontier, the Zulus killed women and children along with men, wiping out half of the Natal contingent of Voortrekkers.

The Voortrekkers retaliated with a 347-strong punitive raid against the Zulu (later known as the Flight Commando), supported by new arrivals from the Orange Free State . The Voortrekkers were roundly defeated by about 7,000 warriors at Ithaleni , southwest of uMgungundlovu. The well-known reluctance of Afrikaner leaders to submit to one another's leadership, which later hindered sustained success in the Anglo-Boer Wars , was largely to blame.

In November 1838 Andries Pretorius arrived with a commando of 60 armed trekkers and two cannon to assist in the defence. A few days later on 16 December 1838, a force of 468 trekkers, 3 Britons , and 60 black allies fought against 10,000 to 12,000 Zulu impis at the Battle of Blood River . Pretorius's victory over the Zulu army led to a civil war within the Zulu nation as King Dingane's half-brother, Mpande kaSenzangakhona , aligned with the Voortrekkers to overthrow the king and impose himself. Mpande sent 10,000 impis to assist the trekkers in follow-up expeditions against Dingane. [17] : 164

After the defeat of the Zulu forces and the recovery of the treaty between Dingane and Retief from Retief's body, the Voortrekkers proclaimed the Natalia Republic . [24] After Dingane's death, Mpande was proclaimed king, and the Zulu nation allied with the short-lived Natalia Republic until its annexation by the British Empire in 1843. [17] : 164 [25]

The Voortrekkers' guns offered them a technological advantage over the Zulu's traditional weaponry of short stabbing spears, fighting sticks, and cattle-hide shields. The Boers attributed their victory to a vow they made to God before the battle: if victorious, they and future generations would commemorate the day as a Sabbath . Thereafter, 16 December was celebrated by Boers as a public holiday, first called Dingane's Day, later changed to the Day of the Vow . Post-apartheid , the name was changed to the Day of Reconciliation by the South African government, in order to foster reconciliation between all South Africans. [25]

Conflict amongst the Voortrekkers was a problem because the trek levelled out the pre-existing class hierarchy which had previously enforced discipline, and thus social cohesion broke down. Instead the trek leaders became more reliant on patriarchal family structure and military reputation to maintain control over their parties. This had a large and lasting impact on Afrikaans culture and society. [17] : 163

The celebration of the Great Trek in the 1930s played a major role in the growth of Afrikaans nationalism . It is thought that the experiences of the Second Boer War and the following period, between 1906 and 1934, of a lack of public discussion about the war within the Afrikaans community helped set the scene for a large increase in interest in Afrikaans national identity. The celebration of the centenary of the Great Trek along with a new generation of Afrikaners interested in learning about the Afrikaans experiences of the Boer War catalysed a surge of Afrikaans nationalism. [17] : 433

The centenary celebrations began with a re-enactment of the trek beginning on 8 August 1938 with nine ox wagons at the statue of Jan van Riebeeck in Cape Town and ended at the newly completed Voortrekker Monument in Pretoria and attended by over 100,000 people. A second re-enactment trek starting at the same time and place ended at the scene of the Battle of Blood River. [17] : 432

The commemoration sparked mass enthusiasm amongst Afrikaners as the re-enactment trek passed through the small towns and cities of South Africa. Both participants and spectators participated by dressing in Voortrekker clothing, renaming streets, holding ceremonies, erecting monuments, and laying wreaths at the graves of Afrikaner heroes. Cooking meals over an open fire in the same way the Voortrekkers did became fashionable amongst urbanites, giving birth to the South African tradition of braaing . [17] : 432 An Afrikaans language epic called Building a Nation ( Die Bou van 'n Nasie ) was made in 1938 to coincide with the 100th anniversary of the Great Trek. [26] The film tells the Afrikaans version of the history of South Africa from 1652 to 1910 with a focus on the Great Trek. [27]

A number of Afrikaans organisations such as the Afrikaner Broederbond and Afrikaanse Taal en Kultuurvereniging continued to promote the centenary's goals of furthering the Afrikaner cause and entrenching a greater sense of unity and solidarity within the community well into the 20th century. [17] : 432 [28]

Political impact

The Great Trek was used by Afrikaner nationalists as a core symbol of a common Afrikaans history. It was used to promote the idea of an Afrikaans nation and a narrative that promoted the ideals of the National Party . In 1938, celebrations of the centenary of the Battle of Blood River and the Great Trek mobilised behind an Afrikaans nationalist theses. The narrative of Afrikaner nationalism was a significant reason for the National Party's victory in the 1948 elections . A year later the Voortrekker Monument was completed and opened in Pretoria by the newly elected South African Prime Minister and National Party member Daniel Malan in 1949.

A few years later, " Die Stem van Suid-Afrika " ('The Voice of South Africa'), a poem written by Cornelis Jacobus Langenhoven referring to the Great Trek, was chosen to be the words of the pre-1994 South African national anthem. The post-1997 national anthem of South Africa incorporates a section of " Die Stem van Suid-Afrika " but it was decided to omit the section in "reference to the Great Trek (' met die kreun van ossewa '), since this was the experience of only one section of our community". [29] When apartheid in South Africa ended and the country transitioned to majority rule, President F. W. de Klerk invoked the measures as a new Great Trek. [30]

H. Rider Haggard , Swallow (1899) and Marie (1912)
Stuart Cloete , Turning Wheels (1937)
Helga Moray, Untamed (1950) - a 1955 movie of the same name is based on this book.
James A. Michener , The Covenant (1980)
Robin Binckes, Canvas under the Sky (2011) ISBN 1920143637 - a controversial novel about a promiscuous drug-using Voortrekker set during the Great Trek. [31]
Jeanette Ferreira
F.A. Venter ,
C. W. H. Van der Post, Piet Uijs, of lijden en strijd der voortrekkers in Natal , novel, 1918.
Untamed (1955), an adventure/love story set in the later part of the trek about an Irish woman seeking a new life in South Africa after the Great Famine . Based on a 1950 novel of the same name by Helga Moray.
The Fiercest Heart (1961), an adventure/love story about two British soldiers who desert the military and join a group of Boers heading north on the Great Trek.
Dorsland Trek
History of South Africa

Definition of 'the Great Trek'

The great trek in british english, browse alphabetically the great trek.

The Great Mother
the Great Powers
the Great Rebellion
the Great Trek
the Greater Antilles
the Greater Dog
All ENGLISH words that begin with 'T'

Quick word challenge

Quiz Review

Score: 0 / 5

Wordle Helper

Scrabble Tools

Great Trek , noun phrase

Visualise quotations, derivatives, browse related words, by category.

"Great Trek, n. phr." Dictionary of South African English. Dictionary Unit for South African English, 2023. Web. 26 April 2024.

Dictionary of South African English , s.v. "Great Trek, n. phr." accessed April 26, 2024, https://dsae.co.za/entry/Great Trek/e02790 .

Great Trek, n. phr. (2023). In Dictionary of South African English. Retrieved from https://dsae.co.za/entry/Great Trek/e02790

This entry documents historical language usage which may be offensive or disturbing.

Please enter your information to subscribe to the Microsoft Fabric Blog.

Microsoft fabric updates blog.

Microsoft Fabric April 2024 Update

Monthly Update

Welcome to the April 2024 update!

This month, you’ll find many great new updates, previews, and improvements. From Shortcuts to Google Cloud Storage and S3 compatible data sources in preview, Optimistic Job Admission for Fabric Spark, and New KQL Queryset Command Bar, that’s just a glimpse into this month’s update.

There’s much more to explore! Read on and let us know what update you’re most excited about and what you found the most helpful.

Fabric Conference Day 1 Keynote is now available!

Did you miss it, or want to hear it again? We are excited to release the FabCon Day 1 Keynote to the Microsoft Fabric YouTube Channel !

If you aren’t already, be sure to subscribe to the Microsoft Fabric Channel! Check out the amazing announcements & demos from Arun, Amir, Wangui, and other awesome presenters. The Day 3 keynotes will be released later this month, and more content will be released regularly moving forward.

Make sure you check out the blog post from Arun, that highlights the announcements from FabCon you can find that here: Announcements from the Microsoft Fabric Community Conference

Earn a free Microsoft Fabric certification exam!

We are thrilled to announce the general availability of Exam DP-600 , which leads to the Microsoft Certified: Fabric Analytics Engineer Associate certification.

Microsoft Fabric’s common analytics platform is built on the instantly familiar Power BI experience , making your transition to Fabric Analytics Engineer easier. With Fabric, you can build on your prior knowledge – whether that is Power BI, SQL, or Python – and master how to enrich data for analytics in the era of AI.

To help you learn quickly and get certified, we created the Fabric Career Hub. We have curated the best free on-demand and live training, exam crams, practice tests and more .

And because the best way to learn is live, we will have free live learning sessions led by the best Microsoft Fabric experts from Apr 16 to May 8, in English and Spanish. Register now at the Learn Together page.

Also, become eligible for a free certification exam by completing the Fabric AI Skills Challenge. But hurry, the challenge only runs from March 19 – April 19 and free certs are first-come, first-served! (limit one per participant, terms and conditions apply).

New Visual – 100% Stacked Area Chart

Line enhancements, enhance q&a with copilot-generated linguistic relationships, snowflake (connector update), storytelling in powerpoint – improved image mode in the power bi add-in for powerpoint, storytelling in powerpoint – continuous slide show auto refresh, storytelling in powerpoint – auto populating the slide title, introducing the fabric metadata scanning sample app, dynamic subscriptions for power bi and paginated reports, supporting folders in workspace, new “clear barcode” action in the report footer, open power bi items in full screen mode, new visuals in appsource kpi matrix growth rate chart by djeeni v1.4 aimplan comment visual.

Financial Reporting Matrix by Profitbase

Horizon Chart by Powerviz

Drill down scatter pro by zoomcharts, image gallery, horizontal bar chart, multi-pane card 1.1.

Introducing Copilot pane in Power BI Desktop (preview)
Shortcuts to Google Cloud Storage and S3 compatible data sources (preview)
OneLake data access roles – public preview

Tenant level Private Link

Managed private endpoints for microsoft fabric.

Trusted Workspace Access for OneLake Shortcuts
Git Integration

Partition elimination performance improvement for tables with a large number of files

Mirroring (public preview) .

Optimistic Job Admission for Fabric Spark
Single Node Support for Starter Pools
Container Image for Synapse VS Code
Git Integration with Spark Job Definition
New Revamped Object Explorer experience in the notebook
%run your scripts in Notebook
Semantic Link is now GA!

Capacity level delegation for AI and Copilot

Eu customers can use ai and copilot without cross-geo setting .

New KQL Queryset Command Bar
New Update Command Public Preview
Introducing Pause and Resume Feature in Eventstream
Fabric Real-Time Analytics Integrates with Newly Announced Database Watcher for Azure SQL (preview)

Service Principal Name authentication kind support for On-Premises and VNET data gateways

Certified connector updates

Updated Fabric data pipeline homepage

Pipeline support for CI/CD in public preview
Data Factory Data Pipelines APIs
Increase in Pipeline activity limit
Fabric Warehouse in ADF copy activity
Edit column type to destination table support added to Fabric Warehouse and other SQL data stores
SFTP: performance improvements when writing data to SFTP

Introducing the new 100% Stacked Area Chart, now available in our core visuals gallery. These visuals display the relative percentage of multiple data series in stacked areas, where the total always equals 100%. It’s perfect for showing the proportion of individual series to the whole and how they change over time. Find it in the visual gallery, on-object dialog, or format pane, right next to the Stacked Area Chart. Give it a try and share your feedback with us!

For more detailed information about this new visual, and the new line enhancements you can read our article: PBI Core Visuals

Take your line charts to the next level with our new line control features.

Adjust line color transparency under Lines > Colors > Transparency.
Control the color and transparency of each series by selecting them in the ‘Apply settings to’ dropdown.
Use Monotone and the new Cardinal smooth type for full control of smooth lines.
Choose from before, center, and after step lines to align your visual with your story.

Try out these new features and enhance your line charts.

These new line enhancements are just the beginning, there is more to come. Try them out and stay ahead of the curve. We would love to hear about your experience and the amazing things you can achieve with these new features.

Improving your linguistic schema is an important step in making sure that the Q&A visual can understand the wide range of questions people might ask about their data. This is why, back in September , we added a new section into the Q&A setup menu to help you add linguistic relationships to teach Q&A about words which qualify or relate your data.

But we also know that coming up with all the different words people might be using to refer to your data can take time and effort, and we’ve been working on ways to make that process easier for you! In November , we introduced a way for you to quickly generate new synonyms for the names of tables and columns in your model; this month, we’ve introduced the same functionality for linguistic relationships!

When you open a report with a Q&A visual, if you have Copilot enabled and you’ve already added synonyms, you’ll now see a banner prompting you to get relationships with Copilot as well.

Unlike with synonyms, Copilot generated relationships will not be used to understand natural language inputs until you have approved them, so make sure you accept the ones which work for your model!

Allow Copilot to help interpret Q&A questions.

You can also now use Copilot to improve the Q&A engine’s term recognition when you ask questions! This new feature will trigger when you ask Q&A a question which uses words or phrases which Q&A doesn’t recognize, but which it detects might be referring to data entities like tables or columns. Then, Copilot will also check those unknown words or phrases to see if there is any reasonable match and if so, return the answer as a visual as though a suggested synonym had been applied.

This feature is not a replacement for synonyms! In fact, adding synonyms for the entities in your semantic model is even more important to create good matches, as they increase the surface area to check for similarities. It will widen the range of inputs Q&A will recognize, but like a multiplier, it will improve recognition for well modeled data much better than it will for poorly modeled data.

This feature will be automatically enabled when you choose to get synonyms with Copilot, but you can also turn it on or off manually in the suggestion settings menu in the Synonyms tab in Q&A setup.

Data Connectivity

The Snowflake connector has been updated to support the use of Snowflake dynamic tables .

We’ve made saving Power BI content as an image more simple and more powerful.

First, we’ve added a new dropdown menu to the add-in’s footer. In that menu, you can choose whether you want to see live data or a snapshot. So now it is much easier to find where to switch between live data and a static image.

Second, for snapshots, you now have two options:

Public snapshot: Anyone who can view the presentation can view the image.

Snapshot: Only those who have permission to view the report in Power BI will be able to see the snapshot.

Third, we’ve disabled the default snapshot, so that the slide thumbnail doesn’t show the image by default (this also applies when you copy & paste the slide into an email for example), but only after the add-in is loaded and the required permissions have been checked.

And lastly, we honor this setting when you open the presentation in PowerPoint for the web. You still cannot change a live view into a snapshot in PowerPoint for the web, but if you or someone else has changed the view to snapshot in the PowerPoint desktop app, this will be respected, and you will see the snapshot also in PowerPoint for the web.

PowerPoint allows you to continuously playback a presentation. This is especially useful when you want to present information in public displays without any human interaction.

If a presentation that is running continuously has slides that include the Power BI add-in, the data in the add-in might become outdated, since the add-in gets the data from Power BI when the slide is loaded, or when the user manually refreshes the data being presented.

With the new automatic refresh in slide show feature, you can set the add-in to automatically pull fresh data from Power BI while the presentation is in slide show mode, ensuring that the presentation will always show the most recent data.

To enable automatic refresh, go to the add-in footer, select Add-in options, choose Slide show settings, check Automatic refresh in slide show and set the desired frequency.

Note that auto refresh only happens in slide show mode and not while you’re editing the presentation.

When you add the Power BI add-in to an empty slide that doesn’t have a title yet, the Power BI add-in is here to help. It offers you suggestions for the slide title based on the content of you add-in. The title can be the report name, the page/visual name, or both. Just select the desired option and hit Add title.

We’re delighted to announce the availability of the new Fabric metadata scanning app. This sample application builds upon the metadata scanning capabilities of Fabric’s set of Admin REST APIs collectively known as the scanner APIs. This new app can be used as a reference for admins interested in utilizing the Scanner API to catalog and report on all the metadata of their organization’s Fabric items.

The Fabric metadata scanning sample app handles all the steps for calling the scanner API including authentication, parallelism, throttling, and incremental scanning. In addition, it provides a central configuration file which can be easily modified to suit the specific needs of the caller. Currently authentication is supported both by using a service principal and a delegated token.

The app is available as a Microsoft open-source project, and is open for suggestions and improvements here: Fabric Metadata Scanning

We’re pleased to announce that you can now send dynamic per recipient subscriptions to up to 1000 recipients instead of the earlier limit of 50 recipients from the data in the Power BI semantic model. For existing subscriptions, we will automatically send subscriptions up to 1000 recipients if your Power BI semantic model contains that many rows of data. You need to edit the subscription if you don’t want to automatically send subscriptions. Learn more about creating dynamic per recipient subscriptions for Power BI Reports and paginated reports .

This feature will be available in some regions as soon as today, however depending on the geography in which your Power BI tenant is located, it may take up to two weeks to appear.

The Power BI Mobile apps support folders in workspace. So, you can access items that are organized in folders inside of your workspace directly from the mobile app.

Workspace and folders are Fabric entities, which means that you can add items that are not necessarily Power BI items to a workspace. But the Power BI Mobile apps only support a subset of Power BI items. Therefore, only the Power BI item will be accessible when you are browsing the folder content from the app. If a folder contains only non-Power BI items, it will appear empty in the mobile app.

When a field in your model is marked as a barcode, you can use your mobile device camera to scan the barcodes of real objects to filter reports that are built on this model. This feature is extremely useful for retail, where you can scan the barcode on a piece of merchandise to get a report showing data about the item directly in your mobile app (for example, inventory information, product selling data, etc.).

To make it easier and more intuitive to use barcodes and based on feedback we’ve gotten from our users in stores, we’ve added a new button to the report footer that makes it a one-click action to clear any previously scanned barcode from the report’s filter.

Learn more about scanning barcode from the mobile app

We continue to simplify the experience of using the Power BI Mobile apps, always keeping in mind the frontline workers who need quick access to their content. In this monthly update we’ve made it possible to open Power BI items in full screen, so users can view their data at its max.

Opening an item in full screen is supported both for launch items and when using a universal link.

A launch item is a Power BI item (report, page, app, etc.) that the user has selected to automatically open when they open the app. Now, you can also tell the Power BI Mobile app to open this item in full screen mode.

To set a launch item to open in full screen mode, go to:

Settings > Launch item and enable the Open in full screen toggle.

Using an MDM tool that supports an AppConfig file, mobile device administrators can also configure a launch item to be opened in full screen mode for their users.

You can also add the query parameter? fullscreen=1 to a Power BI item’s link. When you use a link with this parameter on your mobile device, the mobile app will open the item in full screen mode.

A screenshot of a phone Description automatically generated

Visualizations

Financial reporting matrix by profitbase.

Making financial statements with a proper layout has just become easier with the latest version of the Financial Reporting Matrix.

Users are now able to specify which rows should be classified as cost-rows, which will make it easier to get the conditional formatting of variances correctly:

Et bilde som inneholder tekst, skjermbilde, programvare, nummer Automatisk generert beskrivelse

Selecting a row, and ticking “is cost” will tag the row as cost. This can be used in conditional formatting to make sure that positive variances on expenses are a bad for the result, while a positive variance on an income row is good for the result.

The new version also includes more flexibility in measuring placement and column subtotals.

Measures can be placed either:

Default (below column headers)

Above column headers

Et bilde som inneholder tekst, skjermbilde, nummer, Font Automatisk generert beskrivelse

If you have multiple fields showing on your column headers, you can now decide which of these fields you want a column subtotal for.

This is in addition to the already existing features of the Financial Reporting Matrix:

Adding custom rows

Applying company/customer specific themes

Expand/collapse columns

Conditionally hide columns

+ much more

Highlighted new features:

New Format Pane design

Measure placement – In rows

Select Column Subtotals

Row Options

*Get the visual from AppSource (fix link) and find more videos here !

A Horizon Chart is an advanced visual, for time-series data, revealing trends and anomalies. It displays stacked data layers, allowing users to compare multiple categories while maintaining data clarity. Horizon Charts are particularly useful to monitor and analyze complex data over time, making this a valuable visual for data analysis and decision-making.

Key Features:

Horizon Styles: Choose Natural, Linear, or Step with adjustable scaling.

Layer: Layer data by range or custom criteria. Display positive and negative values together or separately on top.

Reference Line: Highlight patterns with X-axis lines and labels.

Colors: Apply 30+ color palettes and use FX rules for dynamic coloring.

Ranking: Filter Top/Bottom N values, with “Others”.

Gridline: Add gridlines to the X and Y axis.

Custom Tooltip: Add highest, lowest, mean, and median points without additional DAX.

Themes: Save designs and share seamlessly with JSON files.

Other features included are ranking, annotation, grid view, show condition, and accessibility support.

Business Use Cases: Time-Series Data Comparison, Environmental Monitoring, Anomaly Detection

🔗 Try Horizon Chart for FREE from AppSource

📊 Check out all features of the visual: Demo file

📃 Step-by-step instructions: Documentation

💡 YouTube Video: Video Link

📍 Learn more about visuals: https://powerviz.ai/

✅ Follow Powerviz: https://lnkd.in/gN_9Sa6U

A screenshot of a screenshot of a graph Description automatically generated

ZoomCharts has just launched the latest addition to their suite of user-friendly custom visuals – Drill Down Scatter PRO. It provides all the features you would expect from a great scatter chart visual, but what sets Scatter PRO apart is the ability to easily drill down. Simply click on a data point and see all the values underneath it.

This way, you can quickly find your answers while also gaining a full understanding of where they come from. Furthermore, the visual’s UI is designed to be smooth and user-friendly for PCs and touch devices, and with cross-chart filtering you can use Scatter PRO to build incredible reports for immersive data exploration.

Main features:

Drill Down: Create a multi-level hierarchy and drill down with just a click.

Dynamic formatting: Apply custom marker colors, shapes, or images to each data point directly from data.

Trendlines: Show a linear or polynomial regression line on the chart.

Thresholds: Display up to 4 line or area thresholds on each axis.

Area Shading: Highlight up to 8 custom areas with rectangles or ellipses.

🌐 Learn more about Drill Down Scatter PRO

Documentation | ZoomCharts Website | Follow ZoomCharts on LinkedIn

A screenshot of a computer screen Description automatically generated

The Image Gallery is the first visual to be certified by Microsoft that allows for the display of high-quality images and their exportation along with other report content. There is no need to upload images to the Cloud, a CDN, or use any datasets. Simply import your images directly into the visual and share them instantly with your colleagues.

This visual boasts several impressive capabilities:

Microsoft certification ensures that the visual doesn’t interact with external services, ensuring that your images are securely stored and encrypted within the report, consistent with your report’s sensitivity settings.

Automatically saves your selected image in preview mode, allowing your colleagues to view the exact image you have highlighted.

Images can be uploaded or removed exclusively in Edit Mode. Users in View Mode can only view the images.

The visual is compatible with Power BI’s export functionality to PDF and PowerPoint.

A screenshot of a computer Description automatically generated

Image Gallery Link

A space-saving horizontal bar chart designed with category labels placed inside the bars for clarity.

This horizontal bar chart serves as an efficient filter to navigate through your data more effectively, optimizing space by placing the category labels within the bars themselves.

Adjustable Bar Thickness and Spacing: Offers the flexibility to adjust the thickness of the bars and the spacing between them. This allows for optimal use of space and improves readability, especially when dealing with large datasets.

Tooltip Details on Hover: Displays detailed information about each category when the user hovers over a bar. This feature provides additional context and insights without cluttering the visual.

Data-Driven Category Labels: Automatically updates category labels based on the data source. This ensures that the chart remains accurate and up to date, reflecting any changes in the underlying data.

Support for Hierarchical Data: Allows users to drill down into hierarchical categories within the chart. This functionality enables a more detailed data analysis without leaving the context of the initial visual.

Export Options: Offers the ability to export the chart as an image or PDF, facilitating easy sharing and reporting outside of Power BI.

HorizontalBarChart Link

Introducing the “ Trends ” visual for Power BI – your gateway to leveraging Google Trends data for strategic business analysis. This innovative visual tool allows you to compare brand popularity, monitor market trends, and gain insights into consumer search behaviors directly within your Power BI environment.

With Trends visual, you can:

Analyze the ebb and flow of brand interest over time to identify market opportunities and competitive threats.

Compare the popularity of products to inform marketing strategies and product development decisions.

Understand seasonal trends to optimize your marketing campaigns and inventory planning.

Securely integrated and easy to use, “Trends” transforms your Power BI reports into a dynamic analysis tool, offering a comprehensive view of the market landscape. Dive into data-driven decision-making with “Trends” and stay one step ahead in the competitive business environment.

New visual: Multi-pane Card can be used to group and show data in multiple collapsible panes in Power BI reports. It is an alternative to multi-row card visual, but it can combine columns into a few groups and put each group’s data in each pane. It is suitable to show data in detail with a reduced number of report pages.

Screenshot 1 (Show data in 3 groups: Area and Population, GDP and Foreign Exchange Reserves for countries)

Data can be sorted by a specified column and numbers can be converted to a human readable string. You can also set up how many rows that you want to show on the card. Using these features, it will be very easy to show “Top 10 best performing stores” or “Top 10 worst performing stores” for retail businesses.

Screenshot2 (Combined with drilldown choropleth map to show the top 10 richest countries by GDP per capita for each continent and subregion)

You can go to Microsoft AppSource: Multi-pane Card , to download and try it.

To learn more on how to use it, please read tutorials ( https://www.mylocs.ca/tutorials.html#multi-pane-card ).

Introducing Copilot pane in Power BI Desktop (preview)

Earlier this year, we announced preview of Copilot for all customers with Premium/Fabric capacity in Power BI web . We’re thrilled to share that the same Copilot experience for report creation is now available for preview in Power BI Desktop. With our current preview, users can create reports faster and easier in the Power BI Desktop experience. You can now open the Copilot pane in report view and ask Copilot to:

Create a report page – Copilot will create an entire report page for you by identifying the tables, fields, measures, and charts that would help you get started.

Summarize a semantic model – Copilot will help you understand your Power BI semantic model by summarizing the data in your model.

Suggest a topic – Copilot will suggest topics for your report pages.

Click here to learn more about how to get started.

Shortcuts to Google Cloud Storage and S3 compatible data sources (preview)

We are excited to announce that you can now create OneLake shortcuts to your Google Cloud Storage (GCS) buckets and S3 compatible data sources!

With the addition of GCS, you can now utilize cross-cloud shortcuts to analyze your data across all three major cloud platforms. Shortcuts in OneLake allow you to connect to your existing data through a single unified name space without having to copy or move data. Just open Lakehouse in Fabric, create a shortcut to GCS, AWS S3 or ADLS Gen2 and immediately start analyzing your data through Spark, SQL and Power BI.

OneLake is also adding connectivity to data sources that offer an Amazon S3 compatible API, a widely supported API offered by many distributed file systems and services that offer object storage. With this new feature, it’s quick and easy to create a shortcut that references your cloud based S3 compatible data sources. The data source endpoint simply needs to offer S3 compatible APIs, be publicly hosted and accessible, and accept the key/secret credentials you provide during shortcut creation. Once you set up your shortcut, you can access and use your data with the many Fabric engines or other services using OneLake’s open APIs .

Learn more in our recent blog posts for S3 compatible shortcuts and GCS shortcuts !

OneLake data access roles (preview)

OneLake data access roles for folders are a new feature that enables you to apply role-based access control (RBAC) to your data stored in OneLake. You can define security roles that grant read access to specific folders within a Fabric item and assign them to users or groups. The access permissions determine what folders users see when accessing the lake view of the data, either through the lakehouse UX, Spark notebooks, or OneLake APIs.

OneLake previously managed data access at the Fabric item level. Access to the OneLake data behind a Fabric item could be granted or removed for users or groups. Data access roles now allow for defining security roles that can grant access to individual OneLake folders within a Fabric item. The granted access inherits to any newly added sub-folders in a transparent manner. Role permissions and user/group assignments can be easily updated through a new folder security UX or through API calls. The security also extends to 3rd party access requests made through the OneLake APIs.

Check out the full announcement blog or jump right into the getting started guide!

Organizations today rely on cloud platforms for storage and analysis of data at scale and need to keep up with the accelerating volume of data while protecting sensitive information. While enterprises in Banking, Healthcare, and similar domains require strict data security standards by default, securing business-critical data is the highest priority for all enterprises. We are excited to announce the public preview of an enhanced networking feature, Azure Private Link for Microsoft Fabric, for securing access to your sensitive data in Microsoft Fabric by providing network isolation and applying required controls on your inbound network traffic.

Private Links enable secure connectivity to Fabric by restricting access to your Fabric tenant from an Azure VNet of your choice and blocking all public access. This ensures that only network traffic from that VNet is allowed to access Fabric experiences like Notebooks, Lakehouses, Warehouses in your tenant.

With Azure Private Link, you can:

Restrict traffic from the internet to Fabric and route it through the Microsoft backbone network.
Ensure only authorized client machines can access Fabric.
Comply with regulatory and compliance requirements that mandate private access to your data and analytics services.

While Azure private links were supported in Power BI at a tenant level, we are now extending this feature to other Fabric workloads with this release. For example, connecting to your data in Onelake using the OneLake Explorer can be protected through Private Links. Similarly, you can access Warehouses and Lakehouse SQL endpoints in SQL Managed Studio via Private Links. A list of supported scenarios and limitations can be found at Use private link to access Fabric. for detailed instructions, please refer to How to set up private endpoints to access Fabric .

We are excited to announce the public preview of Managed Private Endpoints for Microsoft Fabric. This feature allows secure connections to data sources that are behind a firewall or not accessible from the public internet. Managed Private Endpoints enable Fabric Data Engineering items to access data sources securely without exposing them to the public network or requiring complex network configurations. These private endpoints provide a secure way to connect and access data from sources like Azure SQL DB or Storage account blocked from public access from your Fabric Spark Notebooks or Spark Job Definitions.

Workspaces with managed private endpoints have network isolation through a dedicated managed virtual network. These managed virtual networks (Managed VNETs) separate the Spark compute clusters from the shared virtual network and enable network security features such as private links and managed private endpoints. Microsoft Fabric takes care of the provisioning and management of the virtual networks and private endpoints, so users do not have to create or manage these network infrastructure resources themselves.

By just providing connection details, your managed private endpoint is instantly provisioned in the Managed VNET and a request for private endpoint access is submitted to the data source administrator for approval.

Users can track the status and approval process of the managed private endpoints from the Network security section of the Workspace settings.

Managed Private Endpoints support various data sources, including Azure Storage, Azure SQL Database, Azure Synapse Analytics, Azure Cosmos DB, Application gateway, Azure Key Vault, and many more.

Learn more about the data sources supported, please refer to our documentation Create and use managed private endpoints in Microsoft Fabric (preview) – Microsoft Fabric | Microsoft Learn

Note: Managed private endpoints are only supported for Fabric Trial capacity and Fabric capacities F64 or higher SKUs.

To learn more about the benefits, detailed steps of setup and limitations of managed private endpoints in Microsoft Fabric, please refer to our documentation Overview of managed private endpoints in Fabric.

To learn more about network isolation offered by managed virtual networks, please refer to Overview of managed virtual networks in Fabric .

Trusted Workspace Access for OneLake Shortcuts

Trusted workspace access allows you to securely access firewall-enabled Storage accounts. With Trusted workspace access, you can create OneLake shortcuts to Storage accounts, and then use the shortcuts in various Fabric items, such as Spark notebooks, SQL analytics endpoints, semantic models, reports, data pipelines, and dataflows Gen2.

Trusted workspace access is designed to help you securely and easily access data stored in Storage accounts from Fabric workspaces, without compromising on performance or functionality. You can leverage the power and flexibility of Fabric and OneLake to work with data in place without compromising on security.

How does Trusted workspace access work?

Trusted workspace access is based on the concept of workspace identity, which is a unique identity that can be associated with workspaces that are in Fabric capacities. When you create a workspace identity, Fabric creates a service principal in Microsoft Entra ID to represent the identity.

Workspace identity enables OneLake shortcuts in Fabric to access Storage accounts that have resource instance rules configured. Resource instance rules are a way to grant access to specific resources based on the workspace identity or managed identity. You can create resource instance rules by deploying an ARM template with the resource instance rule details.

To leverage Trusted workspace access in Fabric workspaces, you can create a OneLake shortcut in a Lakehouse, and provide the URL of the Storage account that has been configured with a resource instance rule. While creating the shortcut, you need to select organizational account or service principle for authentication and ensure that the principle used for authenticating to Storage has the appropriate Azure RBAC roles on the Storage account. Once the shortcut is created, you can use it in various Fabric items.

How to get started with Trusted workspace access?

Trusted workspace access is available for workspaces in Fabric capacities (F64 or higher). To get started with Trusted workspace access, you need to do the following steps:

Create a workspace identity for your Fabric workspace if you don’t have one already. If you face issues with creation of the workspace identity, follow the troubleshooting guidelines provided here .

Create a workspace identity.

2. Configure resource instance rules for the Storage account that you want to access from your Fabric workspace. Follow the guidelines for configuring resource instance rules for Fabric workspaces here .

Resource instance rules in a Storage account

Create a OneLake shortcut to the Storage account in a Lakehouse and select the organizational account or service principal option for authentication.

Create an ADLS g2 shortcut in a Lakehouse.

4. Use the OneLake shortcut in various Fabric items, such as Spark notebooks, SQL analytics endpoints, semantic models, reports, data pipelines, and dataflows Gen2.

Access data stored in firewall-enabled Storage accounts through OneLake shortcuts.

For more details and guidance on how to use Trusted workspace access, please refer to the documentation links below.

Trusted workspace access in Fabric
Workspace identity in Fabric

Data Warehouse

Git integration .

We are excited to announce the Git integration for the Warehouse! This feature allows you to check in the changes of your Warehouse into an Azure DevOps Git repository as a SQL database project. Git integration enables source control capabilities for developers to integrate their development processes, tools, and best practices directly into the Fabric platform.

Some scenarios that are enabled by Git:

Backup and version development work
Revert to previous stages
Collaborate with others or work alone using Git branches
Apply the capabilities of familiar source control tools to manage your Warehouse
Commit changes
Sync changes from Git
Manage conflict resolutions
…and many more!

The SQL analytics endpoint of a Lakehouse uses partition elimination to read data from only those partitions that are relevant to the query. Recent improvements have boosted performance even more when queries are aimed at a few partitions in a table that has many files.

We are thrilled to announce Mirroring in Fabric for Azure SQLDB, CosmosDB and Snowflake is in Public Preview!

Mirroring in Fabric allows users to enjoy a highly integrated, end-to-end, and easy-to-use product that is designed to simplify your analytics needs. Built for openness and collaboration between Microsoft, and technology solutions that can read the open-source Delta Lake table format, Mirroring is a low-cost and low-latency turnkey solution that allows you to create a replica of your Azure SQL DB, Snowflake or CosmosDB data in OneLake which can be used for all your analytical needs. Learn more

Data Engineering

Optimistic job admission for fabric spark.

We are excited to announce a new feature for Fabric Spark: Optimistic Job Admission. This feature aims to reduce the frequency of throttling errors (HTTP 430: Spark Capacity Limit Exceeded Response) and improve the job admission experience for our customers, especially during peak usage hours.

Throttling errors on Spark workload occur when the Spark usage exceeds the Fabric capacity limits. In the current job admission policy, Fabric Spark reserves the maximum number of cores that a job may need during its execution, based on the maximum number of nodes that the job can scale up to. This ensures that the job will always have enough resources to run, but it also limits the number of concurrent jobs that can be admitted in the cluster.

With Optimistic Job Admission, Fabric Spark only reserves the minimum number of cores that a job needs to start, based on the minimum number of nodes that the job can scale down to. This allows more jobs to be admitted if there are enough resources to meet the minimum requirements. If a job needs to scale up later, the scale up requests are approved or rejected based on the available cores in capacity.

Optimistic Job Admission can significantly increase the max number of concurrent jobs for our customers, especially for those who use large SKUs. For example, if a customer is using F32 SKU, which has 64 Spark VCores (Based on 1 CU = 2 Spark VCores) and 192 Max Burst Cores for concurrency (based on the 3X burst multiplier), they can only run 3 jobs concurrently in the current job admission policy, assuming they have the default starter pool configuration.

Now with Optimistic Job Admission, they can run up to 24 jobs concurrently with the same configuration. This is an 8x improvement!

We hope that this feature will help you run more jobs faster and more efficiently on Fabric Spark.

Single Node Support for Starter Pools

Do you hate waiting for your Spark sessions to start in starter pools with single node configuration? If yes, you will love the update on single node starter pool support. This feature lets you set your starter pool to max one node and get super-fast session start times for your Spark sessions. With this new support that’s been introduced, the system allocates the driver and executor with 4 cores each and 56 GB in memory, so that they fit within a single medium node configuration for Starter Pools. This improves session start times to 5 seconds in single node starter pool configurations.

How can you use it?

To use this feature, follow these steps:

Go to your Fabric workspace and choose the Workspace settings.
Select the Data Engineering/Science option to expand the menu.

Screenshot showing Spark Settings detail view.

Select the StarterPool option from the Pool selection and click on Edit.

Screenshot showing starter pool configuration options.

Set the maximum node configuration for your starter pools to 1.

Save your changes and enjoy super-fast session start times for your Spark sessions.

Container Image for Synapse VS Code

To simplify the development process for Synapse VS Code extension, we have released a container image that contains all the necessary dependencies for the extension ( Microsoft Artifact Registry) . This image is available in Microsoft artifact repository and can be pulled with a single command. By using this image, you do not need to install Java, Miniconda, or any other tools on your local machine. You can work on your Synapse projects inside the container environment, which is isolated and consistent.

We have also integrated the container image with VS Code dev container feature, which allows you to open a folder or a repository inside a container and use the VS Code editor and extensions as usual. To use this feature, you need to install the Remote – Containers extension and create a devcontainer.json file in your project folder. We have provided a sample devcontainer.json file that you can use as a template or customize according to your needs ( SynapseVSCode/samples/.devcontainer at main · microsoft/SynapseVSCode (github.com) ). The dev container feature will automatically pull the container image, mount your project folder, and launch the VS Code editor inside the container. You can then enjoy the full functionality of the Synapse VS Code extension without any hassle.

Git Integration with Spark Job Definition

We are excited to announce the Git integration for Spark Job Definition artifacts. This feature allows you to check in the changes of your Spark Job Definitions into a Git repository, which will include the source code of the Spark jobs and other artifact properties. By using Git as a version control system, you can track the history of your Spark Job Definitions, collaborate with other developers, and implement CI/CD workflows for your Spark projects.

The Git integration for Spark Job Definition artifacts is designed to enhance your development experience and enable CI/CD scenarios for your Spark projects. We hope you find this feature useful, and we welcome your feedback and suggestions.

When a new Spark Job Definition is made with a PySpark script as the main definition file, the Git status shows that this is an unsaved change that needs to be committed.

Once the change is finalized mich

The structure of the linked git repository and the file containing the source code that was submitted.

New Revamped Object Explorer experience in the notebook

We are excited to announce the release of a revamped object explorer experience. The new experience is designed to improve flexibility and discoverability of data sources in the explorer and improve the discoverability of Resource folders.

Try it out and add new Data sources clicking on the +Data sources button and upload new modules or create folders by clicking on the Resources folder and let us know what you think.

%Run your scripts in Notebook

Now you can use %run magic command to run your Python scripts and SQL scripts in Notebook resources folder, just like Jupyter notebook %run command. By this way you can easily reuse common modules that developed from your local IDE and use them in your Fabric Notebooks conveniently. We also introduced different command parameters to make sure complex cases such as reference run and high concurrency mode can be covered without friction, stay tuned for the best practice example for the usage!

Data Science

Semantic link is now ga .

Semantic links are now generally available! The package comes with our default VHD, you can now use Semantic link in Fabric right away without any pip installation. Check it out .

We introduced a new feature in December 2023 that allows tenant admins to enable AI and Copilot in Fabric for certain security groups in addition to the entire organization. Today, we are excited to announce that you can enable AI and Copilot for a specific Capacity. You can test Copilot at a certain capacity without impacting other workloads. This allows you to adapt Copilot to meet the needs of different groups in your organization and manage your capacity more effectively.

AI and Copilot in Fabric are powered by large language models that are only available in limited datacenters. Previously, users who were not in US and France had to turn on the cross-geo setting to use AI and Copilot. Since mid-March, we updated the cross-geographic mapping logic, EU customers can use AI and Copilot without turning on the cross-geo setting, and their AI and Copilot requests will be processed within EUDB. Check it out !

Real-time Analytics

New kql queryset command bar.

Finding the commands for the actions you are trying to perform just got easier with our latest update to the KQL Queryset. Now, it’s easy to distinguish between actions applicable at the Queryset level and the single query level.

Introducing a secondary command bar within the query editor dedicated to hosting query-level actions. Enjoy smoother navigation and streamlined functionality for a more efficient querying experience.

New Update Command Public Preview

The new update command is now in public preview!

This allows you to update existing records in a Kusto Table. This can be useful to fix ad hoc data issues or be integrated into a data loading pipeline. The command has a “what if” mode to try a command before running it on your data.

.update table Employees on Id <|

MyStagingTable

| where true

Introducing Pause and Resume Feature in Eventstream

We’re excited to introduce a powerful new feature in Fabric Eventstream: The Pause and Resume Feature. This powerful capability empowers you with unprecedented control over your data streams, enabling you to pause data streaming from various sources and destinations within Eventstream. You can then resume data streaming seamlessly from the paused time or a customized time, ensuring no data loss.

Key Features:

Activate/Deactivate All : You can quickly pause and resume all data traffic flowing in and out of Eventstream with the Activate All and Deactivate All options on the menu bar.
Toggle Switch Button : Each node has a convenient toggle switch button, allowing you to activate or deactivate any data source from streaming in or out of Eventstream with ease.

With the Pause and Resume feature in Fabric Eventstream, you can pause traffic from specific sources and destinations whenever needed. Whether it’s for troubleshooting purposes, building proof-of-concepts with test data, or minimizing unnecessary data processing costs, this feature offers unparalleled control over your data streams and leads to more efficient resource allocation.

Fabric Real-Time Analytics Integrates with Newly Announced Database Watcher for Azure SQL (preview)

Azure SQL family users can now take advantage of an enhanced monitoring solution for their databases and leverage Microsoft Fabric integration. With the introduction of the new Database Watcher for Azure SQL (preview), users gain access to advanced monitoring capabilities. Through integration with Microsoft Fabric, they can effortlessly stream, store, and analyze monitoring data in real-time using an Eventhouse database in Fabric Real-Time Analytics. This integration enables users to stay informed about their database performance and make timely, informed decisions.

Database watcher is a new managed monitoring solution for database services in the Azure SQL family. It supports Azure SQL Database and Azure SQL Managed Instance.

Database watchers collect in-depth workload monitoring data to give you a detailed view of database performance, configuration, and health. Monitoring data from the databases, elastic pools, and SQL managed instances you select is collected in near real time into a central data store. To store and analyze SQL monitoring data, database watcher uses an Eventhouse database in Fabric Real-Time Analytics (as a complement option, Azure Data Explorer is also supported).

Dashboards in Azure portal provide a single-pane-of-glass view of your Azure SQL estate and a detailed view of each database, elastic pool, and SQL managed instance.

A conceptual diagram of a database watcher deployment, showing the flow of monitoring data from Azure SQL resources to a database watcher. The monitoring data is stored in Fabric Real-Time Analytics . Dashboards in the Azure portal show you a single-pane-of-glass view across your Azure SQL estate, and a detailed view of each database, elastic pool, and managed instance.

You can query data in your Eventhouse database in Real-Time Analytics using KQL or T-SQL , analyze and model your data using Real-Time Analytics Querysets or Fabric Notebooks , build custom visualizations using KQL built-in visualizations or Power BI .

To analyze collected monitoring data, the recommended method is to use KQL. KQL is optimal for querying telemetry, metrics, and logs. It provides extensive support for text search and parsing, time-series operators and functions, analytics and aggregation, and many other language constructs that facilitate data analysis. You can find examples of analyzing database watcher monitoring data with KQL in the documentation .

The dashboards, complemented by KQL queries, enable you to delve deep into the performance and configuration of your databases. This means you can detect, investigate, and troubleshoot a wide variety of database performance and health issues.

Whether you’re tackling resource bottlenecks or fine-tuning your Azure SQL resources for the best balance of cost and performance, Database Watcher equips you with the insights needed to make informed decisions. It’s your pathway to optimizing your Azure SQL setup for peak efficiency and cost-effectiveness.

Next steps

One effective approach to grasp the potential and the power of Database Watcher is to give it a try yourself. Set up your Azure SQL resources with Database Watcher, explore the dashboards, and start running some queries with KQL. To read more about Database Watcher, check out the documentation .

Data Factory

Dataflows gen2 , fast copy .

Dataflows help with ingesting and transforming data. With the introduction of dataflow scale out with the SQL DW compute, we are able to transform your data at scale. However, to do this on a scale, your data needs to be ingested first.

With the introduction of fast copy, you can ingest Terabytes of data with the easy experience of dataflows, but with the scalable back end of Pipeline’s Copy Activity.

We released support for Azure Service Principals (SPN) as an authentication kind last year. Now we’ve added support for this new authentication kind for on-premises data gateways and VNET data gateways.

Azure service principal is a security identity that is application based and can be assigned permissions to access your data sources. Service principals are used to safely connect to data, without a user identity. Learn more about service principals.

You can learn how to leverage the service principal authentication kind from the documentation available and leverage this in multiple connectors such as Azure Data Lake Storage, Dataverse, Azure SQL database, Web connector and more.

Certified connector updates

We’re pleased to announce the new and updated connectors in this release:

[New] Topcon Aptix Insights
[Update] BitSight Security Ratings
[New] Zendesk Data
[Update] Planview OKR
[Update] BQE Core
[New] LinkedIn Learning
[New] LEAP
[New] Samsara
[Update] Celonis EMS
[New] Supermetrics
[New] Exact Online Premium

Are you interested in creating your own connector and publishing it for your customers? Learn more about the Power Query SDK and the Connector Certification program .

Data pipelines

The Data pipeline homepage is now updated with an all-new look! You’ll now find new guidance cards to help you find what you’re looking for more quickly.

Pipeline support for CI/CD in public preview

When developing workflows with Data Factory’s pipelines it is very important for developers to be able to save their work in a Git repository for versioning, source control, and CI/CD. We are happy to announce the public preview of CI/CD support for Data Factory pipelines! Now, you can connect your Azure DevOps (ADO) projects to your Fabric workspace and commit, merge, and branch your pipelines using Fabric’s Git integration. Additionally, you can now use the built-in Deployment Pipelines inside Fabric to assign workspaces to different environments (dev, test, prod) and promote your changes easily without using ADO!

Data Factory Data Pipelines APIs

You can now use our public APIs to create, execute, and monitor data pipelines in Fabric Data Factory.

Increase in Pipeline activity limit

As a cloud service for analytics workflows, the Data Factory team has had a limit of 40 activities per pipeline since the early days of Azure Data Factory. The same orchestration engine drives Fabric Data Factory data pipelines and we’ve reacted to your feedback that many times you need more than 40 activities in a pipeline to perform complex workflows that require error checks, branching, and other control flow capabilities. We’ve now updated the limits for the Data Factory pipeline service in both Fabric and Azure (Azure Data Factory & Synapse pipelines) to now allow up to 80 activities per pipeline.

Fabric Warehouse in ADF copy activity

We’re excited to announce that you can now connect to your Fabric Warehouse from Azure Data Factory/Synapse pipeline. You can find this new connector when creating a new source or sink destination in your copy activity.

This connector is also supported in the Lookup activity, Stored Procedure activity, Script activity, and Get Metadata activity.

Edit column type to destination table support added to Fabric Warehouse and other SQL data stores

When moving data from any supported data sources into Fabric Warehouse or other SQL data stores (SQL Server, Azure SQL Database, Azure SQL Managed Instance; Azure Synapse Analytics) via data pipelines, users can now specify the data type for each column under the destination table, as well as customize the precision and scale to certain data types such as decimal, numeric, etc.

SFTP: performance improvements when writing data to SFTP

SFTP connector has been improved to offer better performance when writing to SFTP as destination.

Microsoft Fabric February 2024 Update

Welcome to the February 2024 update. We have a lot of great features this month including Fabric Git Integration REST APIs, Fabric notebook status bar upgrade, Copilot in Dataflow Gen2, and many more! Fabric Community Conference Join us at the Microsoft Fabric Community Conference the ultimate Microsoft Data & AI learning event, on March 26-28, … Continue reading “Microsoft Fabric February 2024 Update”

IMAGES

The Boers make the Great Trek to their promised land
Great Trek
Great Trek 1835-1846
What was the Great Trek?
THE GREAT TREK 1836
The Great Trek

VIDEO

Nitpicking STD
Benjamin Ask Jake To Be His Best Man

COMMENTS

Great Trek
Great Trek, the emigration of some 12,000 to 14,000 Boers from Cape Colony in South Africa between 1835 and the early 1840s, in rebellion against the policies of the British government and in search of fresh pasturelands. The Great Trek is regarded by Afrikaners as a central event of their 19th-century history and the origin of their nationhood. It enabled them to outflank the Xhosa peoples ...
Great Trek
The Great Trek (Afrikaans: Die Groot Trek [di ˌχruət ˈtrɛk]; Dutch: De Grote Trek [də ˌɣroːtə ˈtrɛk]) was a northward migration of Dutch-speaking settlers who travelled by wagon trains from the Cape Colony into the interior of modern South Africa from 1836 onwards, seeking to live beyond the Cape's British colonial administration. The Great Trek resulted from the culmination of ...
Great Trek
The Great Trek was a very important event in the history of South Africa . It came about because of disagreements between British and Afrikaner settlers in the colony known as the Cape Colony. As a result of the disagreements, many Afrikaner farmers moved away from the Cape Colony and established their own colonies. This was a first step in ...
Great Trek 1835-1846
Great Trek 1835-1846. The Great Trek was a movement of Dutch-speaking colonists up into the interior of southern Africa in search of land where they could establish their own homeland, independent of British rule. The determination and courage of these pioneers has become the single most important element in the folk memory of Afrikaner ...
What was the Great Trek?
The Great Trek was a perilous exodus of pioneers into the heart of South Africa, looking for a place to call home. When the British took control of Cape Town and the Cape Colony in the early 1800s, tensions grew between the new colonizers of British stock, and the old colonizers, the Boers, descendants of the original Dutch settlers. From 1835 ...
Great Trek
The Great Trek began in 1835. More than 12,000 farmers left the Cape Colony. They took with them about 10,000 black workers, and they drove large herds of cattle. They mostly traveled on horseback and in ox-drawn wagons and were armed with muzzle-loading guns. Some of their best-known leaders were Piet Retief, Gerrit Maritz, Andries Potgieter ...
GREAT TREK Definition & Usage Examples
Great Trek definition: . See examples of GREAT TREK used in a sentence.
Great Trek Definition & Meaning
Great Trek definition, the migration of Boer farmers with their slaves and African servants from the Cape Colony to the north and east from about 1836 to 1845 to escape British authority See more.
Great Trek
Search for: 'Great Trek' in Oxford Reference ». The movement northwards in the 1830s by Boers to escape from British administration in the Cape Colony. From 1835 onwards parties of Voortrekkers reached Natal, where in 1837 Zulu resistance provoked them to kill some 3,000 Zulus at the Battle of Blood River in revenge for the death of their ...
The Great Trek
The Great Trek Credit: James E. McConnell, painter, (1903-1995) You might also be interested in… Lesson Save. 10 Questions for the Future: Student Action Project Students create a plan for enacting change on an issue that they are most passionate about using the 10 Questions Framework. ...
Great Trek
Great Trek. Afrikaners left the Cape Colony (in present-day South Africa) in large numbers during the second half of the 1830s, an act that became known as the "Great Trek" and that helped define white South Africans' ethnic, cultural, and political identity.In line with Afrikaners' belief in a separate existence, developing tensions between these settlers, British authorities, and African ...
GREAT TREK definition and meaning
→ See the Great Trek.... Click for English pronunciations, examples sentences, video.
GREAT TREK definition in American English
to disagree. to instruct to browse to oppose to sprint. SYNONYMS. Select the synonym for: scenic. recent panoramic scared fashionable. Your score: Mar 29, 2024. Word of the day.
What was The Great Trek?
In this video I explore the Great Trek undertaken by South African Boers in the 1840's, hope you enjoy!This video is also available in Dutch:https://www.yout...
Great Trek
Great Trek synonyms, Great Trek pronunciation, Great Trek translation, English dictionary definition of Great Trek. n the Great Trek history South African the migration of Boer farmers with their slaves and African servants from the Cape Colony to the north and east from...
The Great Trek Part 1
The Great Trek was a northward migration of Dutch-speaking settlers who travelled by wagon trains from the Cape Colony into the interior of modern South Afri...
Trek Definition & Meaning
trek: [noun] a trip or movement especially when involving difficulties or complex organization : an arduous journey.
Voortrekker
Voortrekker, any of the Boers (Dutch settlers or their descendants), or, as they came to be called in the 20th century, Afrikaners, who left the British Cape Colony in Southern Africa after 1834 and migrated into the interior Highveld north of the Orange River.During the next 20 years, they founded new communities in the Southern African interior that evolved into the colony of Natal and the ...
Great Trek
The Great Trek (Afrikaans: Die Groot Trek [di ˌχruət ˈtrɛk]; Dutch: De Grote Trek [də ˌɣroːtə ˈtrɛk]) was a northward migration of Dutch-speaking settlers who travelled by wagon trains from the Cape Colony into the interior of modern South Africa from 1836 onwards, seeking to live beyond the Cape's British colonial administration. [1] The Great Trek resulted from the culmination of ...
Boers
The Great Trek occurred between 1835 and the early 1840s. During that period some 12,000 to 14,000 Boers (including women and children), impatient with British rule, emigrated from Cape Colony into the great plains beyond the Orange River, and across them again into Natal and the vastness of the Zoutspansberg, in the northern part of the ...
trek noun
Definition of trek noun in Oxford Advanced Learner's Dictionary. Meaning, pronunciation, picture, example sentences, grammar, usage notes, synonyms and more.
Definition of 'the Great Trek'
the Great Trek in British English. South Africa history. the migration of Boer farmers with their slaves and African servants from the Cape Colony to the north and east from about 1836 to 1845 to escape British authority. See full dictionary entry for Great Trek. Collins English Dictionary.
Great Trek
Any long and arduous journey or exodus to another place, especially one undertaken by a large number of people; a difficult or noteworthy change of attitude, opinion, or belief; groot trek. 1892 The Jrnl 10 Sept. 2 Many of the Transvaal farmers are thoroughly disgusted with the recent course of events in that republic, and.. a great trek ...
Microsoft Fabric April 2024 Update
Welcome to the April 2024 update! This month, you'll find many great new updates, previews, and improvements. From Shortcuts to Google Cloud Storage and S3 compatible data sources in preview, Optimistic Job Admission for Fabric Spark, and New KQL Queryset Command Bar, that's just a glimpse into this month's update.